Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

ltox: Cross-chain DIDs #116

Closed
jasny opened this issue Aug 13, 2021 · 0 comments · Fixed by #150
Closed

ltox: Cross-chain DIDs #116

jasny opened this issue Aug 13, 2021 · 0 comments · Fixed by #150
Assignees

Comments

@jasny
Copy link
Member

jasny commented Aug 13, 2021

By default, an LTO identity node will only resolve DIDs based on LTO network addresses. It's possible to configure the service to index DIDs based on addresses of other blockchains, like Ethereum or Bitcoin.

DIDs with the method "ltox" can be resolved by LTO Network identity nodes that support cross-chain identifiers.

The method-specific string is comprised of a CAIP-2 blockchain ID and an address on that specific chain.

did:ltox:eip155:1:0xab16a96d359ec26a11e2c2b3d8f8b8942d5bfcdb

ltox-did = "did:ltox:" chain-id ":" address
chain-id = chain-namespace + ":" + chain-reference
chain-namespace = {3,16}\*( ALPHA / DIGIT )
chain-reference = {1,47}\*( ALPHA / DIGIT )
address = {1,63}\*( ALPHA / DIGIT )

The method-specific string is case-sensitive.

Supported chains

Currently, only eip155 is supported. This address scheme is used by Ethereum and other EVM-based blockchains like Binance Smart Chain.

See documentation

Also see https://github.com/ChainAgnostic/CAIPs


You should be able to configure which chains to index. Initially, you can only configure eip155.

The following config will index DIDs for Ethereum and Binance chain.

{
    "cross_chain": ["eip155:1", "eip155:56"]
}

When indexing, check the key type. For instance for eip155, only index sep256k1 keys.

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

Successfully merging a pull request may close this issue.

2 participants