Now you can use your @auth0 login to generate a non-custodial #web3 private key using their official @Web3Auth marketplace integration!
This is a huge step for the #web3 ecosystem, because… 🧵
auth0.com/blog/web3-sign…
This is a huge step for the #web3 ecosystem, because… 🧵
auth0.com/blog/web3-sign…
@auth0 is the biggest name in authentication, with thousands of apps and millions of users logging in every hour!
This integration now allows ALL these applications to onboard their users to #web3 with just a couple of lines of code.
This integration now allows ALL these applications to onboard their users to #web3 with just a couple of lines of code.
To get access to any #dapp, a user needs a key pair.
Using the secure OAuth 2.0 logins from Auth0 and the threshold architecture from Web3Auth, a user can generate a key pair, using standard Web2 logins.
Using the secure OAuth 2.0 logins from Auth0 and the threshold architecture from Web3Auth, a user can generate a key pair, using standard Web2 logins.
When a user logs in with their preferred web2 login, @auth0 sends a JWT id_token to the app.
This JWT token is sent to the Web3Auth SDK's login function, where on successful validation Web3Auth SDK will generate a private key for the user in a non-custodial way.
This JWT token is sent to the Web3Auth SDK's login function, where on successful validation Web3Auth SDK will generate a private key for the user in a non-custodial way.
This enables the user to access any web3 app, on any chain without the need to change their login habits. See it for yourself.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
