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

# Robinhood Chain

> Everything the catalog holds for Robinhood Chain, from raw blocks to project activity.

Most of the catalog is queryable for Robinhood Chain, from the blocks themselves to the daily activity of the projects that run on it.

The chain's own record sits in the `robinhoodchain` dataset: one row per block, transaction, log and internal call. Everything above that sits in the catalog, where the Robinhood Chain rows are selected with `chain_id = 'robinhoodchain'`.

The section mirrors the catalog itself: the core entities, then the market verticals with data on Robinhood Chain.

## Layers

<table>
  <thead>
    <tr>
      <th width="180">Layer</th>
      <th width="110">Since</th>
      <th>What it holds</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/robinhoodchain/raw">Raw</a></td>
      <td>2026-04</td>
      <td>Blocks, transactions, logs and internal calls.</td>
    </tr>

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/robinhoodchain/projects">Projects</a></td>
      <td>2026-04</td>
      <td>Daily Fees and Revenue for each tracked project, broken out to Robinhood Chain.</td>
    </tr>

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/robinhoodchain/apps">Apps</a></td>
      <td>2026-06</td>
      <td>Daily Trading volume, TVL, Fees and Revenue for each tracked app, broken out to Robinhood Chain.</td>
    </tr>

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/robinhoodchain/assets">Assets</a></td>
      <td>2021-02</td>
      <td>Every curated asset issued on Robinhood Chain, with daily supply, holders and transfer activity.</td>
    </tr>

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/robinhoodchain/tokens">Tokens</a></td>
      <td><strong>In progress</strong></td>
      <td>Every ERC-20 transfer, both sides of every balance move, holder balances at query time, and daily prices.</td>
    </tr>

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/robinhoodchain/accounts">Accounts</a></td>
      <td><strong>In progress</strong></td>
      <td>Wallets and contracts labeled with the projects that own them.</td>
    </tr>

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/robinhoodchain/stablecoins">Stablecoins</a></td>
      <td>2026-05</td>
      <td>Every stablecoin issued on Robinhood Chain: supply, holders and transfers.</td>
    </tr>

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/robinhoodchain/tokenized-assets">Tokenized assets</a></td>
      <td>2024-01</td>
      <td>Tokenized stocks, funds and commodities issued on Robinhood Chain, tracked against their underlying instruments.</td>
    </tr>

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/robinhoodchain/dex">DEX</a></td>
      <td>2026-05</td>
      <td>Trading pools, their daily volume, value locked and fees.</td>
    </tr>

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/robinhoodchain/bridges">Bridges</a></td>
      <td>2026-05</td>
      <td>Cross-chain transfers that left Robinhood Chain or arrived on it, matched leg to leg.</td>
    </tr>
  </tbody>
</table>

## Filtering

`chain_id` reads `robinhoodchain` wherever a catalog table carries a chain, so the same filter selects Robinhood Chain everywhere. Some shapes ask for something else. The asset tables key on the asset or its deployment, so the chain comes from `dimensions.asset_tokens`, as the query below does. Project and app totals span every chain a project runs on, so one chain's share reads from `metrics_project_chains` and `metrics_app_chains`. A bridge transfer has a chain on each end and carries `source_chain_id` and `destination_chain_id`.

<Warning>
  Every table splits by day: the raw and event tables on `block_timestamp`, the daily tables on `timestamp`. Bound that column in every query; without a bound the query reads the whole table.
</Warning>

```sql theme={null}
select
    daily.timestamp,
    deployments.asset_id,
    assets.symbol,
    daily.market_cap_circulating_total
from `metrics_asset_tokens.market_cap_circulating_total_daily` as daily
join `dimensions.asset_tokens` as deployments
    using (asset_token_id)
join `dimensions.assets` as assets
    using (asset_id)
where deployments.chain_id = 'robinhoodchain'
  and daily.timestamp >= timestamp('2026-08-01')
  and daily.timestamp < timestamp('2026-08-02')
limit 100
```