Registry - Token Terminal Docs

The identity table behind every chain figure. Every metric table joins to it, and Coverage introduces the grain.

Columns

Column	Type	Description
`chain_id`	`STRING`	Identifier of the chain. Every table that mentions a chain joins on this.
`project_id`	`STRING`	Project that runs the chain. Defaults to the chain’s own project, and names another project where that project’s app runs the chain: `unichain` resolves to `uniswap`.
`name`	`STRING`	Display name.
`chain_family`	`STRING`	`evm` or `svm`, null when the chain is unmapped. Every chain in one family is summed together for a key’s activity, such as `region` on Accounts ▸ Registry.

Sample queries

Chain identity
Chains for one project
Chain to project

chain_id is the value every other table keys on, and this is the table that spells out what it stands for.

select
    chain_id,
    name,
    project_id
from `dimensions.chains`
where chain_id = 'hyperevm'

project_id is the one place a chain’s operator is recorded, so a change of operator reaches every query that joins here.

select
    chain_id,
    name
from `dimensions.chains`
where project_id = 'uniswap'
order by chain_id

The daily chain tables key on chain_id alone, so putting a project’s name beside a chain’s figures means joining dimensions.projects through project_id.

select
    chains.chain_id,
    chains.name,
    chains.project_id,
    projects.name as project_name
from `dimensions.chains` as chains
join `dimensions.projects` as projects
    using (project_id)
order by chains.chain_id