And the second question: what happens if you use your private key? Every website that uses password has a mechanism to reset your password. Take that feature away you'll lock out millions of users.
And the second question: what happens if you use your private key? Every website that uses password has a mechanism to reset your password. Take that feature away you'll lock out millions of users.
If you lose your private key, you're probably out of luck, but there may be some wallets / platforms that have strategies to mitigate risk, but idk to be honest. So yes, for sensitive applications it is a risk vector, however for users that are already familiar with crypto, it's not really a new risk. If you ever lose your private key or it's compromised you can lose whatever money is in that wallet.
The thing that I like about the infra personally as a solo dev is that using this for authentication for small scale applications on whatever chain I chose is really easy to set up and is a great user experience, and I'm not worried about this as an app developer as my target audience already should be vaguely familiar with how this works.
Everyone using wallets for identity equals everyone just picking a random number to represent themselves (and then classic cryptography allows you to prove to others that you know this number without revealing it).
The hard part of this is not cryptography — that is already solved quite well. It's the human side. People forget pass phrases. Or disclose them to whoever calls them and says they're from Microsoft Pass Phrase Verification Authority. People break computers they haven't backed up. People click "Yes" on security prompts, and open random mail attachments. With private keys involved, these situations are irreversibly catastrophic.
OK. This was literally 100% possible and functioned in 100% the same way a decade ago. A wallet address is just a public key for which you control the private key. Literally nothing about this requires blockchains. When you sign up for a service you say "here is my public key" and then you sign a message providing that you have the private key for that public key to authenticate in the future. Where is the blockchain?
The blockchain is involved for you to be able to make transactions and execute smart contracts, which take your wallet public key and signed message as inputs. So yeah you could use a traditional web app and the only thing you are using is this wallet for authentication purposes if you want, but most apps using this approach are going to natively interact with the blockchain, whether it's a financial app, gaming app, whatever. They're going to be inseparably part of the experience.
But this is literally the same as just "connecting my pgp public key" to some authentication service that manages this. This is no more convenient than the stuff that happens the first time I ssh into a service.
And surprise, passwords crushed this and virtually nobody uses this for consumer applications.
> but most apps using this approach are going to natively interact with the blockchain, whether it's a financial app, gaming app, whatever.
Now the story is very different. You led with "a good use of web3 technologies is auth." Now you say "yeah, auth isn't any better but you might as well do it this way given that your web3 service is using ETH for whatever other hypothetical thing."
For auth though, I agree with you. The only thing new here is that a lot of people have public/private key pairs that never had them before. Maybe this means that adoption is easier but I'm skeptical that this is a meaningful difference over existing signature-based authentication systems.
And I just wanted to say that I personally don't think the whole web will transition to this model, despite me working in the field. The current web isn't really going anywhere, I don't really have pipedreams of everything under the sun getting decentralized, but what I see is the potential for creators to make something cool and it's a neat emerging field to explore as a developer.
And one more time, just because I mentioned it in the first post, ETH is ridiculously expensive right now, but there are alternatives. It's awful for anything other than pretty minor distributed computing currently. There are some really neat projects out there that may be able to get around this by using off-chain distributed computing on ETH, there is a product that I've been meaning to test out as a dev but haven't had the chance yet as I've been focusing in learning the Solana ecosystem for the past few months instead of Ethereum. But it's an emerging space and I think we'll continue to see a lot of innovations over the years; even in the past 2 years we've seen a huge influx of innovative projects.
> Now you say "yeah, auth isn't any better but you might as well do it this way given that your web3 service is using ETH for whatever other hypothetical thing."
Edit - And I did want to reply to this actually. The value I find in this as an authentication method is it does make it incredibly easy as a developer to integrate. I've worked with SSO before that's also super easy as well, however that relies on centralization of trust in an entity such as Google. Even if it is just minor, I do like the idea of being able to provide authentication that:
1. I don't need to store passwords or handle them whatsoever
2. I don't need to rely on an external arbiter of truth such as google / facebook
I have used webauthn a bit, not as a dev, but as an end user and it's really awesome. I would imagine it's not terribly difficult to integrate and would satisfy both of those above desires for my own projects. But yes, in crypto world, might as well use the keypairs everyone already has.