Venue edges - Token Terminal Docs

One row per wallet, venue and edge direction: the first contact between them, to the venue or from it. first_transaction_hash names the transaction the edge was first observed in.

Columns

Column	Type	Description
`account_id`	STRING	Account as one key: `{address}-{chain_id}`.
`chain_id`	STRING	Chain the edge happened on.
`address`	STRING	The wallet: lowercase on EVM, verbatim base58 on Solana.
`venue_project_id`	STRING	Venue on the other side of the edge, from Accounts ▸ Registry’s Venues tab.
`edge_direction`	STRING	`to_venue` or `from_venue`.
`first_edge_at`	TIMESTAMP	Time of the first contact between the wallet and the venue in this direction.
`first_edge_date`	DATE	UTC date of `first_edge_at`. Partition column, by month.
`first_transaction_hash`	STRING	Transaction that made the first contact.
`counterparty_address`	STRING	Venue-side address the wallet first touched.
`counterparty_kind`	STRING	`anchor` for a registry-curated venue wallet, `deposit_address` for a detected one.
`counterparty_confidence`	STRING	`curated` or `detected`, matching `counterparty_kind`.
`funding_leg`	STRING	`erc20`, `spl` or `native`: the transfer leg the edge was observed on.
`wallet_set_version`	INT64	Fingerprint of the venue’s anchor set the edge was matched under.

Sample queries

This table is large and split by month. Bound first_edge_date and filter address and chain_id on every query, or you read the whole table and the whole table is billed to you.

One wallet's edges
New edges per chain, one month
Curated versus detected edges, one venue

address and chain_id together are the cluster key, so filtering both reads only this wallet’s blocks; first_edge_date still bounds the months scanned.

select
    venue_project_id,
    edge_direction,
    first_edge_at,
    counterparty_kind
from `facts_accounts.venue_edges`
where address = '0x7240234c7bf954cd7fc6323c38bbf6e6e4355e52'
  and chain_id = 'ethereum'
  and first_edge_date >= date('2024-01-01')
  and first_edge_date < date('2025-06-01')
order by first_edge_at

edge_direction splits deposits into a venue from withdrawals out of it, so grouping on it alongside chain_id reads both directions apart.

select
    chain_id,
    edge_direction,
    count(*) as edges
from `facts_accounts.venue_edges`
where first_edge_date >= date('2026-08-01')
  and first_edge_date < date('2026-09-01')
group by chain_id, edge_direction
order by edges desc

venue_project_id joins dimensions.venues for the display name; counterparty_kind is the same split facts_accounts.funding’s funding_venue_source reads off the earliest edge.

select
    venues.name,
    edges.counterparty_kind,
    count(*) as edge_count
from `facts_accounts.venue_edges` as edges
join `dimensions.venues` as venues
    on edges.venue_project_id = venues.venue_project_id
where edges.chain_id = 'ethereum'
  and edges.first_edge_date >= date('2026-08-01')
  and edges.first_edge_date < date('2026-09-01')
group by venues.name, edges.counterparty_kind
order by edge_count desc