> ## 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 hit rate

> Curated deposit anchors against detected deposit addresses, per venue and chain.

One row per venue and chain, comparing its curated deposit anchors against the deposit addresses detected from wallet behavior. `curated_hit_rate` is `curated_also_detected` divided by `curated_deposit_wallets`, null where `curated_deposit_wallets` is zero.

## Columns

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

  <tbody>
    <tr><td><code>venue\_project\_id</code></td><td>STRING</td><td>Venue the wallets are compared for.</td></tr>
    <tr><td><code>chain\_id</code></td><td>STRING</td><td>Chain the wallets are on.</td></tr>
    <tr><td><code>curated\_deposit\_wallets</code></td><td>INT64</td><td>Venue's curated deposit anchors on this chain.</td></tr>
    <tr><td><code>detected\_deposit\_addresses</code></td><td>INT64</td><td>Distinct counterparty addresses this venue's edges detected as deposit addresses on this chain.</td></tr>
    <tr><td><code>curated\_also\_detected</code></td><td>INT64</td><td>Curated deposit anchors that also appear as a detected counterparty.</td></tr>
    <tr><td><code>curated\_hit\_rate</code></td><td>FLOAT64</td><td><code>curated\_also\_detected</code> divided by <code>curated\_deposit\_wallets</code>. Null where <code>curated\_deposit\_wallets</code> is zero.</td></tr>
  </tbody>
</table>

## Sample queries

<Tabs>
  <Tab title="One venue's hit rate by chain">
    A high `curated_hit_rate` on a chain means the detector is rediscovering the same anchors the registry already curated there.

    ```sql theme={null}
    select
        chain_id,
        curated_deposit_wallets,
        detected_deposit_addresses,
        curated_hit_rate
    from `reports_accounts.funding_hit_rate`
    where venue_project_id = 'coinbase'
    order by chain_id
    ```
  </Tab>

  <Tab title="Every venue and chain, ranked by hit rate">
    Filtering `curated_deposit_wallets > 0` drops the pairs `curated_hit_rate` is null for.

    ```sql theme={null}
    select
        venue_project_id,
        chain_id,
        curated_deposit_wallets,
        curated_hit_rate
    from `reports_accounts.funding_hit_rate`
    where curated_deposit_wallets > 0
    order by curated_hit_rate desc
    limit 50
    ```
  </Tab>

  <Tab title="Venue name alongside the hit rate">
    `venue_project_id` joins `dimensions.projects` for the display name.

    ```sql theme={null}
    select
        projects.name,
        rate.chain_id,
        rate.curated_deposit_wallets,
        rate.curated_hit_rate
    from `reports_accounts.funding_hit_rate` as rate
    join `dimensions.projects` as projects
        on rate.venue_project_id = projects.project_id
    where rate.curated_deposit_wallets > 0
    order by rate.curated_hit_rate desc
    limit 50
    ```
  </Tab>
</Tabs>


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