Agreed, it’s much the same as OIDC.
Tho personally, beyond GitHub for dev related sites, I won’t use them.
If anything it enables “websites” to be simpler, smaller.
A UI atop a single function.
Without the bloat. Without the “we must do enough to show value to get users to sign up”.
I just auth, use it, and move on with my life.
Sometimes there’s a fee per use. Sometimes that value is exchanged somewhere else in the transaction. But either way, I got what I needed and I’m done.
Web3 is everything we wanted out of auth for the last decade or so.
I don't disagree that having a keypair on the client for authentication is a cool idea, but it's hardly specific to "Web3" (e.g. https://developer.apple.com/documentation/authenticationserv...).
I do see the value in being able to bring an identity around and store it in a blockchain, but... extreme fragmentation is a bummer.
Easiest by what measure? As I understand it, few browsers (read: only one or two) have built in wallets and outside of that the UX for this auth isn’t great. It’s hard to see how this is better/easier to use than existing OIDC/"Sign In With X" solutions.