Funding hit rate - Token Terminal Docs

One row per venue and chain, comparing its curated deposit anchors against the deposit addresses detected from wallet behavior. curated_hit_rate is curated_also_detected divided by curated_deposit_wallets, null where curated_deposit_wallets is zero.

Columns

Column	Type	Description
`venue_project_id`	STRING	Venue the wallets are compared for.
`chain_id`	STRING	Chain the wallets are on.
`curated_deposit_wallets`	INT64	Venue’s curated deposit anchors on this chain.
`detected_deposit_addresses`	INT64	Distinct counterparty addresses this venue’s edges detected as deposit addresses on this chain.
`curated_also_detected`	INT64	Curated deposit anchors that also appear as a detected counterparty.
`curated_hit_rate`	FLOAT64	`curated_also_detected` divided by `curated_deposit_wallets`. Null where `curated_deposit_wallets` is zero.

Sample queries

One venue's hit rate by chain
Every venue and chain, ranked by hit rate
Venue name alongside the hit rate

A high curated_hit_rate on a chain means the detector is rediscovering the same anchors the registry already curated there.

select
    chain_id,
    curated_deposit_wallets,
    detected_deposit_addresses,
    curated_hit_rate
from `reports_accounts.funding_hit_rate`
where venue_project_id = 'coinbase'
order by chain_id

Filtering curated_deposit_wallets > 0 drops the pairs curated_hit_rate is null for.

select
    venue_project_id,
    chain_id,
    curated_deposit_wallets,
    curated_hit_rate
from `reports_accounts.funding_hit_rate`
where curated_deposit_wallets > 0
order by curated_hit_rate desc
limit 50

venue_project_id joins dimensions.projects for the display name.

select
    projects.name,
    rate.chain_id,
    rate.curated_deposit_wallets,
    rate.curated_hit_rate
from `reports_accounts.funding_hit_rate` as rate
join `dimensions.projects` as projects
    on rate.venue_project_id = projects.project_id
where rate.curated_deposit_wallets > 0
order by rate.curated_hit_rate desc
limit 50