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
960 Commits 320 Branches 7 Tags 66 MiB
Kotlin 94.2%
JavaScript 5.8%
70c7e0da11
Go to file
raulk 70c7e0da11
add Filecoin networks. (#1567) 
* add Filecoin networks.

* add SLIP-0044 coin type ID to all networks.

* add RPCs.

* expand currency names.

* set testnet SLIP-44 identifiers to 1.

* add faucet URLs.

* fix CI failures.

* fix short names.
2022-10-19 08:24:06 -07:00
_data add Filecoin networks. (#1567) 2022-10-19 08:24:06 -07:00
.ci Add test stage 2020-11-13 04:19:30 +01:00
.github Revert back to previous Prettier implementation (#1675) 2022-09-30 21:09:21 +02:00
gradle/wrapper Use gradle 7.5.1 2022-08-20 15:23:24 +02:00
model Use Kotlin 1.7.20 (#1677) 2022-10-01 06:10:22 +02:00
processor Generate Icon list JSON in build (#1524) 2022-08-31 01:58:16 +02:00
tools Disallow leading zeroes in file names (#1680) 2022-10-01 14:10:05 +02:00
.gitignore Generate Icon list JSON in build (#1524) 2022-08-31 01:58:16 +02:00
.prettierignore Added Prettier and formatted existing JSON files (#1501) 2022-08-27 19:20:08 +02:00
.prettierrc.json Added Prettier and formatted existing JSON files (#1501) 2022-08-27 19:20:08 +02:00
build.gradle Bump gradle-versions-plugin from 0.42.0 to 0.43.0 (#1725) 2022-10-18 02:02:50 +02:00
gradlew Use gradle 7.5.1 2022-08-20 15:23:24 +02:00
gradlew.bat Use gradle 7.5.1 2022-08-20 15:23:24 +02:00
LICENSE Initial commit 2018-12-20 18:53:11 +01:00
README.md Add wagmi compatible chain listings (#1696) 2022-10-08 16:56:32 +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",
  "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 positive integers
  • 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

Wallets

Explorers

EIPs

  • EIP-155
  • EIP-3014
  • EIP-3770
  • EIP-4527

Listing sites

Other