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

# Scroll

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

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

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

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

## 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/scroll/raw">Raw</a></td>
      <td>2023-10</td>
      <td>Blocks, transactions, logs and internal calls.</td>
    </tr>

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/scroll/projects">Projects</a></td>
      <td>2023-10</td>
      <td>Daily Fees and Revenue for each tracked project, broken out to Scroll.</td>
    </tr>

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

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/scroll/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/scroll/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/scroll/stablecoins">Stablecoins</a></td>
      <td>2024-03</td>
      <td>Every stablecoin issued on Scroll: supply, holders and transfers.</td>
    </tr>

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/scroll/lending">Lending</a></td>
      <td><strong>In progress</strong></td>
      <td>The lending markets deployed on Scroll, the asset each one lends, and the lending facts.</td>
    </tr>

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/scroll/bridges">Bridges</a></td>
      <td>2024-03</td>
      <td>Cross-chain transfers that left Scroll or arrived on it, matched leg to leg.</td>
    </tr>
  </tbody>
</table>

## Filtering

`chain_id` reads `scroll` wherever a catalog table carries a chain, so the same filter selects Scroll 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 = 'scroll'
  and daily.timestamp >= timestamp('2026-08-01')
  and daily.timestamp < timestamp('2026-08-02')
limit 100
```