Crypto in this case is also being used as an authentication / password replacement system. Signing with your wallet address proves you are a specific person. So that alone is a great reason to include the wallet.
>> Signing with your wallet address proves you are a specific person. So that alone is a great reason to include the wallet.
No, it doesn't. It just proves that you own/hold a private key. You need to build an identity protocol on top of that if you want to prove that you are a specific person/organization. Such protocols have been around for quite some time before crypto currencies. It's just they don't have a good UX, that's why most websites require a password based authentication instead of a key/certificate.
I like a lot JWT/JWT as it has a lot of useful attributes(. e.g the "acr" attribute) so you better start with that than a crypto wallet
I think they meant to say a specific "account" rather than getting into person-hood.
I have been wanting what the op describes for a long time - why do we have to "create" accounts? Why can't we simply tell the site our account with our request. For a dumb example, having "?publicKey=(key)" in the url. That way the site can know who we are and be able to link our profile, provable by our ability to sign using the private key, does away with login forms, does away with password recovery flow, does away with email single-point-of-failure, allows us to switch profiles easily, etc. It's mind-boggling that every site in the world rebuilds login logic.
Your statement makes me very curious because as far as I'm aware, key distribution is the core problem of asymmetric cryptography. I can generate a private key and say I'm you, and there's nothing stopping me from doing that.
The only solution I'm aware of so far is DNSSec which starts from the operating system level.
I'm not sure how I feel about tying authentication with payment. It means anywhere you log into with this address knows your payment history with this wallet.
