Skip to content
This repository has been archived by the owner on Oct 29, 2019. It is now read-only.

Fix #201 and #56 -- Added support for public keys as Ethereum addresses #202

Merged
merged 4 commits into from
Jun 7, 2019

Conversation

awoie
Copy link

@awoie awoie commented May 24, 2019

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

index.html Outdated Show resolved Hide resolved
@peacekeeper
Copy link
Member

I agree this fixes #56 and #201 .

@peacekeeper peacekeeper self-requested a review May 30, 2019 15:29
@peacekeeper
Copy link
Member

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.

@awoie
Copy link
Author

awoie commented Jun 6, 2019

@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.

@peacekeeper
Copy link
Member

peacekeeper commented Jun 7, 2019

Merging per decision in 2019-06-06 DID Spec and DID Resolution Spec meeting.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants