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

# Move ecosystem

> Standardized tables for the Move chains Aptos, Movement and Sui.

Move is the programming language these three chains run their contracts in, which is what makes them a family. They do not all keep the same records, though, because they store what a transaction changed in two different ways.

Aptos and Movement list the changes themselves, and carry `blocks`, `transactions`, `events`, `changes`, `resources`, `modules` and `table_items`. Sui treats everything on the chain as an object with an owner, and records the objects a transaction touched: `blocks`, `transactions`, `events`, `move_calls`, `move_packages`, `objects`, `transaction_objects` and `wrapped_objects`.

## Chains

<table>
  <thead>
    <tr>
      <th width="160">Chain</th>
      <th width="140"><code>chain\_id</code></th>
      <th width="90">blocks</th>
      <th width="120">transactions</th>
      <th width="90">events</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>Aptos</td>
      <td><code>aptos</code></td>
      <td><span class="tt-check">✓</span></td>
      <td><span class="tt-check">✓</span></td>
      <td><span class="tt-check">✓</span></td>
    </tr>

    <tr>
      <td>Movement</td>
      <td><code>movement</code></td>
      <td><span class="tt-check">✓</span></td>
      <td><span class="tt-check">✓</span></td>
      <td><span class="tt-check">✓</span></td>
    </tr>

    <tr>
      <td>Sui</td>
      <td><code>sui</code></td>
      <td><span class="tt-check">✓</span></td>
      <td><span class="tt-check">✓</span></td>
      <td><span class="tt-check">✓</span></td>
    </tr>
  </tbody>
</table>

## Exceptions

* Sui's tables differ from the Aptos ones because the chain works differently, not because anything is missing.
* Sui's `blocks` rows are checkpoints rather than blocks, and its `transactions` and `events` carry gas costs and execution effects instead of Move-style changes.
* Aptos and Movement additionally carry `changes`, `resources`, `modules` and `table_items`, the tables that record what a transaction wrote.
* Sui additionally carries `move_calls`, `move_packages`, `objects`, `transaction_objects` and `wrapped_objects`, the tables that record the objects a transaction touched.

## Chain pages

[Aptos](/docs/catalog/chain-verticals/move/aptos) and [Sui](/docs/catalog/chain-verticals/move/sui) have pages of their own. Movement uses the Aptos tables exactly.