chains/README.md

100 lines
2.9 KiB
Markdown
Raw Normal View History

2018-12-20 17:57:42 +00:00
# EVM-based Chains
2021-04-13 07:50:30 +00:00
The source data is in _data/chains. Each chain has its own file with the filename being the [CAIP-2](https://github.com/ChainAgnostic/CAIPs/blob/master/CAIPs/caip-2.md) representation as name and `.json` ans extension.
2018-12-20 20:43:59 +00:00
2019-04-02 13:00:00 +00:00
## Example
2019-02-08 23:20:14 +00:00
```json
2018-12-20 20:43:59 +00:00
{
"name": "Ethereum Mainnet",
"chain": "ETH",
"network": "mainnet",
2019-04-02 13:00:00 +00:00
"rpc": [
"https://mainnet.infura.io/v3/${INFURA_API_KEY}",
"https://api.mycryptoapi.com/eth"
],
"faucets": [],
2019-07-02 10:02:07 +00:00
"nativeCurrency": {
"name": "Ether",
"symbol": "ETH",
"decimals": 18
},
"infoURL": "https://ethereum.org",
2019-07-02 10:02:07 +00:00
"shortName": "eth",
"chainId": 1,
2021-04-13 07:50:30 +00:00
"networkId": 1,
"icon": "ethereum",
"explorers": [{
"name": "etherscan",
"url": "https://etherscan.io",
"icon": "etherscan",
"standard": "EIP3091"
}]
2018-12-20 20:43:59 +00:00
}
```
2021-03-14 15:24:22 +00:00
2021-04-13 07:50:30 +00:00
when an icon is used in either the network or a explorer there must be a json in _data/icons with the name used (e.g. in the above example there must be a `ethereum.json` and a `etherscan.json` in there) - the icon jsons look like this:
```json
[
{
2022-03-07 06:07:25 +00:00
"url": "ipfs://QmdwQDr6vmBtXmK2TmknkEuZNoaDqTasFdZdu3DRw8b2wt",
2021-04-13 07:50:30 +00:00
"width": 1000,
"height": 1628,
"format": "png"
}
]
```
where:
* the URL must be a IPFS url that is publicly resolveable
* width and height are optional - but when one is there then the other must be there also
* format is either "png", "jpg" or "svg"
If the chain is an L2 or a shard of another chain you can link it to the parent chain like this:
```json
{
...
"parent": {
"type" : "L2",
"chain": "eip155-1",
"bridges": [ {"url":"https://bridge.arbitrum.io"} ]
}
}
```
where you need to specify type 2 and the reference to an existing parent. The field about bridges is optional.
2022-03-07 06:07:25 +00:00
## Aggregation
2021-04-13 07:50:30 +00:00
There are also aggregated json files with all chains automatically assembled:
* https://chainid.network/chains.json
* https://chainid.network/chains_mini.json (miniaturized - fewer fields for smaller filesize)
2021-07-25 05:33:45 +00:00
## Collision management
If different chains have the same chainID we list the one with the oldest genesis.
2021-03-14 15:24:22 +00:00
## Usages
2021-03-26 10:51:40 +00:00
* [chainlist.org](https://chainlist.org) or [networklist-org.vercel.app](https://networklist-org.vercel.app) as a staging version with a more up-to-date list
2021-03-14 15:24:22 +00:00
* [chainid.network](https://chainid.network)
* [WallETH](https://walleth.org)
* [TREZOR](https://trezor.io)
2021-04-15 06:24:15 +00:00
* [networks.vercel.app](https://networks.vercel.app)
* [eth-chains](https://github.com/taylorjdawson/eth-chains)
2022-01-04 10:52:15 +00:00
* [EVM-BOX](https://github.com/izayl/evm-box)
* [FaucETH](https://github.com/komputing/FaucETH)
2022-01-28 14:57:48 +00:00
* [Sourcify playground](https://playground.sourcify.dev)
* [chaindirectory.xyz](https://www.chaindirectory.xyz)
* [chain-list.org](https://chain-list.org)
2022-03-06 14:27:34 +00:00
* [DefiLlama's chainlist](https://chainlist.defillama.com/)
2022-03-07 06:07:25 +00:00
* [chainlist.network](https://chainlist.network/)
* [evmchainlist.org](https://evmchainlist.org)
* [evmchainlist.com](https://evmchainlist.com)
2021-03-14 15:24:22 +00:00
* Your project - contact us to add it here!