It has been widely observed that web3 offerings are hobbled by the user loss at the very first steps of the onboarding process: authentication and wallet formation.
It seems wise, when introducing a new application to a new user for them to onboard in the simplest, well known way to them. So, Google oauth, etc, and wallet handled centrally. But then in a period of time, the user should get emails with instructions to take control of their identity and wallet.
Web3 ventures can do this for themselves, but what if this was something handled for them by a specialist in that onboarding and transfer procedure? What would a pluggable Progression service look like?
It has been widely observed that web3 offerings are hobbled by the user loss at the very first steps of the onboarding process: authentication and wallet formation.
It seems wise, when introducing a new application to a new user for them to onboard in the simplest, well known way to them. So, Google oauth, etc, and wallet handled centrally. But then in a period of time, the user should get emails with instructions to take control of their identity and wallet.
Web3 ventures can do this for themselves, but what if this was something handled for them by a specialist in that onboarding and transfer procedure? What would a pluggable Progression service look like?
The Problem
How does it work?
Existing Work
Fit and Fitness
Assumptions