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

# Registry

> Chain names, and the project that runs each one.

The identity table behind every chain figure. Every metric table joins to it, and [Coverage](https://tokenterminal.com/docs/catalog/chains.md) introduces the grain.

## Columns

<table>
  <thead>
    <tr>
      <th width="280">Column</th>
      <th width="130">Type</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>`chain_id`</td>
      <td>`STRING`</td>
      <td>Identifier of the chain. Every table that mentions a chain joins on this.</td>
    </tr>

    <tr>
      <td>`project_id`</td>
      <td>`STRING`</td>
      <td>Project that runs the chain. Defaults to the chain's own project, and names another project where that project's app runs the chain: `unichain` resolves to `uniswap`.</td>
    </tr>

    <tr>
      <td>`name`</td>
      <td>`STRING`</td>
      <td>Display name.</td>
    </tr>

    <tr>
      <td>`logo`</td>
      <td>`STRING`</td>
      <td>The chain's logo URL, with its content hash on the end so a changed logo is a new URL.</td>
    </tr>

    <tr>
      <td>`market_sectors`</td>
      <td>`ARRAY<STRING>`</td>
      <td>The market sectors the chain belongs to, most relevant first.</td>
    </tr>

    <tr>
      <td>`primary_market_sector`</td>
      <td>`STRING`</td>
      <td>The first of `market_sectors`.</td>
    </tr>

    <tr>
      <td>`chain_family`</td>
      <td>`STRING`</td>
      <td>`evm` or `svm`, null when the chain is unmapped. Every chain in one family is summed together for a key's activity, such as `region` on [Accounts ▸ Registry](https://tokenterminal.com/docs/catalog/accounts/registry.md).</td>
    </tr>
  </tbody>
</table>

## Sample queries

**Chain identity**

`chain_id` is the value every other table keys on, and this is the table that spells out what it stands for.

```sql theme={null}
select
    chain_id,
    name,
    project_id
from `dimensions.chains`
where chain_id = 'hyperevm'
```

**Chains for one project**

`project_id` is the one place a chain's operator is recorded, so a change of operator reaches every query that joins here.

```sql theme={null}
select
    chain_id,
    name
from `dimensions.chains`
where project_id = 'uniswap'
order by chain_id
```

**Chain to project**

The daily chain tables key on `chain_id` alone, so putting a project's name beside a chain's figures means joining `dimensions.projects` through `project_id`.

```sql theme={null}
select
    chains.chain_id,
    chains.name,
    chains.project_id,
    projects.name as project_name
from `dimensions.chains` as chains
join `dimensions.projects` as projects
    using (project_id)
order by chains.chain_id
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.