schnellreich / on-chain-registry

asset list of cosmos-sdk based chains. on-chain data only!

On-Chain Registry: Cosmos-SDK Asset List

As blockchain assets transition between various chains within the Cosmos ecosystem and beyond, the need arises for a precise tool to monitor this intricate data flow. Meet the On-Chain Registry (OCR) – meticulously designed to compile all proof-of-nodes data, offering a timely and detailed snapshot of the current asset landscape.

Proof-of-Nodes Concept

Rather than a static registry, the OCR represents a living, constantly updating protocol that sources data straight directly from nodes. This mechanism leads to:

• Accuracy: Provides complete and precise data essential for successful blockchain transactions.
• Reliability: Minimizes human error, offering consistent and reliable information.
• Inclusivity: Ensures comprehensive coverage by including all relevant data across chains.

Workflow:

Functionality

OCR provides an interface for updating, storing, and accessing data on-chain. This enables it to dynamically adapt to the ever-changing state of the chains.

API & IBC Tokens Verification. OCR functions as a robust and secure API, offering users the capability to verify Inter-Blockchain Communication (IBC) tokens with trusted and verified metadata. This feature further enhances the transparency and security of cross-chain transactions.

Integration of External Registries. In the pursuit of providing an all-encompassing data access point, OCR integrates data from other registries as well. This guarantees that users have a comprehensive, unified, and updated view of the entire blockchain ecosystem.

Assets

On-chain based data allows viewing of all existing assets:

• chain-registry like data
• csv data
• contracts (code, schema)
  • bostrom

Asset Data Structure

OCR uses a chain-registry like asset data structure for better compatibility.

Differences from the chain-registry asset data structure:

• add chain_id required property;
• denom_units, display, name and symbol asset object properties are optional;
• add chain_id required property in asset traces section;
• set chain_name property in asset traces section as optional;
• add supply optional property in asset section and base_supply optional property in asset traces section;
• add admin required property for factory asset type in asset section.

Contract queries

Query schema
Query examples

How to deploy

clone repo and optionally edit the .env file

git clone https://github.com/Snedashkovsky/on-chain-registry && \
cd on-chain-registry && \
cp .env.example .env

install python requirements

pip install -r requirements.txt

update asset list

make update

Data Sources (REST APIs)

• /cosmos/bank/v1beta1/supply
  • denom
  • amount (supply)

    {
      "denom": "gamm/pool/1",
      "amount": "216862733786995310900019706"
    }

• /cosmos/bank/v1beta1/denoms_metadata
  • description
  • denom units
    • denom
    • exponent (decimals)
    • aliases
  • base (denom)
  • display
  • name
  • symbol

    {
      "description": "The bandwidth token of Bostrom",
      "denom_units": [
        {
          "denom": "millivolt",
          "exponent": 0,
          "aliases": []
        },
        {
          "denom": "volt",
          "exponent": 3,
          "aliases": [
            "VOLT"
          ]
        }
      ],
      "base": "millivolt",
      "display": "volt",
      "name": "Bostrom Volt",
      "symbol": "VOLT"
    }

• /ibc/core/channel/v1/channels
  • chain_id_counterparty

{
    "@type": "/ibc.lightclients.tendermint.v1.ClientState",
    "chain_id": "cosmoshub-4",
    "trust_level": {
      "numerator": "1",
      "denominator": "3"
    },
    "trusting_period": "1209600s",
    "unbonding_period": "1814400s",
    "max_clock_drift": "60s",
    "frozen_height": {
      "revision_number": "0",
      "revision_height": "0"
    },
    "latest_height": {
      "revision_number": "4",
      "revision_height": "15547071"
    },
    "proof_specs": [
      {
        "leaf_spec": {
          "hash": "SHA256",
          "prehash_key": "NO_HASH",
          "prehash_value": "SHA256",
          "length": "VAR_PROTO",
          "prefix": "AA=="
        },
        "inner_spec": {
          "child_order": [
            0,
            1
          ],
          "child_size": 33,
          "min_prefix_length": 4,
          "max_prefix_length": 12,
          "empty_child": null,
          "hash": "SHA256"
        },
        "max_depth": 0,
        "min_depth": 0
      },
      {
        "leaf_spec": {
          "hash": "SHA256",
          "prehash_key": "NO_HASH",
          "prehash_value": "SHA256",
          "length": "VAR_PROTO",
          "prefix": "AA=="
        },
        "inner_spec": {
          "child_order": [
            0,
            1
          ],
          "child_size": 32,
          "min_prefix_length": 1,
          "max_prefix_length": 1,
          "empty_child": null,
          "hash": "SHA256"
        },
        "max_depth": 0,
        "min_depth": 0
      }
    ],
    "upgrade_path": [
      "upgrade",
      "upgradedIBCState"
    ],
    "allow_update_after_expiry": true,
    "allow_update_after_misbehaviour": true
  }

• /ibc/apps/transfer/v1/denom_traces (iterate by denom)
  • denom_base
  • path
  • channels (calculated from path)

{
    "path": "transfer/channel-2",
    "denom_base": "uosmo"
  }

• /ibc/core/channel/v1/channels
  • channel_id_counterparty

    {
      "state": "STATE_OPEN",
      "ordering": "ORDER_UNORDERED",
      "counterparty": {
        "port_id": "transfer",
        "channel_id": "channel-341"
      },
      "connection_hops": [
        "connection-10"
      ],
      "version": "ics20-1",
      "port_id": "transfer",
      "channel_id": "channel-8"
    }

Contributions

We warmly welcome pull requests, issues, and feedback from the community.