Hi team! I would like to know how private keys are stored in auth network, and whether node owners have the authority to directly access users’ private keys.
@batxent Welcome Aboard!
The Web3Auth wallet Infrastructure is a decentralised model that splits the user’s private key into multiple factors/shares.
- ShareA is managed and divided across Web3Auth’s Auth Network and can be accessed through an OAuth login provider owned by the user, like their Google account.
- ShareB is stored on the user’s device. The method of storage is specific to the device and system. For instance, on mobile devices, the share could be stored in device storage that’s secured with biometrics.
- ShareC serves as a recovery share. It’s an extra share that the user can keep on a separate device, download, or base on user input with sufficient entropy. This could include a password, security questions, or a hardware device, among other options.
Like existing 2FA systems, users must prove ownership of at least 2 out of 3 (2/3) shares to retrieve their private key. You can read more here
Since the private keys is split across nodes and we are non-custodial, there is no one node operator that can directly access the user’s private keys since it needs to be reconstructed across the auth network and only the user has access to it.
ShareA is managed across Auth Network, so if each Auth Network node can retrieve it?
ShareA is managed and divided across Web3Auth’s Auth Network and can be accessed through an OAuth login provider owned ONLY by the user.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.