Conversation

Replying to and
2/ A single organization should not have the sole discretion as to what kinds of data sharing are supported for billions of people, especially if they have interests competing with those of their users.
2
32
3/ The user and the accessed service should be the only parties who need to agree on what data are shared and how to share them. Unbundling the Login gets us there by allowing the user to assemble their own end-to-end login experience without an intermediary.
1
23
4/ We break down the login into its core components, starting with extensible key-based authentication. Then it’s built back up, allowing us to surpass the state of the art by creating open interfaces and therefore opportunities for innovations along each part of the stack.
1
22
5/ To get there, the easiest path is for end users to use private keys. With blockchains as the most successful key adoption event ever, we can evolve their use past just on-chain transactions to explore an entire universe of key-controlled interactions.
2
26
7/ We can move from users logging into platforms to platforms logging into users’ data vaults.
5
29
SIWE abstracts over wallets, so it’s however the wallet decides to handle it, whether it’s multisigs, smart contract wallets, social recovery, trusted custodians, etc. Key recovery has come a long way due to wallet/exchange security advancements!
2
8
Show replies
Replying to and
We need to separate the wallet from identity and any other digital asset you want to share with the public. As a first step, it could be a code clone of a wallet with a different metaphor. It would lead to similar functionality but hacker safe restrictions.
1
2
I should also state, I don't think a "vault" is the correct metaphor, I wouldn't want to share access to my real life vault to prove my identity. Another contradiction is making off chain data at the core of web3 identity, it's just a restart & ultimately a replay of web2 ID
2