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

Question: Rely on CAIP-2/10 for Namespace and Chain ID #33

Open
jdsika opened this issue Mar 7, 2024 · 1 comment
Open

Question: Rely on CAIP-2/10 for Namespace and Chain ID #33

jdsika opened this issue Mar 7, 2024 · 1 comment

Comments

@jdsika
Copy link

jdsika commented Mar 7, 2024

In the example of the readme you define the ID as:
"id": "did:tz:delphinet:tz1WvvbEGpBXGeTVbLiR6DYBe1izmgiYuZbq",

I am wondering if it might be more consistent to change it to the chain agnostic specification see my draft PR.
CAIP-2 for Chain ID
CAIP-10 for account id

In this case there are two options where the use of an "alias" is not recommended without an external chain registry

"id": "did:tezos:mainnet:tz1WvvbEGpBXGeTVbLiR6DYBe1izmgiYuZbq",
"id": "did:tezos:NetXdQprcVkpaWU:tz1WvvbEGpBXGeTVbLiR6DYBe1izmgiYuZbq",

Most wallet use the Octez --network configurations as alias for the two networks "ghostnet" and "mainnet" but the others change regularily and therefore the use of the actual chain ID might be more useful. Also if we consider that we might have the situation in which we need to resolve the public key by looking up the reveal operation on-chain.

Looking forward to your feedback.

Best regards
Carlo

@jdsika
Copy link
Author

jdsika commented Apr 2, 2024

I see it is defined that way for the did:pkh method: https://github.com/w3c-ccg/did-pkh/blob/main/did-pkh-method-draft.md#syntax-and-interpretation

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

No branches or pull requests

1 participant