I’m assuming that Torus & Web3auth is done on a separate blockchain.
After looking this up on their docsite here, this is what their current architecture looks like for integrating with the Torus network
I haven’t been able to find much information/documentation on the actual Torus network itself and how it is architected, how decentralized it is, etc. (please point me to docs if you’ve found them!).
I definitely see a potential benefit in de-risking your application by having user auth and user data on different blockchains (especially given the friction and performance around adopting Internet Identity), but I would be wary to use Web3Auth if it’s architecture is more centralized or less documented (even if it does provide a great user workflow and experience).
Furthermore, navigating to the Torus repo GitHub - Web3Auth/Web3Auth: Simple infrastructure that enables Web3 wallets and applications to provide seamless user logins for both mainstream and Web3.0 users., I don’t see any software licenses attached to the software - so what happens if they come out and put a super restrictive/pay for license on their libraries/sdks after you’ve already built it into your workflow.
I think this looks like a promising auth route, just want to make sure I understand all of the pros/cons for any projects I might build before thinking about or using Torus Web3Auth, as well as for others who are reading this thread in the future because they are considering using Torus Web3Auth for their applications.