Registry

dimensions.chains contains one row per chain. The names come from the registry we author by hand, and project_id names the project that runs the chain.

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.
`name`	`STRING`	Display name.

Sample queries

Chain to project
Chains for one project

Resolve one chain to its operating project.

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)
where chains.chain_id = 'hyperevm'

List every chain one project operates.

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

Notes

project_id defaults to the chain’s own project, and is overridden where another project’s app runs the chain: unichain resolves to uniswap. The daily chain table keys on chain_id alone, so attributing a chain’s numbers to a project always means joining this table. A change of operator lands here once and flows through every query that joins it.

Overview

Core entities

Market verticals

Chain verticals

Columns

Sample queries

Notes

​Columns

​Sample queries

​Notes

Columns

Sample queries

Notes