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
The Registry that lists all Linked Data key types known to the community should include "Secp256k1VerificationKey2018" type, used in Uport specs and Bitcoin specs (page 4)
I suggest we had a 3.4 Secp256k1VerificationKey2018 entry with the example
3.4 Secp256k1VerificationKey2018
{ id: 'did:ethr:b9c5714089478a327f09197987f16f9e5d936e8a#owner', type: 'Secp256k1VerificationKey2018', owner: 'did:ethr:b9c5714089478a327f09197987f16f9e5d936e8a', publicKeyHex: 'b9c5714089478a327f09197987f16f9e5d936e8a' }
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
The Registry that lists all Linked Data key types known to the community should include "Secp256k1VerificationKey2018" type, used in Uport specs and Bitcoin specs (page 4)
I suggest we had a
3.4 Secp256k1VerificationKey2018
entry with the exampleThe text was updated successfully, but these errors were encountered: