Closed nop33 closed 2 weeks ago
Hi @Cali93! Thank you for looking into this issue!
When browsing the Chains List I see that only the 2 examples that we gave above are included:
This is not an exhaustive list, as described by the issue description as well as CAIP2:
That means the full list is:
alephium:0_mainnet
alephium:1_mainnet
alephium:2_mainnet
alephium:3_mainnet
alephium:-1_mainnet
alephium:0_testnet
alephium:1_testnet
alephium:2_testnet
alephium:3_testnet
alephium:-1_testnet
alephium:universal
The list extends with devnet
as an option, but I believe you are not interested in it:
alephium:0_devnet
alephium:1_devnet
alephium:2_devnet
alephium:3_devnet
alephium:-1_devnet
Adding a new chain to the Explorer To get a new chain added to the Explorer, you will need to submit the following:
chains: Alephium's chain id follows this format
alephium + ":" + group + "_" + network_id
where group can be1
,2
,3
or4
which represent individual group, or-1
which represent all groups. The value of network_id could bemainnet
,testnet
ordevnet
. See CAIP2 for more info. Here are a few examples of chain ids:References To ensure timely processing of your request, please provide the following references:
[x] Source of RPC endpoints (e.g. RPC docs):
[x] Source of namespace (if non-EIP155) chain information (particularly chainIds): https://namespaces.chainagnostic.org/alephium/caip2
Additional context Add any other context here.
Please note:
Registering a chain with the Explorer does not impact or improve the ability for wallets and dapps to support your chain. It is simply a way for users to discover wallets and dapps that support your chain by:
It is still up to wallets and dapps to provide concrete support for your chain once it is listed as part of the Explorer.