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

# Berachain

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

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

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

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

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

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/berachain/projects">Projects</a></td>
      <td>2025-01</td>
      <td>Daily trading and bridge volume for each tracked app and project, broken out to Berachain.</td>
    </tr>

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

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

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

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

## Filtering

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