XCM Global Asset Registry

TL;DR

This XCM Global Asset Registry (XCMGAR) repo does all the data processing needed to aggregate multiple on-chain asset registries from the Polkadot and Kusama ecosystem into one XCM Global Asset Registry.

• Input: known Polkadot + Kusama RPC endpoints

• Output:

  • xcmgar.json: a registry file containing all assets, xcAssets, xcmRegsitry across parachains.
    • CDN: https://cdn.jsdelivr.net/gh/colorfulnotion/xcm-global-registry/metadata/xcmgar.json
  • xcmgar_url.json: a metadata file containing links to every individual asset, xcAsset. xcmRegistry files. Each file can be served individually, depending on your use case
    • CDN: https://cdn.jsdelivr.net/gh/colorfulnotion/xcm-global-registry/metadata/xcmgar_url.json
  • local (xc)Assets registry + local xcm registry per each parachain.
    • Used as cached backups when endpoints are temporarily unreachable during the periodic on-chain crawl.

As of March 2023, XCMGAR covers 55+ chains with 35 xcAssets on Polkadot and 47 on Kusama. This is a work in progress and needs contributions from parachain teams to be successful. Data is updated daily via Github Actions.

Target use cases: multichain dapps, chain analytics in the Substrate ecosystem

Roadmap

Spring 2023

• Implementing common chainParser to automatically parse {assets, tokens} pallets registry, which are commonly used by many parachains.
• Periodic registry fetching via Github workflow
• local (xc)Assets registry + local xcm registry per each parachain for debuggability
• Publishing results as CDN files for easier importing/exporting.
• Load public endpoints from Polkadot.js

Install

To get started, clone this repo:

git clone [email protected]:colorfulnotion/xcm-global-registry.git && cd xcm-global-registry

And install all dependencies, python3 may be required:

npm install

Quick Start

./xcmgar
Usage: xcmgar [options] [command]

XCM Global Asset Registry. Repo: https://github.com/colorfulnotion/xcm-global-registry

Options:
  -V, --version       output the version number
  -h, --help          display help for command

Commands:
  registry [options]  Fetch on-chain Asset Registry and XCM MultiLocation Registry
  endpoint [options]  Update public endpoints
  generate [options]  generate metadata from cached results
  help [command]      display help for command

To generate XCM Global Asset Registry:

Usage: xcmgar registry [options]

Fetch on-chain Asset Registry and XCM MultiLocation Registry

Options:
  -r, --relaychain <relaychain>  relaychain (polkadot or kusama) (default: "polkadot")
  -p, --paraID <paraID>          Targeted paraID (relaychain itself is identified using paraID=0). If not specified, crawl for all reachable parachains. (default: "all")
  -d, --dry                      dry run the cmd without updating (default: false)
  -h, --help                     display help for command

# generate polkadot xcmRegistry
./xcmgar registry -r polkadot -p all

# generate kusama xcmRegistry
./xcmgar registry -r kusama -p all

xcmRegistry and parachains (xc)Asset Registry will be cached/updated after successful run:

✅ Success: polkadot XCM Global Asset Registry (Found:35) cached @
    xcmRegistry/polkadot_xcmRegistry.json
...
✅ Success: polkadot-2000 Local Asset Regsitry (Found:22) cached @

Generate Single Parachain (xc)Asset Registry:

Single parachain (xc)Asset registry can be generated/inspected by passing in with --relaychain and --paraID:

# generate acala's (xc)Asset registry:
./xcmgar registry -r polkadot -p 2000

# dry-run moonriver's (xc)Asset registry:
./xcmgar registry -r kusama -p 2023 -d

Implement Custom Parser:

Follow the tutorial to spin up a custom parser under 30min.

How it works

TL;DR version:

• Given a relaychain, retrieve a list of its parachains (paraIDs) on-chain.
• Use polkadot.js's public endpoint registry to spin up crawlers for every reachable parachains(paraIDs).
• Every crawler will go through a 3-step process to:
  • Step 1 - Fetch its Asset registry on-chain
  • Step 2 - Fetch its XCM Registry on-chain.
  • Step 3 - [optional] Augment the XCM result from previous step
• Aggregate multiple parachains' XCM Registry into one map keyed by the standardized multilocation

For implementation details (including design choice), see the doc here.

Goal: Filling the lack of XCM Global Asset Registry

Substrate Engineers, dapp developers and analytics providers are currently faced with a "Tower of Babel" to align each parachain's asset registry and XCM asset registry and associated weights/fees. Multichain dapp developers (including multi-chain indexers like Polkaholic.io) are required to independently develop this mapping just to initiate seemly simple XCM tasks like transferring “KSM” or "USDT" from one chain to another or indexing XCM transfers. In our opinion, it’s counter-productive to require multichain app developers to independently piece this together, and furthermore, read fee constants in N parachains to support their multi-chain dapps and be faced with so much friction.

In our work in Polkaholic.io XCM Indexing, we have developed a useful API [Polkaholic.io Multilocation Tool] that attempts to address the Tower of Babel. We believe this already covers as much as 90% of the cross-chain transferable assets and over 97% of the XCM Transfer USD volume in Polkadot + Kusama at present. However, we believe that the recipe for this dataset construction should be managed not by one "trusted" team but with:

• (A) Open Source Data Generation (automated Github Action) - Given Input: Polkadot + Kusama WSEndpoints from polkadot.js apps, augmented with a polkadot.toml file containing details of how to process the (xc)asset registry of each parachain

  • Step 1: Crawl assetRegistry + xcAssetRegistry and store it in JSON file
  • Step 2: Aggregate and publish registry keyed by XcmInteriorKey

• (B) Joint Collaboration -

  • Having Open Source Data Generation managed by parachain teams who model their own (xcm) asset registry and fees accurately when working their parachain partners.

The data generation process is technically simple, but we cant stress enough the importance of joint collaboration - currently many parachain chains are largely building their own 'xcm-tools' independently of one another and only trying to cover a subset of the xcm global asset registry problem.

Key Use cases for the XCM Global Asset Registry (GAR):

• Powering XCM Transfer dapps with Multilocation
• Parachain Bridge Monitoring
• AssetHub DEX Aggregator
• Cross-chain Price Quote Mechanism that have MultiLocation

Together, we can do much better, and be more reactive to any incompleteness and inaccuracy, because simply put, 90-97% is not good enough to here. The expectation is to collaborate for the common good/maximal impact:

• When parachains or dapp developers see errors in step 1/2, they submit PRs because their community depends on the output
• Parachain reviewers from the affected teams will approve the PR, with special attention to how the registry changes with any change.
• Updates to the repo’s output dataset
• Data pipelining with Github actions

We can only succeed if parachains possess high reactivity (< 12-24 hrs) here and are not bottlenecked by a central reviewer, and data quality is either at 100%, or the data contains 100% reliable social proof data that users can understand.

Contributing:

We are looking for Polkadot/Kusama treasury and parachain teams to support this initiative. Please take a look at here and give us your valuable feedbacks.

To indicate your interest, please submit a PR:

NOTE This repo is now in Maintenance mode; if you interested in taking over this project, please send us an email at [email protected]