-
Notifications
You must be signed in to change notification settings - Fork 802
Open
Labels
Description
Adding a new chain to the Explorer
To get a new chain added to the Explorer, you will need to submit the following:
- JSON-RPC spec for Wallets (only if one doesn't already exist). For more information, please review the Ethereum JSON-RPC API docs.
GitHub Link: N/A (Uses standard Ethereum JSON-RPC API) - Write a CASA namespace spec if not already available for this namespace.
GitHub Link: N/A (Uses existing eip155 namespace) - namespaces: eip155
*known chain namespaces (e.g. eip:155 for Ethereum/EVM-based chains, solana, ...) - chains:
*known chains, where the primary key is a compound key composed of namespace + reference (e.g. ETH mainnet is eip155:1).
Please provide labels for each chain (e.g. mainnet, testnet, devnet, ...)
eip155:4352 - MemeCore Mainnet
eip155:43521 - Formicarium MemeCore Testnet - RPC endpoints:
*list of common/canonical RPC endpoints for the chain(s)
[ChainID:4352] MemeCore Mainnet: https://rpc.memecore.net
[ChainID:43521] Formicarium MemeCore Testnet: https://rpc.formicarium.memecore.net - SLIP-0044 coin type:
* slip44 coin type used in the namespace
60 (EVM compatible)
References
To ensure timely processing of your request, please provide the following references:
- Source of RPC endpoints (e.g. RPC docs):
https://chainlist.org/chain/4352
https://chainlist.org/chain/43521 - Source of namespace (if non-EIP155) chain information (particularly chainIds):
eip155
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:
- Browsing the Chains List
- Filtering results programmatically via the Explorer API
It is still up to wallets and dapps to provide concrete support for your chain once it is listed as part of the Explorer.
- I have read and understood the above clarification