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
859 Commits 320 Branches 7 Tags 66 MiB
Kotlin 94.2%
JavaScript 5.8%
a32b889f18
Go to file
PHI NETWORK a32b889f18
Updated PHI Network & Added PHI V2 Smart Chain (#1427) 
* Add New PHI Network v2 Chain

Added New Upgraded Chain For PHI Network

* Update PHI Network Chain To v1 chain

Update PHI Network Chain To v1 Chain To Add v2 Chain In Other Files.

* Add PHI Network Phiv2 image

Added Logo for PHI Network v2

* Updated PHI Network Image

Updated PHI Network v1 logo image
2022-08-18 16:42:36 +02:00
_data Updated PHI Network & Added PHI V2 Smart Chain (#1427) 2022-08-18 16:42:36 +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 Update kotlin and ksp to 1.7.0 (#1247) 2022-06-12 11:32:35 +02:00
processor Normalize names and shortNames (#1412) 2022-08-04 12:50:58 +02:00
.gitignore add Gather chains (#598) 2021-11-29 10:43:31 +01:00
build.gradle Bump KOTLIN_VERSION from 1.7.0 to 1.7.10 (#1335) 2022-07-08 11:12:32 +02:00
gradlew Use gradle 7.2 2021-09-14 13:38:05 +02:00
gradlew.bat
LICENSE
README.md Update README.md (#1306) 2022-07-15 12:00:16 +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

Wallets

Explorers

EIPs

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

Listing sites

Other