ETHDenver is the largest live-action experiment in Web3. From the ground up, we have included Web3 in just about every elemet of our tech stack. However, we recognize that there is a wide range of experience levels within our community, as well as a wide-range of user experience with the integrations we build into our tech stack.
That being said, we’ve explored the ability to allow new members in our ecosystem to create a wallet using their Gmail accounts, however, we ran into a few problems that took away time from our small staff when they had to work on other problems. It’s a free-to-attend event, which naturally has some limitations, mostly balancing time and money without over/under engineering.
To solve the email login, some wallets were using a Web3Auth key provided by ETHDenver. It was a feature that the ETHDenver team would have to pay for. While we want to make the onboarding and ticketing process easy for all of our DAO members, we would have to pay all of the monthly active members going forward.
Every application that we have would have had to be updated to provide support to be able to sign messages from Web3Auth and Torus. Account abstraction is a fabulation we tell ourselves is solved, yet we made it harder.
Web3Auth is a tremendous tool for connecting, but not for signing/interacting and staking (i.e., reading vs writing).
New members were pigeonholed to have to become power members to figure it out and it negated the whole experience to begin with. That being said, we decided to move away from Web3Auth and toward technology that is easier for interacting/ signing.
If you were an attendee who used Web3Auth before it was removed, please read this article.