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
362 Commits 320 Branches 7 Tags 66 MiB
Kotlin 94.2%
JavaScript 5.8%
32c100d7fd
Go to file
medicine 32c100d7fd
Add RPC URLs, and show the current name "Polygon" (#324) 
The original RPC has been unusable for a long time and the has not been resolved, we should add new alternative URLs from the MATIC documentation(https://docs.matic.network/docs/develop/network-details/network/).
2021-07-05 14:05:25 +02:00
_data Add RPC URLs, and show the current name "Polygon" (#324) 2021-07-05 14:05:25 +02:00
.ci Add test stage 2020-11-13 04:19:30 +01:00
.github Also run build github action on pull_request (#325) 2021-07-05 14:02:31 +02:00
gradle/wrapper Use gradle 7.1.1 2021-07-02 23:53:24 +02:00
src Fix faucet field for minified json 2021-07-05 06:22:09 +02:00
.gitignore add verify-script and run through data 2019-06-17 17:45:49 +02:00
build.gradle Use Kethereum 0.84.4 2021-07-02 23:59:45 +02:00
gradlew Use gradle 7.1.1 2021-07-02 23:53:24 +02:00
gradlew.bat Use gradle 6.7 2020-11-13 04:19:29 +01: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

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"

Aggregation

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

Usages