1. The barrier is using a wallet of some kind. For me this difficulty kind of goes both ways - one, we've primed everyone already to expect to "sign up" for an

1. The barrier is using a wallet of some kind. For me this difficulty kind of goes both ways - one, we've primed everyone already to expect to "sign up" for an account as it is, but in this realm they only need a wallet(a one-time operation). You go to a web3 site and click "connect wallet", approve, and that's it. In order to actually _do_ anything in terms of mutating your wallet's state, you have to willingly accept the transaction. 2. Impersonation depends on the application in question. It is a subject with a lot of attention, and I've seen varying proposed solutions for "proof of uniqueness". This is a good jumping off point imo: https://www.microsoft.com/en-us/security/business/identity-access-management/decentralized-identity-blockchain https://www.microsoft.com/en-us/security/business/identity-a... 3. This is where things diverge sharply from "web2". There is no "forgot password" or support infrastructure that can come to the rescue. At this current moment you are screwed. But there are some promising ideas that could address this - look into "social recovery".