Skip to content
New issue

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

Register verification methods #51

Open
sbihel opened this issue Dec 16, 2020 · 3 comments
Open

Register verification methods #51

sbihel opened this issue Dec 16, 2020 · 3 comments
Labels
developer experience Make nicer and easier to use for developers did:tz

Comments

@sbihel
Copy link
Member

sbihel commented Dec 16, 2020

We need to register the tz1/tz2/tz3 verification methods so we could refer to them satisfying LD-Proofs? E.g., Ed25519PublicKeyBLAKE2BDigestSize20Base58Encoded2020.

It looks to me like the way to register a proof type is to create a specification for it, like https://w3c-ccg.github.io/lds-ed25519-2020/, and then make a PR adding it to security vocab, e.g. w3c-ccg/security-vocab#66


Related to #49

@sbihel sbihel added the did:tz label Dec 16, 2020
@wyc
Copy link
Contributor

wyc commented Dec 22, 2020

Some recent feedback:

  • Ed25519PublicKeyBLAKE2BDigestSize20Base58Encoded2020 should be renamed to Ed25519PublicKeyBLAKE2BDigestSize20Base58CheckEncoded2020, and should include the public key in the proof object due to EdDSA not supporting a function like ecrecover that can recover the public key from a payload and signature.

@clehner
Copy link
Contributor

clehner commented Dec 29, 2020

I just noticed this: Linked Data Cryptographic Suite Registry / Registration process.

It looks like maybe a more appropriate place for proof/key types. But adding to security-vocab might be good too.

@wyc
Copy link
Contributor

wyc commented Feb 22, 2021

N.B. Let's go with Ed25519PublicKeyBLAKE2BDigestSize20Base58CheckEncoded2021 to avoid confusion.

@clehner clehner added the developer experience Make nicer and easier to use for developers label Apr 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer experience Make nicer and easier to use for developers did:tz
Projects
None yet
Development

No branches or pull requests

3 participants