Instadapp/chains
1
0
Fork 0
mirror of https://github.com/Instadapp/chains.git synced 2024-07-29 22:37:19 +00:00
Code Issues Packages Projects Releases Wiki Activity
provides metadata for chains
761 Commits 320 Branches 7 Tags 66 MiB
Kotlin 94.2%
JavaScript 5.8%
71bbadb687
Go to file
ammar-lakho 71bbadb687
Add more RPCs for Zenith Mainnet (#1169) 
* added zenith mainnet and testnet networks

* Update _data/chains/eip155-79.json

* Update _data/chains/eip155-81.json

* added shortName

* rename testnet symbol to length<6

* fix vilnius typo

* Update _data/chains/eip155-81.json

* add more rpcs

Co-authored-by: ligi <ligi@ligi.de>
2022-05-20 10:43:37 +02:00
_data Add more RPCs for Zenith Mainnet (#1169) 2022-05-20 10:43:37 +02:00
.ci Add test stage 2020-11-13 04:19:30 +01:00
.github Do not mark enhancement issues as stale 2022-02-16 05:55:31 +01:00
gradle/wrapper Use gradle 7.4.2 2022-04-11 14:37:18 +02:00
model Use ksp 1.6.21-1.0.5 2022-05-19 18:34:35 +02:00
processor Add status field and remove deprecated field 2022-05-19 18:34:35 +02:00
.gitignore add Gather chains (#598) 2021-11-29 10:43:31 +01:00
build.gradle Only suggest stable versions 2022-05-19 18:34:35 +02:00
gradlew Use gradle 7.2 2021-09-14 13:38:05 +02:00
gradlew.bat Use gradle 6.7 2020-11-13 04:19:29 +01:00
LICENSE
README.md Add status field and remove deprecated field 2022-05-19 18:34:35 +02:00
settings.gradle.kts Split out the model to extra module 2021-12-30 07:38:32 +01:00

README.md

EVM-based Chains

The source data is in _data/chains. Each chain has its own file with the filename being the CAIP-2 representation as name and .json ans extension.

Example

{
  "name": "Ethereum Mainnet",
  "chain": "ETH",
  "network": "mainnet",
  "rpc": [
    "https://mainnet.infura.io/v3/${INFURA_API_KEY}",
    "https://api.mycryptoapi.com/eth"
  ],
  "faucets": [],
  "nativeCurrency": {
    "name": "Ether",
    "symbol": "ETH",
    "decimals": 18
  },
  "infoURL": "https://ethereum.org",
  "shortName": "eth",
  "chainId": 1,
  "networkId": 1,
  "icon": "ethereum",
  "explorers": [{
    "name": "etherscan",
    "url": "https://etherscan.io",
    "icon": "etherscan",
    "standard": "EIP3091"
  }]
}

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:


[
    {
      "url": "ipfs://QmdwQDr6vmBtXmK2TmknkEuZNoaDqTasFdZdu3DRw8b2wt",
      "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:

{
  ...
  "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.

You can add a status field e.g. to deprecate a chain (a chain should never be deleted as this would open the door to replay attacks) Other options for status are active (default) or incubating

Aggregation

There are also aggregated json files with all chains automatically assembled:

Collision management

If different chains have the same chainID we list the one with the oldest genesis.

Usages