provides metadata for chains
Go to file
2021-06-30 10:58:32 +02:00
_data Add Palm Mainnet chain definition (#315) 2021-06-30 10:58:32 +02:00
_includes Checking in just-the-docs theme, create a chains page with links to each section 2019-01-25 10:28:05 -08:00
_layouts Checking in just-the-docs theme, create a chains page with links to each section 2019-01-25 10:28:05 -08:00
_posts Basic Jekyll site with just-the-docs theme 2018-12-20 12:09:37 -08:00
_sass Checking in just-the-docs theme, create a chains page with links to each section 2019-01-25 10:28:05 -08:00
.ci Add test stage 2020-11-13 04:19:30 +01:00
.github/ISSUE_TEMPLATE Create other.md 2020-11-13 03:33:38 +01:00
assets Checking in just-the-docs theme, create a chains page with links to each section 2019-01-25 10:28:05 -08:00
gradle/wrapper Use gradle 7.0.2 2021-05-25 10:57:12 +02:00
src Initial explorers support - closes #59 2021-04-12 09:32:38 +02:00
_config.yml Checking in just-the-docs theme, create a chains page with links to each section 2019-01-25 10:28:05 -08:00
.gitignore add verify-script and run through data 2019-06-17 17:45:49 +02:00
404.html Basic Jekyll site with just-the-docs theme 2018-12-20 12:09:37 -08:00
about.md merge master and resolve conflicts 2019-04-24 17:52:17 +02:00
build.gradle Use Kotlin 1.5.10 2021-05-25 10:57:48 +02:00
chains_mini.json Also ignore the deprecated folder for mini json 2021-02-21 01:24:12 +01:00
chains.json Expose explorers in chains.json 2021-04-12 10:54:07 +02:00
chains.md Add nativeCurrency - closes #66 and add chains_mini.json 2019-05-22 23:41:52 +02:00
CNAME Create CNAME 2019-01-31 08:39:11 -08:00
Gemfile Basic Jekyll site with just-the-docs theme 2018-12-20 12:09:37 -08:00
Gemfile.lock Update BUNDLED WITH 2021-04-12 10:54:07 +02:00
gradlew Use gradle 6.7 2020-11-13 04:19:29 +01:00
gradlew.bat Use gradle 6.7 2020-11-13 04:19:29 +01:00
index.md Add nativeCurrency - closes #66 and add chains_mini.json 2019-05-22 23:41:52 +02:00
LICENSE Initial commit 2018-12-20 18:53:11 +01:00
README.md Adds eth-chains to the usages section (#288) 2021-06-05 18:37:06 +02:00

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"

Aggregation

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

Usages