Registry

The identity tables behind every bridge figure. Every fact and metric joins to one of them, and Coverage introduces each grain.

Tables

Projects
Apps
Bridge tokens

One row per project in the catalog.

Column	Type	Description
`project_id`	STRING	The project, such as `aave`.
`name`	STRING	Display name.
`symbol`	STRING	Ticker of the project’s token, where it has one.
`status_label`	STRING	Whether the project is active or archived.
`market_sectors`	ARRAY<STRING>	Every sector the project is tagged with.
`primary_market_sector`	STRING	The first of those, for grouping.

One row per app in the catalog.

Column	Type	Description
`app_id`	STRING	The app, such as `aave-v3`.
`project_id`	STRING	The project operating it.
`name`	STRING	Display name.
`market_sectors`	ARRAY<STRING>	Every sector the app is tagged with.
`primary_market_sector`	STRING	The first of those, for grouping.
`created_at`	TIMESTAMP	When the app was added.

One row per token in the catalog, in dimensions.tokens. token_id is the key the bridge token grain is built on.

Column	Type	Description
`token_id`	`STRING`	Token identifier: `{token_address}-{chain_id}`.
`asset_id`	`STRING`	The curated asset this token is a deployment of. Empty where no one has matched it.
`chain_id`	`STRING`	Chain the contract is deployed on.
`token_address`	`STRING`	Contract address, lowercase.
`symbol`	`STRING`	Symbol read from the contract, unverified.
`name`	`STRING`	Name read from the contract, unverified.
`decimals`	`INT64`	How many decimal places to move to turn a raw amount into a token amount.
`created_at`	`TIMESTAMP`	When the token launched onchain.
`bridged`	`BOOL`	Whether the deployment is a bridged wrapper. Empty where the token has not been matched to an asset.
`coingecko_id`	`STRING`	Identifier of the same token in the CoinGecko catalogue, for joining our record to a public one.

Sample queries

Bridge apps
Projects behind the bridges
Tokens one bridge moves
Chains a bridge connects

market_sectors is an array, so the section filter reads 'bridges' in unnest(market_sectors). An app tagged with several sectors returns one row.

select
    app_id,
    project_id,
    name
from `dimensions.apps`
where 'bridges' in unnest(market_sectors)
order by project_id, app_id

A project can run several bridge versions, and this returns the project once. primary_market_sector is the first tag on the project, and what the Explorer groups on.

select
    project_id,
    name,
    symbol,
    primary_market_sector
from `dimensions.projects`
where 'bridges' in unnest(market_sectors)
order by project_id

The token grain is where a bridge’s assets are named, and token_id joins dimensions.tokens for the symbol and the decimals. Bound timestamp on the metrics side: this reads one day.

select distinct
    daily.token_id,
    tokens.symbol,
    tokens.decimals,
    daily.chain_id
from `metrics_bridge_tokens.source_transfer_volume_daily` as daily
join `dimensions.tokens` as tokens
    using (token_id)
where daily.app_id = 'circle-cctp-v2'
  and daily.timestamp = timestamp('2026-08-01')
order by tokens.symbol, daily.chain_id

The chain pairs a bridge serves are read off the transfers themselves, on source_chain_id and destination_chain_id. Bound block_timestamp: the fact is partitioned on it.

select
    source_chain_id,
    destination_chain_id,
    count(*) as transfers
from `facts_bridge_tokens.transfers`
where app_id = 'layerzero-v2'
  and block_timestamp >= timestamp('2026-08-01')
  and block_timestamp < timestamp('2026-08-02')
group by source_chain_id, destination_chain_id
order by transfers desc
limit 25

Overview

Popular datasets

Market verticals

Chain ecosystems

Core entities

Tables

Sample queries

​Tables

​Sample queries

Tables

Sample queries