Registry

The identity table behind an attributed address: the chain it sits on, the project that runs it, its type and its label. Accounts introduces the grain, and Contracts has the deployment behind a contract account. We publish region of activity, never country of a person. Region is a UTC-offset band derived from public transaction timing by a published rule; it is a statement about when an address is active, and it is wrong for bots, custodians and anyone who does not sleep. Issuer domicile stays where it is, on dimensions.assets. Region is a property of the address key across its whole chain_family, not of one chain, and its evidence comes only from the chains activity hours covers: ethereum, base, robinhoodchain and solana. No country is ever derived from region. Every confidence tier describes the strength of one signal, the address’s daily rhythm. Per-address region is published only for accounts attributed to a project; an unattributed sender’s region appears only in the region distribution report, never as a per-address value. region is derived from activity hours:

Sum the address’s hourly transaction counts over the trailing 90 complete UTC days, across every chain in its chain_family; n is the total. Addresses with n below 300 get a null region_confidence.
The trough is the 6-hour window with the smallest share of n; its centre hour is t. The UTC offset is round(3.5 - t), wrapped to -11..+12, taking 03:30 as the local sleep centre.
The band is the one of seven that contains the offset.
Depth d = 1 - (trough share / 0.25); night share is the share in the 12 hours centred on the trough.
high needs n >= 3000, d >= 0.70, night <= 0.25; medium needs n >= 1000, d >= 0.50, night <= 0.30; low needs n >= 300, d >= 0.30, night <= 0.35; otherwise region and region_confidence are null. A second trough within 10% of the first caps confidence at low.

An address has a region only once it is attributed to a registry project, and v1’s registry projects are venues, protocols and their operators, so region describes where venues and operators run, rather than where individual traders live. A global venue’s wallets move on its users’ hours across every band, so its region reflects where its users are, aggregated, and its region_confidence often stays null. The hit rate is read against venues whose operations sit in one band. Activity coverage publishes the share of each day’s active senders that are attributed.

Columns

Column	Type	Description
`account_id`	`STRING`	Account as one key: `{address}-{chain_id}`. The key the table is clustered on, and the one that joins `dimensions.contracts` and `dimensions.tokens` directly.
`chain_id`	`STRING`	Chain the address is on. The same address on two chains is two different accounts, so an address identifies a row only with this beside it.
`address`	`STRING`	The address, spelled the way its chain spells it: lowercase on EVM and Starknet, base58 and case-sensitive on Solana and Tron. Lowercase an EVM address copied from an explorer before matching it here; the balance functions lowercase the address they are handed.
`project_id`	`STRING`	Project the address is attributed to. Joins `dimensions.projects` for the name and market sector.
`contract_name`	`STRING`	Label for the address as the attributing project names it, such as `Factory` or `USDC-WETH pool`.
`account_type`	`STRING`	`eoa` or `smartcontract`, and null where nobody has determined it, so test it with `is null` rather than `= ”`. Says nothing about whether the owner holds the address custodially.
`parent_address`	`STRING`	For a factory-emitted address, the factory that emitted it.
`label_source`	`STRING`	`curated` for an attribution a person authored, `factory_derived` for an address a known factory emitted. Most rows are factory derived; filter to `curated` for the addresses someone has looked at.
`region`	`STRING`	One of seven UTC-offset bands: `utc-11..-9`, `utc-8..-5`, `utc-4..-2`, `utc-1..+2`, `utc+3..+6`, `utc+7..+9`, `utc+10..+12`. Null when `region_confidence` is null.
`region_confidence`	`STRING`	`high`, `medium` or `low`, from the thresholds behind `region`, and null where `region` is null.
`region_evidence_txs`	`INT64`	Transactions behind the band: `n`, the trailing 90-day total the `region` calculation summed across the address’s chain family.

Sample queries

Look up an account
What one project operates
Addresses per project on one chain

account_id is the address and the chain joined by a hyphen, and the key the table is clustered on, so filtering it is the cheapest lookup. Lowercase an EVM address copied from an explorer before you paste it in.

select
    chain_id,
    address,
    project_id,
    contract_name,
    account_type,
    label_source
from `dimensions.accounts`
where account_id = '0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2-ethereum'

An address reaches this table once somebody has attributed it, so label_source splits the two ways that happens: curated is the set a person authored, and the rest is factory output.

select
    chain_id,
    address,
    contract_name,
    account_type
from `dimensions.accounts`
where project_id = 'uniswap'
  and label_source = 'curated'
order by chain_id, contract_name
limit 100

project_id joins dimensions.projects for the display name and the market sector, which is how a chain’s labeled addresses group into sectors.

select
    projects.name,
    projects.primary_market_sector,
    count(*) as addresses
from `dimensions.accounts` as accounts
join `dimensions.projects` as projects
    using (project_id)
where accounts.chain_id = 'ethereum'
  and accounts.label_source = 'curated'
group by projects.name, projects.primary_market_sector
order by addresses desc
limit 50

Overview

Popular datasets

Market verticals

Chain ecosystems

Core entities

Columns

Sample queries

​Columns

​Sample queries

Columns

Sample queries