|
|
|
|
|
by bawolff
1423 days ago
|
|
Are blockchain people physically incapable of speaking plainly? Its hard to cut theough the buzzword bullshit, but this sounds like they reinvented PKI and added 10 billion layers of indirection. Is there more to it than that? Or is this really just taking the latest technogies of the 1990s, and explaining it badly so people think they have invented something new? |
|
While I agree that blockchain technologies can quickly fall in bullshit buzzwords, there is still food for thoughts here, but you have to be somewhat familiar with the subject to understand it.
Let me try to explain it from software engineer to software engineer.
The core of web 5 is "self sovereign identity" . That means you (the user) gets to be in control of authentication, identification, and user data access and lifecycle.
Take a typical web 2.0 worflow:
- You sign up on a website / app by providing mail, password, and some other user data like address, phone, etc.
- The website / app stores your information + their own metadata (admin flag, purchase history, whatever) in their database somehow.
- When you log in, you are given a JWT which basically is just a subset of the data you provided + the website metadata, along with a signature to ensure you're not forging all that.
- The website / app have you perform API calls providing the JWT.
The whole idea of self sovereign identity is that you don't need the website / app to own any of your data and metadata in the first place.
If your data is stored in a place _you_ control, and where _you_ can delegate read access to them, as well as the capability for them to enhance it with their metadata that they can sign, then you can pretty much get rid of them storing anything at all about you.
This place where you store your data is a blockchain dedicated for that purpose. You can have all your information stored there, encrypted, and just encrypt for their public key what you are willing to share with them. If you don't want them to know you anymore, just remove the version of your data encrypted for them.
If they need to store additional metadata on you (say an "is_admin" flag), have them store it in your wallet and sign it.
You can pretty much see it as a blockchain of persistent JWT claims that you control. These claims would be accessed through a browser plug-in a-la-metamask.
The overall idea is that by switching to this model, websites / apps will become 99% front-end only, APIs will switch to smart contracts, and you will have total control of your data.
Hope that clarifies a bit the jargon of the article.