-
Notifications
You must be signed in to change notification settings - Fork 15
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
Tezos DID-Method #2564
Comments
Hello |
To clarify: It is actually two different topics
|
I think the did:tezos method is dead, nobody uses did:tezos in practice. |
That would be worth a try:
|
we already have it in jwt_vc_json format , we can change te credntialSubject.id and fix the "sub" which is incorrect in that one... but it will require you to change the protocol to use OIDC4VP as this model is not supported by the previous protocol that is what we have today |
I think I have to discuss this with @jfelixh Are you sure it cannot be used with json-ld - did you test it? |
The only lib we have to sign with did:pkh and jdon ld on flutter is the one provided by Spruce and it looks like they do not maintain it anymore. So the did:pkh is still the previous version with did:pkh:tz1 and no chain id |
The Tezos-DID Method document is not maintained anymore see here.
! There is a call for maintainers !
It came up because I was updating the Chain Agnostic improvement proposals mentioned in #2523 for CAIP-2/10/122 and I realized that the Tezos DID URN was not correctly used in the credentials mentioned here.
After stating this in my issue I did also encounter the following w3c did-pkh-method-draft which correctly gives the examples like e.g.:
did:pkh:tezos:NetXdQprcVkpaWU:tz1TzrmTBSuiVHV2VfMnGRMYvTEPCP42oSM8
instead of currently incorrectly:
did:pkh:tz:tz1TzrmTBSuiVHV2VfMnGRMYvTEPCP42oSM8
The difference is that we should use the CAIP-10 compliant account-id correctly including the chain id
I think the correct way of the urn should be supported as well in Altme.
Best regards
Carlo
The text was updated successfully, but these errors were encountered: