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

# Humanity

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

The chain's own record is queryable for Humanity, with its eligible catalog layers above it.

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

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

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

    <tr>
      <td><a href="/docs/catalog/chain-verticals/evm/humanity/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/humanity/accounts">Accounts</a></td>
      <td><strong>In progress</strong></td>
      <td>Wallets and contracts labeled with the projects that own them.</td>
    </tr>
  </tbody>
</table>

## Filtering

`chain_id` reads `humanity` wherever a catalog table carries a chain, so the same filter selects Humanity 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
    block_timestamp,
    transaction_hash,
    from_address,
    to_address
from `humanity.transactions`
where block_timestamp >= timestamp('2026-08-01')
  and block_timestamp < timestamp('2026-08-02')
limit 100
```