generated from TBD54566975/tbd-project-template
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Labels
Comments
Make sure the alias is user-entered but also a URN. Could look into standardizing this. |
@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
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
becomesdid:dht:example:name
). To add this property to their DID document they would find an associated nonce value that hashes todid:dht:example:name
and include it in the DNS packet record.The text was updated successfully, but these errors were encountered: