Closed awoie closed 5 years ago
I agree this fixes #56 and #201 .
Per discussion in 2019-05-30 DID Spec and DID Resolution Spec meeting, @awoie will update this PR to say that a public key property MUST be in the Linked Data Cryptographic Suite Registry.
@peacekeeper @rhiaro updated the PR and I hope that resolves the issue.
(updated) Please note, the information in the note section refers to what the SSI community has in use rather than the registry itself. This is reasonable as the registry is not well maintained atm (but we want to change that) and as far as I know some of the other public key properties are not yet included as well, e.g., publicKeyJwk.
Merging per decision in 2019-06-06 DID Spec and DID Resolution Spec meeting.
This PR addresses the immediate need to support public keys as Ethereum addresses and removes constraints on public keys in general. This will ensure that any entry in the referenced registry (once final) can be used to describe the key types and formats.
Preview | Diff