Funding - Token Terminal Docs

One row per wallet with at least one funding edge, attributed to a project or not. funding_venue_project_id is null wherever a wallet’s edges split across venues too evenly to name one.

Columns

Column	Type	Description
`account_id`	STRING	Account as one key: `{address}-{chain_id}`. The key this table is clustered on.
`chain_id`	STRING	Chain the wallet is on.
`address`	STRING	The wallet: lowercase on EVM, verbatim base58 on Solana.
`funding_venue_project_id`	STRING	Venue that funded the wallet: the earliest edge’s venue, from Accounts ▸ Registry’s Venues tab. Null when the wallet’s edges split across venues.
`funding_venue_type`	STRING	`cex` or `fiat-ramps`, from Venues. Null iff `funding_venue_project_id` is null.
`funding_venue_source`	STRING	`curated` for an edge to a registry anchor, `detected` for an edge through a detected deposit address. Null iff `funding_venue_project_id` is null.
`funding_confidence`	STRING	`high`, `medium` or `low`, from the tiers described on Accounts ▸ Registry. Null iff `funding_venue_project_id` is null.
`funding_evidence_edges`	INT64	First-contact edges behind the row.
`funding_distinct_venues`	INT64	Venues the wallet has edges with.
`funding_first_edge_at`	TIMESTAMP	Timestamp of the wallet’s earliest funding edge.
`funding_jurisdiction`	STRING	ISO 3166-1 alpha-2 of the venue, from Venues. Null unless the venue passes the jurisdiction gate there.
`wallet_set_version`	INT64	Fingerprint of the venue’s anchor set the row was computed under. Null iff `funding_venue_project_id` is null.

Sample queries

The table is clustered on account_id, one row per wallet. Filter on the account where you have it, or on chain_id otherwise; a query that filters on neither reads the whole table.

One wallet's funding tag
Wallets by venue and confidence, on one chain
High-confidence wallets by venue, with jurisdiction

account_id is the address and the chain joined by a hyphen, and the column this table is clustered on, so filtering it is the cheapest lookup.

select
    funding_venue_project_id,
    funding_venue_type,
    funding_confidence,
    funding_jurisdiction,
    funding_first_edge_at
from `facts_accounts.funding`
where account_id = '0x7240234c7bf954cd7fc6323c38bbf6e6e4355e52-ethereum'

chain_id is not the cluster key, so bound the column list too: selecting only the columns a query needs keeps a chain-wide scan affordable.

select
    funding_venue_project_id,
    funding_confidence,
    count(*) as wallets
from `facts_accounts.funding`
where chain_id = 'ethereum'
  and funding_venue_project_id is not null
group by funding_venue_project_id, funding_confidence
order by wallets desc
limit 20

funding_venue_project_id joins dimensions.venues for the venue’s display name and jurisdiction.

select
    venues.name,
    venues.venue_type,
    venues.funding_jurisdiction,
    count(*) as wallets
from `facts_accounts.funding` as funding
join `dimensions.venues` as venues
    on funding.funding_venue_project_id = venues.venue_project_id
where funding.chain_id = 'ethereum'
  and funding.funding_confidence = 'high'
group by venues.name, venues.venue_type, venues.funding_jurisdiction
order by wallets desc