> ## 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 coverage

> The share of each chain's funded wallets that resolve to a venue, by confidence tier.

One row per chain, over the whole of [Funding](https://tokenterminal.com/docs/catalog/accounts/funding.md). `resolved_share` is `wallets_resolved` divided by `wallets_with_edges`.

## Columns

<table>
  <thead>
    <tr>
      <th width="220">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>`wallets_with_edges`</td><td>INT64</td><td>Rows in [Funding](https://tokenterminal.com/docs/catalog/accounts/funding.md) for this chain.</td></tr>
    <tr><td>`wallets_resolved`</td><td>INT64</td><td>Of those, `funding_venue_project_id` is not null.</td></tr>
    <tr><td>`resolved_share`</td><td>FLOAT64</td><td>`wallets_resolved` divided by `wallets_with_edges`.</td></tr>
    <tr><td>`wallets_high`</td><td>INT64</td><td>Resolved wallets at `high` confidence.</td></tr>
    <tr><td>`wallets_medium`</td><td>INT64</td><td>Resolved wallets at `medium` confidence.</td></tr>
    <tr><td>`wallets_low`</td><td>INT64</td><td>Resolved wallets at `low` confidence.</td></tr>
    <tr><td>`wallets_curated_source`</td><td>INT64</td><td>Resolved wallets whose `funding_venue_source` is `curated`.</td></tr>
    <tr><td>`wallets_detected_source`</td><td>INT64</td><td>Resolved wallets whose `funding_venue_source` is `detected`.</td></tr>
    <tr><td>`wallets_with_jurisdiction`</td><td>INT64</td><td>Resolved wallets with a `funding_jurisdiction`.</td></tr>
    <tr><td>`jurisdiction_share`</td><td>FLOAT64</td><td>`wallets_with_jurisdiction` divided by `wallets_resolved`.</td></tr>
    <tr><td>`distinct_venues`</td><td>INT64</td><td>Distinct `funding_venue_project_id` values on this chain.</td></tr>
    <tr><td>`first_edge_at`</td><td>TIMESTAMP</td><td>Earliest `funding_first_edge_at` on this chain.</td></tr>
    <tr><td>`last_edge_at`</td><td>TIMESTAMP</td><td>Latest `funding_first_edge_at` on this chain.</td></tr>
  </tbody>
</table>

## Sample queries

**One chain's coverage**

`resolved_share` and `jurisdiction_share` read together show how much of a chain's funded wallets resolve to a venue, and how much of that group also resolves to a country.

```sql theme={null}
select
    wallets_with_edges,
    wallets_resolved,
    resolved_share,
    wallets_with_jurisdiction,
    jurisdiction_share
from `reports_accounts.funding_coverage`
where chain_id = 'ethereum'
```

**Every chain, ranked by resolved share**

One row per covered chain, so ranking them needs no aggregation.

```sql theme={null}
select
    chain_id,
    resolved_share,
    distinct_venues
from `reports_accounts.funding_coverage`
order by resolved_share desc
```

**Chain name alongside the coverage**

`chain_id` joins `dimensions.chains` for the display name.

```sql theme={null}
select
    chains.name,
    coverage.resolved_share,
    coverage.wallets_high,
    coverage.wallets_medium,
    coverage.wallets_low
from `reports_accounts.funding_coverage` as coverage
join `dimensions.chains` as chains
    using (chain_id)
order by coverage.resolved_share desc
```


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