> ## 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, and that shared language is what makes them a family. They record what a transaction changed in two different ways, so their tables come in two shapes.

Aptos and Movement list the changes themselves, in `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, in `blocks`, `transactions`, `events`, `move_calls`, `move_packages`, `objects`, `transaction_objects` and `wrapped_objects`.

The [Tables](#tables) section below says which tables each shape has and where their columns are documented.

## Chains

<table>
  <thead>
    <tr>
      <th width="160">Chain</th>
      <th width="140">`chain_id`</th>
      <th width="90">blocks</th>
      <th width="120">transactions</th>
      <th width="90">events</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>Aptos</td>
      <td>`aptos`</td>
      <td>✓</td>
      <td>✓</td>
      <td>✓</td>
    </tr>

    <tr>
      <td>Movement</td>
      <td>`movement`</td>
      <td>✓</td>
      <td>✓</td>
      <td>✓</td>
    </tr>

    <tr>
      <td>Sui</td>
      <td>`sui`</td>
      <td>✓</td>
      <td>✓</td>
      <td>✓</td>
    </tr>
  </tbody>
</table>

## Tables

All three chains have `blocks`, `transactions` and `events`: the blocks the network agreed on, the transactions inside them, and the notes the chain wrote while running each one. On top of those, each shape adds tables of its own.

The Aptos shape adds `changes`, `resources`, `modules` and `table_items`, which record what a transaction wrote. Its columns are documented on the [Aptos](https://tokenterminal.com/docs/catalog/chain-verticals/move/aptos.md) page, and Movement uses those same tables exactly.

The Sui shape adds `move_calls`, `move_packages`, `objects`, `transaction_objects` and `wrapped_objects`, which record the objects a transaction touched and the code it called. Its columns are documented on the [Sui](https://tokenterminal.com/docs/catalog/chain-verticals/move/sui.md) page.

> [!WARNING]
>
> On both shapes every table except `blocks` splits by day on `block_timestamp`, and `blocks` on `timestamp`. Bound that column in every query; without a bound the query reads the whole table.

## Exceptions

Sui is where the family splits, and it splits because the chain itself works differently.

* Sui's `blocks` rows are checkpoints, the groups it batches transactions into, rather than blocks in the usual sense.
* Sui's `transactions` and `events` hold gas costs and execution effects where the Aptos ones hold Move-style changes.
* Sui's object tables stand in for the Aptos change tables: `objects`, `transaction_objects` and `wrapped_objects` record every version of every object a transaction touched.


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