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

# X Layer

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

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

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

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

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

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

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

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

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

## Filtering

`chain_id` reads `xlayer` in every catalog table that mentions a chain, so the same filter selects X Layer everywhere. Bridge transfers are the one exception: a transfer has a chain on each end and carries `source_chain_id` and `destination_chain_id` instead.

<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
    timestamp,
    asset_id,
    symbol,
    market_cap_circulating_total
from `metrics.asset_tokens_daily`
where chain_id = 'xlayer'
  and timestamp >= timestamp('2026-08-01')
  and timestamp < timestamp('2026-08-02')
limit 100
```