Enhancement API to align with Chain Agnostic Improvement Proposals (CAIPs)

[MASDXI]

Problem description

The current design of CAMARA the blockchainNetworkId proposed format is <L1_Ecosystem>:<sub_id> may face limitations in certain future scenarios, for instance. The ecosystem is going to be complex e.g. rootstock is a sidechain of the bitcoin, it's using evm address format which is also used eip155, another is moonbeam or other parachain are considered to be part of the polkadot ecosystem. Some parachain also support EVM-address, another is the emerging of the layer3 or L3 network such as apechain is built on top of optimism which also eip155 format, Deutsche Bank's L2 that build on zksync also use eip155

Possible evolution

Adopt CAIP-2 for the blockchain identifier and CAIP-10 for blockchain address or account.

Example:

• moonbeam will be polkadot:fe58ea77779b7abda7da4ec526d14db alias eip155:1284:address
• rootstock will be eip155:30:address
• optimism will be eip155:10:address
• evmos will be cosmos:evmos_9000-1:address alias eip155:9000:address
• avalanche will support three formats P-Chain, X-Chain, and C-Chain alias eip155:43114 for C-Chain only.

To ensure compatibility, networks supporting the eip155 format should include an alias.

Additional context

Collaborating with the Chain Agnostic community could help identify widely recognized blockchains and document them on namespace repository.

Supplementary

• List of chains build on zksync https://forum.zknation.io/t/list-of-zk-chains-that-make-up-the-elastic-chain/343
• List of chains build on optimism https://www.superchain.eco/superchain-index
• Polygon CDK building layer3 https://polygon.technology/blog/l3s-v-aggregated-l2s-an-analysis-for-developers

[PedroDiez]

Thanks for the input. This topic will be discussed within the WG.
Initially it will be managed for the MetaRelease Fall25