You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
When indexing, check the key type. For instance for eip155, only index sep256k1 keys.
The text was updated successfully, but these errors were encountered: