Region hit rate

One row per project, chain family, expected region and confidence tier. hit_rate is hits divided by accounts, the share of that project’s accounts on that chain family whose derived region matched expected_band. Every combination is reported regardless of size, but the automated modal-band check behind this table only asserts on a (project, chain family) pair once it has at least five accounts with a resolved region band — below that, the pair passes vacuously rather than being judged on too little evidence.

Columns

Column	Type	Description
`project_id`	STRING	Project the accounts are attributed to, such as an exchange running hot wallets.
`chain_family`	STRING	`evm` or `svm`; joins `dimensions.chains`.
`expected_band`	STRING	Region band the account is expected to fall in, known in advance rather than derived from activity. One of the same seven UTC-offset bands as Accounts ▸ Registry’s `region`.
`region_confidence`	STRING	`high`, `medium` or `low`, or null when no tier was met, the confidence tier the row’s accounts were measured at.
`accounts`	INT64	Attributed accounts for that project, chain family and confidence tier with a known expected band.
`hits`	INT64	Of those, the accounts whose derived `region` matched `expected_band`.
`hit_rate`	FLOAT64	`hits` divided by `accounts`, from `safe_divide`.

Sample queries

One project's hit rate by confidence
Hit rate across every project, at high confidence
Project name alongside the hit rate

Filtering to one project_id shows whether the hit rate rises with region_confidence, the pattern the tier thresholds are meant to produce.

select
    chain_family,
    region_confidence,
    accounts,
    hits,
    hit_rate
from `reports_accounts.region_hit_rate`
where project_id = 'coinbase'
order by region_confidence

Summing hits and accounts before dividing avoids averaging an average across projects of very different sizes.

select
    project_id,
    sum(hits) as hits,
    sum(accounts) as accounts,
    safe_divide(sum(hits), sum(accounts)) as hit_rate
from `reports_accounts.region_hit_rate`
where region_confidence = 'high'
group by project_id
order by hit_rate desc

project_id joins dimensions.projects for the display name.

select
    projects.name,
    rate.chain_family,
    rate.region_confidence,
    rate.hit_rate
from `reports_accounts.region_hit_rate` as rate
join `dimensions.projects` as projects
    using (project_id)
where rate.region_confidence = 'high'
order by rate.hit_rate desc
limit 50

Overview

Popular datasets

Market verticals

Chain ecosystems

Core entities

Columns

Sample queries

​Columns

​Sample queries

Columns

Sample queries