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

Support for optional user-hashed names #77

Open
Tracked by #292
decentralgabe opened this issue Dec 19, 2023 · 2 comments
Open
Tracked by #292

Support for optional user-hashed names #77

decentralgabe opened this issue Dec 19, 2023 · 2 comments

Comments

@decentralgabe
Copy link
Member

Consider an additional DNS property for an aka field in the DID Document. This could be a user-hashed name.

The user could 'mine' for a hash that extends their did (e.g. did:dht:example becomes did:dht:example:name). To add this property to their DID document they would find an associated nonce value that hashes to did:dht:example:name and include it in the DNS packet record.

@decentralgabe decentralgabe added enhancement New feature or request specification labels Dec 19, 2023
@decentralgabe decentralgabe self-assigned this Dec 19, 2023
@decentralgabe
Copy link
Member Author

Make sure the alias is user-entered but also a URN. Could look into standardizing this.

@decentralgabe
Copy link
Member Author

@mistermoe unless you think otherwise I am deprioritizing this to a later version of the spec. I believe it can be added as a non breaking extension and not crucial for 1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant