[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-7188":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":17,"compositeScore":19,"rankGlobal":10,"rankLanguage":10,"license":20,"archived":21,"fork":21,"defaultBranch":22,"hasWiki":21,"hasPages":23,"topics":24,"createdAt":10,"pushedAt":10,"updatedAt":30,"readmeContent":31,"aiSummary":32,"trendingCount":16,"starSnapshotCount":16,"syncStatus":33,"lastSyncTime":34,"discoverSource":35},7188,"chains","ethereum-lists\u002Fchains","ethereum-lists","provides metadata for chains","https:\u002F\u002Fchainid.network",null,"Kotlin",9828,8041,557,29,0,1,4,41,"MIT License",false,"master",true,[25,5,26,27,28,29],"chainid","eip155","ethereum","evm","hacktoberfest","2026-06-12 02:01:35","# EVM-based Chains\n\nThe source data is in _data\u002Fchains. Each chain has its own file with the filename being the [CAIP-2](https:\u002F\u002Fgithub.com\u002FChainAgnostic\u002FCAIPs\u002Fblob\u002Fmaster\u002FCAIPs\u002Fcaip-2.md) representation as name and `.json` as extension.\n\n## Example:\n\n```json\n{\n  \"name\": \"Ethereum Mainnet\",\n  \"chain\": \"ETH\",\n  \"rpc\": [\n    \"https:\u002F\u002Fmainnet.infura.io\u002Fv3\u002F${INFURA_API_KEY}\",\n    \"https:\u002F\u002Fapi.mycryptoapi.com\u002Feth\"\n  ],\n  \"faucets\": [],\n  \"nativeCurrency\": {\n    \"name\": \"Ether\",\n    \"symbol\": \"ETH\",\n    \"decimals\": 18\n  },\n  \"features\": [{ \"name\": \"EIP155\" }, { \"name\": \"EIP1559\" }],\n  \"infoURL\": \"https:\u002F\u002Fethereum.org\",\n  \"shortName\": \"eth\",\n  \"chainId\": 1,\n  \"networkId\": 1,\n  \"icon\": \"ethereum\",\n  \"explorers\": [{\n    \"name\": \"etherscan\",\n    \"url\": \"https:\u002F\u002Fetherscan.io\",\n    \"icon\": \"etherscan\",\n    \"standard\": \"EIP3091\"\n  }]\n}\n```\n\nWhen an icon is used in either the network or an explorer, there must be a JSON in _data\u002Ficons with the name used.\n(e.g. in the above example there must be a `ethereum.json` and a `etherscan.json` in there) - The icon JSON files look like this:\n\n```json\n\n[\n    {\n      \"url\": \"ipfs:\u002F\u002FQmdwQDr6vmBtXmK2TmknkEuZNoaDqTasFdZdu3DRw8b2wt\",\n      \"width\": 1000,\n      \"height\": 1628,\n      \"format\": \"png\"\n    }\n]\n\n```\n\nwhere:\n * The URL MUST be publicly resolvable through IPFS\n * width and height MUST be positive integers\n * format is either \"png\", \"jpg\" or \"svg\"\n * size MUST be less than 250kb\n\nIf the chain is an L2 or a shard of another chain you can link it to the parent chain like this:\n\n\n```json\n{\n  ...\n  \"parent\": {\n   \"type\" : \"L2\",\n   \"chain\": \"eip155-1\",\n   \"bridges\": [ {\"url\":\"https:\u002F\u002Fbridge.arbitrum.io\"} ]\n  }\n}\n```\n\nwhere you need to specify the type and the reference to an existing parent. The field about bridges is optional.\n\nYou can add a `status` field e.g. to deprecate (via status `deprecated`) a chain (a chain should never be deleted as this would open the door to replay attacks)\nOther options for `status` are `active` (default) or `incubating`\n\n## Aggregation\n\nThere are also aggregated json files with all chains automatically assembled:\n * https:\u002F\u002Fchainid.network\u002Fchains.json\n * https:\u002F\u002Fchainid.network\u002Fchains_mini.json (miniaturized - fewer fields for smaller filesize)\n\n## Constraints\n\n * the shortName and name MUST be unique - see e.g. EIP-3770 on why\n * if referencing a parent chain - the chain MUST exist in the repo\n * if using an IPFS CID for the icon - the CID MUST be retrievable via `ipfs get` - not only through some gateway (means please do not use pinata for now)\n * for more constraints you can look into the CI\n\n## Collision management\n\n We cannot allow more than one chain with the same chainID - this would open the door to replay attacks.\n The first pull request gets the chainID assigned. When creating a chain we can expect that you read EIP155 which states this repo.\n All pull requests trying to replace a chainID because they think their chain is better than the other will be closed.\n The only way to get a chain reassigned is when the old chain gets deprecated. This can e.g. be used for testnets that are short-lived. But then you will get the redFlag \"reusedChainID\" that should be displayed in clients to warn them about the dangers here.\n\n## Getting your PR merged\n### before PR is submitted\n\nBefore submitting a PR, please ensure all checks pass by running:\n\n```bash\n$ .\u002Fgradlew run\n\nBUILD SUCCESSFUL in 7s\n9 actionable tasks: 9 executed\n```\n\nAdditionally, run Prettier to format your JSON according to the style [defined here ](https:\u002F\u002Fgithub.com\u002Fethereum-lists\u002Fchains\u002Fblob\u002Fmaster\u002F.prettierrc.json)\ne.g. run\n\n```\nnpx prettier --write _data\u002F*\u002F*.json\n```\n\n### Once PR is submitted\n\n * Make sure CI is green. There will likely be no review when the CI is red.\n * When making changes that fix the CI problems - please re-request a review - otherwise it is too much work to track such changes with so many PRs daily\n\n## Usages\n### Tools\n * [MESC](https:\u002F\u002Fparadigmxyz.github.io\u002Fmesc)\n\n### Explorers\n * [Otterscan](https:\u002F\u002Fotterscan.io)\n\n### Wallets\n * [WallETH](https:\u002F\u002Fwalleth.org)\n * [TREZOR](https:\u002F\u002Ftrezor.io)\n * [Minerva Wallet](https:\u002F\u002Fminerva.digital)\n\n### EIPs\n * EIP-155\n * EIP-3014\n * EIP-3770\n * EIP-4527\n\n### Listing sites\n * [chainid.network](https:\u002F\u002Fchainid.network) \u002F [chainlist.wtf](https:\u002F\u002Fchainlist.wtf)\n * [chainlist.org](https:\u002F\u002Fchainlist.org)\n * [Chainlink docs](https:\u002F\u002Fdocs.chain.link\u002F)\n * [dRPC Chainlist - Load-balanced public nodes](https:\u002F\u002Fdrpc.org\u002Fchainlist)\n * [eth-chains](https:\u002F\u002Fgithub.com\u002Ftaylorjdawson\u002Feth-chains)\n * [EVM-BOX](https:\u002F\u002Fgithub.com\u002Fizayl\u002Fevm-box)\n * [evmchain.info](https:\u002F\u002Fevmchain.info)\n * [evmchainlist.org](https:\u002F\u002Fevmchainlist.org)\n * [networks.vercel.app](https:\u002F\u002Fnetworks.vercel.app)\n * [Wagmi compatible chain configurations](https:\u002F\u002Fspenhouet.com\u002Fchains)\n * [chainlist.simplr.sh - Info packaged single pager](https:\u002F\u002Fchainlist.simplr.sh)\n\n### Other\n * [FaucETH](https:\u002F\u002Fgithub.com\u002Fkomputing\u002FFaucETH)\n * [Sourcify playground](https:\u002F\u002Fplayground.sourcify.dev)\n * [Smart Contract UI](https:\u002F\u002Fxtools-at.github.io\u002Fsmartcontract-ui)\n\n * Your project - contact us to add it here!\n","ethereum-lists\u002Fchains 项目提供了基于EVM的区块链元数据。该项目使用Kotlin语言编写，通过JSON格式存储每条链的关键信息，如名称、链ID、RPC节点、原生货币等，并支持为链和探索器添加图标。它还能够定义链的状态（如活跃、孵化或废弃）以及处理L2链与主链的关系。适用于需要获取或展示不同EVM兼容链详细信息的应用场景，比如钱包服务、区块链浏览器或其他依赖于链元数据的服务。",2,"2026-06-11 03:11:05","top_language"]