decentralized-identity
Add support for CACAO -> UCAN delegation
Chain-agnostic Capability Objects (CACAOs) are a way to encapsulate Sign-in with Everything (e.g., Ethereum, Solana etc.) delegations from a did:pkh to any DID. To achieve seamless UX with existing Blockchain wallets (e.g. Ethereum), it is critical to add support for CACAO Delegations in capability chains. This would enable users with existing Blockchain wallets to use their Blockchain wallet to get access to their DWN.
What are the working definitions of "Web3" and "Web3 wallet"? Please link to the relevant specification(s) (whether RFC, DIF spec, W3C REC, or otherwise).
What are the working definitions of "Web3" and "Web3 wallet"? Please link to the relevant specification(s) (whether RFC, DIF spec, W3C REC, or otherwise).
There is no need to add any language to the spec that mentions Web3.
The issue is about supporting a UX flow where the user uses an Ethereum, Solana etc. crypto wallet. CACAOs define a model where such a crypto wallet can temporarily delegate access through Sign-in with Ethereum, Solana to a temporary, limited-scope and short-lived key/DID. This delegation can be represented as a CACAO. CACAOs are like ZCap/UCAN delegations. The issue is about adding support for CACAOs as an option for delegations. It should be possible to combine them with the current model. The advantage is that the Ethereum, Solana etc. user does not need to install additional software to interact with the DWN which would have been a major blocker in a certain market.
@awoie -- Your original comment spoke of requirements "To achieve seamless UX in Web3" and to "enable users with existing Web3 wallets to use their Web3 wallet".
If "Web3" is not relevant to those original sentences, then they should be rewritten to remove that element from consideration, and replace it with something that is relevant.
If "Web3" is relevant to those original sentences, then it must be defined (as, to my current understanding, it has not been rigorously defined anywhere, though it is being flung about on Twitter and the like), in order for anyone to understand the issue you are raising.
@TallTed I get your point that web3 is an overloaded and not well-defined term if this was your concern.
