We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm confused by the implementation of the eddsa Multikey that this test suite assumes. Both according to https://github.com/multiformats/multicodec/blob/master/table.csv and https://w3c-ccg.github.io/did-method-key/#signature-method-creation-algorithm the prefix for an ed25519 public key is 0xed, but the implementation here (incorrectly, I'd say?) assumes a prefix of 0xed, 0x01 resulting in a hard-coded assertion that did:key DIDs must begin with z6Mk. Can you clarify where this extra byte is coming from?
0xed
0xed, 0x01
did:key
z6Mk
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm confused by the implementation of the eddsa Multikey that this test suite assumes.
Both according to https://github.com/multiformats/multicodec/blob/master/table.csv and https://w3c-ccg.github.io/did-method-key/#signature-method-creation-algorithm the prefix for an ed25519 public key is
0xed, but the implementation here (incorrectly, I'd say?) assumes a prefix of0xed, 0x01resulting in a hard-coded assertion thatdid:keyDIDs must begin withz6Mk. Can you clarify where this extra byte is coming from?The text was updated successfully, but these errors were encountered: