- At Pulsar we felt like there was a big gap with IBC Token Data, which prevented us from having a good way to match any IBC token to its original native token. This repo is meant to be kept updated with the current native and IBC tokens of each cosmos chain under Cosmos Chain Registry.
- With
ibc_data.json
you should be able to find any IBC token by it's hash where the keys are in the formatibc/HASH__CHAIN
, and using the origin property, you should be able to trace back to its original token data onnative_token_data.json
.
{
"ibc/HASH__CHAIN": {
"chain": String,
"hash": String,
"supply": String,
"path": String,
"origin": {
"denom": String,
"chain": String | List[String] | null
// null if we cant find this denom on native_token_data.json
// list if we couldn't pick correct chain e.g: [terra, terra2] for uluna
}
}
}
Type AssetType(Enum, String) {
native,
contract
}
Type BridgeAsset(Object) = {
"chain": String,
"value": String,
"token_type": AssetType,
}
{
"DENOM__CHAIN": {
"chain": String,
"name": String,
"denom": String,
"symbol": String,
"decimals": integer,
"description": String,
"coingecko_id": String | null,
"bridge_asset": BridgeAsset | null
"logos": {
String: String
}
}
}
- The file
ibc_data.min.json
is just a minified version ofibc_data.json
. - The file
native_token_data.min.json
is just a minified version ofnative_token_data.json
.
basecro
anduluna
have conflicts.uluna
denom is used on [Terra, Terra2] andbasecro
on [crypto_org, cronos] chains. This has been solved in most ibcs 153 out of 162.
- Planning on adding more relevant data.
- Planning on adding an API for this data.