Nearchos

Found this interesting suggestion of how to build DIDs architecture. This is a scheme from an article called "A trustworthy architecture for Web3 service" written by Yuki Yasuno, Ryo Tateishi, Ranmaru Shiroishi and Shigeru Hosono, 2024.

They are solving the following issues:
1) saving users from the decision taking on what web3 services to uses and by doing it eliminating the security issues
2) keeping all personal data on the user side and by doing that removing risk of losing personal data which is held by centralized providers.

Their idea is to have this brokerage system, where credentials (DID) of a user is confirmed by broker and then the service provided is chosen by that from a list of available web3 service providers.

Looking at this I still have one question tho... Isn't that brokerage part not centralized too? 🤔

good real-world example of how embedded wallets break identity

web3 becoming web2 but instead of email/passwords its now app-specific wallets (identities)

to fix, 1) devs must implement one-to-many identity mapping in thier app and, 2) users need to do the work of mapping (which they wont) *in every web3 app they use*

is this really a better ux than pasting a seed phrase in a pw manager? is this progress? 

given lack of web3 consumer growth the market says no

The web3 Identity crisis is real. Which is interesting considering web3 seems tailor-made for solving this problem as well!

The web3 Identity crisis is real. Which is interesting considering web3 seems tailor-made for solving this problem as well!

https://warpcast.com/nonlinear.eth/0x7763a1e8