> ## 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](/docs/catalog/accounts/funding). `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><code>chain\_id</code></td><td>STRING</td><td>Chain the wallets are on.</td></tr>
    <tr><td><code>wallets\_with\_edges</code></td><td>INT64</td><td>Rows in <a href="/docs/catalog/accounts/funding">Funding</a> for this chain.</td></tr>
    <tr><td><code>wallets\_resolved</code></td><td>INT64</td><td>Of those, <code>funding\_venue\_project\_id</code> is not null.</td></tr>
    <tr><td><code>resolved\_share</code></td><td>FLOAT64</td><td><code>wallets\_resolved</code> divided by <code>wallets\_with\_edges</code>.</td></tr>
    <tr><td><code>wallets\_high</code></td><td>INT64</td><td>Resolved wallets at <code>high</code> confidence.</td></tr>
    <tr><td><code>wallets\_medium</code></td><td>INT64</td><td>Resolved wallets at <code>medium</code> confidence.</td></tr>
    <tr><td><code>wallets\_low</code></td><td>INT64</td><td>Resolved wallets at <code>low</code> confidence.</td></tr>
    <tr><td><code>wallets\_curated\_source</code></td><td>INT64</td><td>Resolved wallets whose <code>funding\_venue\_source</code> is <code>curated</code>.</td></tr>
    <tr><td><code>wallets\_detected\_source</code></td><td>INT64</td><td>Resolved wallets whose <code>funding\_venue\_source</code> is <code>detected</code>.</td></tr>
    <tr><td><code>wallets\_with\_jurisdiction</code></td><td>INT64</td><td>Resolved wallets with a <code>funding\_jurisdiction</code>.</td></tr>
    <tr><td><code>jurisdiction\_share</code></td><td>FLOAT64</td><td><code>wallets\_with\_jurisdiction</code> divided by <code>wallets\_resolved</code>.</td></tr>
    <tr><td><code>distinct\_venues</code></td><td>INT64</td><td>Distinct <code>funding\_venue\_project\_id</code> values on this chain.</td></tr>
    <tr><td><code>first\_edge\_at</code></td><td>TIMESTAMP</td><td>Earliest <code>funding\_first\_edge\_at</code> on this chain.</td></tr>
    <tr><td><code>last\_edge\_at</code></td><td>TIMESTAMP</td><td>Latest <code>funding\_first\_edge\_at</code> on this chain.</td></tr>
  </tbody>
</table>

## Sample queries

<Tabs>
  <Tab title="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'
    ```
  </Tab>

  <Tab title="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
    ```
  </Tab>

  <Tab title="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
    ```
  </Tab>
</Tabs>


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