Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why two identities? #1

Open
FabioPinheiro opened this issue Sep 25, 2023 · 1 comment
Open

Why two identities? #1

FabioPinheiro opened this issue Sep 25, 2023 · 1 comment

Comments

@FabioPinheiro
Copy link

My only point against this did:peer:4 is why complicate everything else with two identities. Other than that I love the idea.

IMO is complicated enough controlling one identity and here we are proposing to identities that come always in pairs:

did:peer:4{{hash}}:{{encoded document}}
did:peer:4{{hash}}

Was it considered to use DID query?
Note the the query part of a DID is not part of the identity! On the contrary of DID path.
(The DID fragment is also not part of the identity but can't be used on the DID Comm message field id.)

did:peer:4{{hash}}?doc={{encoded document}} <=> did:peer:4{{hash}}
Those two are equivalent in terms of identity. According to the DID core specs they are one identity.

@dbluhm
Copy link
Member

dbluhm commented Sep 25, 2023

I recommend raising this discussion on: decentralized-identity/peer-did-method-spec#61

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants