The reason is: With private key auth alone, you don’t have identity, just a non-human readable public key, and no universally known exclusive association with a particular username. With OpenID or WebAuthn or any of that, you would still need a company or org to keep a centralized database of everyone’s credentials and user info. With Blockchain you don’t: As long as the Ethereum blockchain keeps going, your info (username: “johndoe.eth” public_key: “420abc” avatar: “some HTTP or IPFS url”) will stay stored. This is the exact precise thing blockchains are unusually good at doing, and given how much people these days are hating on big tech companies managing their identities and harvesting data in the process, “SSO with no company attached” seems like a thing people actually want.
I’m still highly skeptical of art NFTs and crypto as currency and lots of other blockchain stuff, but in this one case they’ve won me over. This seems legit.
Someone else posts into the blockchain that jondoe.eth public_key "420abc..." is {this real data about the person}.
And now that identity and every login it is associated with has been doxed in a permeant, public, and unalterable way.
If someone doxes my gmail account, I can go through the process of dissociating myself with that identity and hopefully the provider were that doxing is stored could be persuaded to delete that content (yes, the internet has a long memory).
This would seem to be much harder if not impossible with an identity stored on a public blockchain (that also allows for other data to be stored).
Also it’s up to you how you use the system. You could have a number of online persona’s each with it’s own login.
This is about having a public, centralized source of identities that cannot be erased.
Yes, you can have multiple identities on it - but if an identity on that chain is doxed, it is forever doxed.
If you are maintaining one identity per application... then what is the advantage of having the identity in a place where it can be accessed by multiple applications?
I have difficulty seeing the advantage of a public, append only, identity provider compared to say... setting up your own auth server on AWS and managing your identities out of there.