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

# Chains

> Blockchains, their transactions, and the fees and revenue each one earns.

A chain is a blockchain: the network that transactions run on. Chains sit alongside projects and apps rather than inside them, and `dimensions.chains` names the project behind every chain.

## Pages

<CardGroup cols={3}>
  <Card title="Registry" icon="table-list" href="/docs/catalog/chains/registry">
    Chain names, and the project that runs each one.
  </Card>

  <Card title="Transactions" icon="bolt" href="/docs/catalog/chains/transactions">
    Individual transactions with the fee each one paid. **In progress.**
  </Card>

  <Card title="Metrics" icon="chart-line" href="/docs/catalog/chains/metrics">
    Daily chain fees, revenue, and the fees passed on.
  </Card>
</CardGroup>

## Chains and projects

Where a project runs a blockchain, the two match one to one: gas paid on HyperEVM shows up in the [daily chain table](/docs/catalog/chains/metrics) under `chain_id = 'hyperevm'` and rolls into Hyperliquid's project fees. A chain's project defaults to the chain's own, and is overridden where another project's app runs it: `unichain` resolves to `uniswap`.

The daily chain table carries no project column; join `chains.project_id` to attribute a chain, and the transaction records already carry that column on every row.