IBC-Token-Data-Cosmos
IBC-Token-Data-Cosmos copied to clipboard
A package containing all IBC Token Data, across the whole Cosmos Ecosystem.

🪙 Cosmos IBC Token Data
⚒️ Why This Repository?
- 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.jsonyou 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.
🧩 Schemas
IBC Data Schema
{
"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
}
}
}
Native Token Data Schema
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
}
}
}
Notes
- The file
ibc_data.min.jsonis just a minified version ofibc_data.json. - The file
native_token_data.min.jsonis just a minified version ofnative_token_data.json.
🐛 Known Issues
basecroandulunahave conflicts.ulunadenom is used on [Terra, Terra2] andbasecroon [crypto_org, cronos] chains. This has been solved in most ibcs 153 out of 162.
🔮 Future
- Planning on adding more relevant data.
- Planning on adding an API for this data.
📚 Useful Links
(back to top)