decentralized-identity / decentralized-identity/did-dht
Support for optional user-hashed names
Open
did-dht-2.0
enhancement
hacktoberfest
large
specification
- Dominant language
- Go
- Stars
- 42
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
Assessment
This issue has not been assessed yet.