Registry

Three registry tables describe the assets we track. Every other asset table, daily or event by event, joins to them.

dimensions.assets: one row per curated asset.
dimensions.asset_tokens: one row per onchain deployment, one token contract on one chain.
dimensions.reference_assets: one row per thing an instrument tracks or wraps.

Tables

Assets
Deployments
Reference assets

dimensions.assets contains one row per curated tokenized asset. The row belongs to no particular chain: it carries the asset’s name, what kind of instrument it is, and what it tracks. The per-chain contracts live in dimensions.asset_tokens.

Column	Type	Description
`asset_id`	`STRING`	Identifier of the asset, for example `usdc`.
`reference_asset_id`	`STRING`	What the asset tracks or wraps. Joins `dimensions.reference_assets`.
`name`	`STRING`	Display name of the asset.
`symbol`	`STRING`	Ticker symbol of the asset.
`asset_type`	`STRING`	What kind of instrument it is: `stablecoin`, `tokenized-stocks`, `tokenized-funds`, `lending-token`, `tokenized-commodities`, `liquid-staking-token`, `tokenized-cryptoasset` or `wrapped_native`.
`description`	`STRING`	Short description of the asset.
`created_at`	`TIMESTAMP`	When the asset entered the registry.
`metrics_verified_at`	`TIMESTAMP`	When the asset’s published metrics were last verified. Null while unverified.
`peg_currency`	`STRING`	ISO currency code of the peg, set when the asset tracks a national currency. Empty otherwise: a fund strategy, a share or a commodity is not a peg.
`mica_indicator`	`STRING`	Which MiCA category the peg implies: `e_money_token_candidate` for single-currency stablecoins, `asset_referenced_token_candidate` for other stablecoins, `undetermined` for everything else. An indicator, not a regulatory ruling.

dimensions.asset_tokens contains one row per onchain deployment of a curated asset. A deployment is one token contract on one chain, and it is what every supply, holder and transfer measure is counted per.

Column	Type	Description
`asset_token_id`	`STRING`	Identifier of the deployment, formatted `{asset_id}-{token_address}-{chain_id}`.
`asset_id`	`STRING`	Asset the deployment belongs to. Joins `dimensions.assets`.
`token_id`	`STRING`	Key of the deployment in `dimensions.tokens`, formatted `{token_address}-{chain_id}`.
`chain_id`	`STRING`	Chain the contract is deployed on.
`token_address`	`STRING`	Address of the token contract.
`is_bridged`	`BOOL`	Raw registry flag: bridged in rather than issued natively. Always present, so `false` means native or unstated. Filter on `bridged_status` instead.
`bridged_status`	`STRING`	The classification supply measures split on: `native`, `bridged` or `unclassified`.

The table keeps deployments that have no row in dimensions.tokens: a deployment our price feed does not cover has no row there, and dropping it would under-report what exists. So token_id is not guaranteed to match a row in dimensions.tokens.Filter supply on bridged_status. A stated registry flag is taken as given; an unstated one reads native when the asset has no confirmed bridged deployment anywhere, and unclassified when it does.

dimensions.reference_assets contains one row for each thing an instrument can track or wrap: national currencies, stocks, commodities, funds and cryptoassets. This is what a tokenized instrument or a perpetual market points at, and it is not the same thing as the tokenized asset itself.

Column	Type	Description
`reference_asset_id`	`STRING`	Identifier of the thing being tracked.
`linked_asset_id`	`STRING`	Its own tokenized asset in `dimensions.assets`, where one exists.
`name`	`STRING`	Display name.
`symbol`	`STRING`	Ticker symbol.
`type`	`STRING`	What kind of thing it is: `stock`, `crypto`, `fiat`, `pendle_pt`, `etf`, `commodity`, `fund_strategy`, `bond` or `other`.
`currency_code`	`STRING`	ISO currency code, filled in only on the `fiat` rows.
`unit`	`STRING`	The physical unit a commodity is quoted in, for example `troy ounce` or `barrel`. Empty on everything else.
`aliases`	`ARRAY<STRING>`	Other names it is known by.

type = 'fiat' is what makes something a currency peg. peg_currency on dimensions.assets is empty for everything else, so an asset that tracks a fund strategy or a share carries no peg, even though it does track something.

Sample queries

Assets by type
Deployments of one asset
What an asset tracks

Count assets by type. asset_type says what kind of instrument it is.

select
    asset_type,
    count(*) as assets
from `dimensions.assets`
group by asset_type
order by assets desc

List every deployment of one asset. bridged_status says whether each contract was issued natively on its chain or bridged in from another.

select
    asset_token_id,
    chain_id,
    token_address,
    bridged_status
from `dimensions.asset_tokens`
where asset_id = 'usdc'
order by chain_id

Find out what an asset tracks. Tracking a national currency is what makes an asset a currency-pegged stablecoin, and assets.peg_currency comes from it.

select
    assets.asset_id,
    reference_assets.reference_asset_id,
    reference_assets.type,
    reference_assets.currency_code
from `dimensions.assets` as assets
join `dimensions.reference_assets` as reference_assets
    using (reference_asset_id)
where assets.asset_id in ('usdc', 'usdt', 'dai')
order by assets.asset_id

Overview

Core entities

Market verticals

Chain verticals

Tables

Sample queries

​Tables

​Sample queries

Tables

Sample queries