> ## Documentation Index
> Fetch the complete documentation index at: https://tokenterminal.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To query the Token Terminal data catalog, read https://tokenterminal.com/docs/catalog/agents-manual.md first. It is the whole catalog as one page: table naming grammar, key columns, partition and cluster rules, units, additivity, and the tables that are documented but not served yet.
> Never query a catalog table on a time bound alone. Also filter its cluster key, which you read from INFORMATION_SCHEMA.COLUMNS; an empty result means the object is a view, whose pruning contract is on its page. Compute is billed to the caller's own Google Cloud project.

# Funding venue distribution

> Funded wallets by venue and confidence tier, per chain.

One row per chain, venue and confidence tier, including the null venue and null confidence row for wallets that resolve to no venue. `wallet_share` is `wallets` divided by the chain's total rows in [Funding](https://tokenterminal.com/docs/catalog/accounts/funding.md).

## Columns

<table>
  <thead>
    <tr>
      <th width="230">Column</th>
      <th width="120">Type</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr><td>`chain_id`</td><td>STRING</td><td>Chain the wallets are on.</td></tr>
    <tr><td>`funding_venue_project_id`</td><td>STRING</td><td>Venue the wallets resolve to. Null for the unresolved row.</td></tr>
    <tr><td>`funding_venue_type`</td><td>STRING</td><td>`cex` or `fiat-ramps`, from [Accounts ▸ Registry](https://tokenterminal.com/docs/catalog/accounts/registry.md)'s Venues tab. Null for the unresolved row.</td></tr>
    <tr><td>`funding_jurisdiction`</td><td>STRING</td><td>ISO 3166-1 alpha-2 of the venue. Null unless the venue passes the jurisdiction gate.</td></tr>
    <tr><td>`funding_confidence`</td><td>STRING</td><td>`high`, `medium` or `low`. Null for the unresolved row.</td></tr>
    <tr><td>`wallets`</td><td>INT64</td><td>Wallets on this chain at this venue and confidence tier.</td></tr>
    <tr><td>`wallet_share`</td><td>FLOAT64</td><td>`wallets` divided by the chain's total rows in [Funding](https://tokenterminal.com/docs/catalog/accounts/funding.md).</td></tr>
    <tr><td>`first_edge_at`</td><td>TIMESTAMP</td><td>Earliest `funding_first_edge_at` in the group.</td></tr>
    <tr><td>`last_edge_at`</td><td>TIMESTAMP</td><td>Latest `funding_first_edge_at` in the group.</td></tr>
  </tbody>
</table>

## Sample queries

**One chain's venue breakdown**

The unresolved row has a null `funding_venue_project_id`, so `wallet_share` still sums to 1 across every row for the chain.

```sql theme={null}
select
    funding_venue_project_id,
    funding_confidence,
    wallets,
    wallet_share
from `reports_accounts.funding_venue_distribution`
where chain_id = 'ethereum'
order by wallets desc
```

**Top venues across every chain, at high confidence**

Summing `wallets` before ranking avoids letting one chain's larger wallet count dominate the order.

```sql theme={null}
select
    funding_venue_project_id,
    sum(wallets) as wallets
from `reports_accounts.funding_venue_distribution`
where funding_confidence = 'high'
group by funding_venue_project_id
order by wallets desc
limit 20
```

**Venue name alongside the distribution**

`funding_venue_project_id` joins `dimensions.projects` for the display name.

```sql theme={null}
select
    projects.name,
    dist.chain_id,
    dist.funding_confidence,
    dist.wallets
from `reports_accounts.funding_venue_distribution` as dist
join `dimensions.projects` as projects
    on dist.funding_venue_project_id = projects.project_id
where dist.chain_id = 'ethereum'
order by dist.wallets desc
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.