Registry

The identity tables behind every asset figure. Every fact and metric joins to them, and Coverage introduces the grain.

Tables

Assets
Deployments
Reference assets

One row per curated asset: its name, what kind of instrument it is, and what it tracks. The row belongs to no particular chain, and the per-chain contracts live in dimensions.asset_tokens.

Column	Type	Description
`asset_id`	`STRING`	Identifier of the asset, for example `usdc`. Every table that mentions an asset joins on this.
`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`. One value per asset.
`coingecko_id`	`STRING`	Identifier of the same asset in the CoinGecko catalogue, for joining our record to a public one.
`coinmarketcap_id`	`STRING`	Identifier of the same asset in the CoinMarketCap catalogue, for the same purpose.
`description`	`STRING`	Short description of the asset.
`yahoo_ticker`	`STRING`	Ticker the underlying trades under on Yahoo Finance, where it is listed.
`custom_price_fx_peg`	`STRUCT`	A fixed rate the asset is priced at rather than a market quote, in `currency`, `multiplier` and `priority`. Set only where the asset declares one, and `priority` says whether the rate overrides the market price or only fills in where there is none.
`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.
`mica_marker`	`STRING`	Which MiCA category the peg implies: `emt_by_peg` for single-currency stablecoins, `art_by_peg` for other stablecoins, `other_crypto_asset` or `out_of_scope_financial_instrument` for everything else. A marker read off the peg.
`mica_authorization_status`	`STRING`	Whether the token is authorized under MiCA according to the official register: `emt_authorized`, `art_authorized`, `not_authorized`, `application_withdrawn`, `out_of_scope_mifid`, `other_crypto_asset` or `not_checked`. A sourced regulatory fact, where `mica_marker` is read off the peg.
`regulatory_supervised`	`STRING`	What the issuer discloses about its own supervision: `true`, `false` or `unknown`. A disclosure, taken as given.
`regulator`	`STRING`	The authority the issuer names as its supervisor, such as `NYDFS/FinCEN`. Filled in where the issuer names one.
`reserves_source`	`STRING`	Where the reserve figure comes from: `attestation` for an issuer-published report, `onchain` where the backing addresses are identified and the balance computed here, `none` where the issuer publishes nothing.
`reserves_attestor`	`STRING`	The firm signing the attestation, filled in where `reserves_source` is `attestation`.
`return_treatment`	`STRING`	How the token treats the income the underlying pays: `total_return`, `price_return`, `price_return_with_distribution` or `not_applicable`. Keyed on the token rather than on what it tracks, so two tokenizations of one share can differ.
`issuer_legal_name`	`STRING`	The issuing entity as a government register spells it, which is routinely different from the brand.
`issuer_domicile`	`STRING`	ISO 3166-1 alpha-2 country code of where the issuing entity is registered, such as `US`. Resolved from the issuing project, so it is filled in where that project has a domicile on file.
`issuer_lei`	`STRING`	Legal Entity Identifier of the issuing entity.
`issuer_cik`	`STRING`	SEC Central Index Key of the issuing entity.
`issuer_regulatory_framework`	`ARRAY<STRING>`	Regimes the issuing entity operates under. An array because an entity can sit under several at once.
`issuer_legal_source_url`	`STRING`	The filing or register the legal fields above were read from, with `issuer_legal_retrieved_at` recording when.
`issuer_legal_retrieved_at`	`STRING`	When `issuer_legal_source_url` was last read.
`use_of_income`	`STRING`	What the issuer says it does with the income the underlying pays, in its own words. `return_treatment` is the coded answer to the same question.
`isin`	`STRING`	International Securities Identification Number of the instrument, where it has one.
`cusip`	`STRING`	CUSIP of the instrument, where it has one.
`peg_currency`	`STRING`	ISO currency code of the peg, set where the asset tracks a national currency. A fund strategy, a share or a commodity is tracked without a peg, and leaves this empty.
`project_relations`	`ARRAY<STRUCT>`	Every project linked to the asset, one element per `(project_id, product_id, relation)`. `relation` is `issuer`, `asset_manager`, `risk_curator` or `manager`. Most assets link to one project; a few link to several, such as an issuer alongside a separate manager.
`issuer_project_id`	`STRING`	The project whose relation is `issuer`, when exactly one project holds that relation. Read `project_relations` for the full set, which is what this column resolves.

One row per onchain deployment of a curated asset, which is one token contract on one chain. A deployment 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}`. This table keeps every deployment that exists, so a `token_id` resolves to a row in `dimensions.tokens` where the price feed reaches that contract.
`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, and the column to filter supply by: `native`, `bridged` or `unclassified`. A stated registry flag is taken as given; an unstated one reads `native` where the asset has no confirmed bridged deployment anywhere, and `unclassified` where it has one.

One row per 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, one level below 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`. A `fiat` row is what makes an asset pointing at it a currency-pegged one, and what fills `peg_currency` on `dimensions.assets`.
`currency_code`	`STRING`	ISO currency code, filled in on the `fiat` rows.
`unit`	`STRING`	The physical unit a commodity is quoted in, for example `troy ounce` or `barrel`. Filled in on the `commodity` rows.
`aliases`	`ARRAY<STRING>`	Other names it is known by.
`yahoo_ticker`	`STRING`	Ticker it trades under on Yahoo Finance, where it is listed.

Sample queries

Assets by type
Deployments of one asset
What an asset tracks
Assets linked to a project

asset_type holds one value per asset, so these counts add up to the whole registry.

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

bridged_status says whether each contract was issued natively on its chain or bridged in from another, and it is the column the supply measures split on.

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

Tracking a national currency is what makes an asset a currency-pegged stablecoin, and assets.peg_currency comes from it. The inner join keeps the assets whose reference_asset_id resolves to a row.

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

One asset can name several projects, so unnest(project_relations) yields one row per relation and a count taken over it counts an asset once per relation. Filter inside the unnest, or use exists where only presence matters.

select
    assets.asset_id,
    assets.name,
    relation.relation
from `dimensions.assets` as assets
cross join unnest(assets.project_relations) as relation
where relation.project_id = 'securitize'
order by assets.asset_id

Overview

Popular datasets

Market verticals

Chain ecosystems

Core entities

Tables

Sample queries

​Tables

​Sample queries

Tables

Sample queries