Skip to content

Refactor the blockchain model #1295

@aurelticot

Description

@aurelticot

Custom blockchain network are persisted under this model/schema:
https://github.com/verida/schemas-vault/blob/main/blockchain/custom-networks/v0.1.0/schema.json

We should have a similar structure internally for any blockchain networks. It would make it easier to use the object.

{
  "chainId": {
    "namespace": "eip155",
    "reference": "5"
  },
  "label": "Ethereum Goerli",
  "chainName": "ethereum", // What is it? Not needed in Wallet
  "logo": "https://s2.coinmarketcap.com/static/img/coins/64x64/1027.png",
  "isMainnet": false,
  "confirmations": 6,
  "derivationPath": "m/44'/60'/0'/0/0",
  "rpcUrls": ["https://goerli.infura.io/v3/%INFURA_KEY%"], // An array
  "nativeCurrency": {
    "assetType": {
      "chainId": {
        "namespace": "eip155",
        "reference": "5"
      },
      "assetName": {
        "namespace": "slip44",
        "reference": "60"
      }
    },
    "label": "Ether Goerli",
    "decimal": 18,
    "symbol": "ETH"
  },
  "blockExplorers": [{ // An array of object that can later be expanded with the standard
    "url": "https://goerli.etherscan.io"
  }]
}

It has been suggested to follow this structure from the source, in Wallet Provider: https://github.com/verida/wallet-provider/issues/166

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions