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

# Other ecosystems

> Standardized tables for chains that match none of the other families.

These chains work differently enough inside that they match none of the other families, and what they have in common with each other is that and little else. Each one keeps its own set of tables.

The [Tables](#tables) section below says where each chain's tables are documented and names the two conventions that hold across all of them.

## Chains

<table>
  <thead>
    <tr>
      <th width="200">Chain</th>
      <th width="180">`chain_id`</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>[Algorand](https://tokenterminal.com/docs/catalog/chain-verticals/other/algorand.md)</td>
      <td>`algorand`</td>
    </tr>

    <tr>
      <td>[Cardano](https://tokenterminal.com/docs/catalog/chain-verticals/other/cardano.md)</td>
      <td>`cardano`</td>
    </tr>

    <tr>
      <td>[Flow](https://tokenterminal.com/docs/catalog/chain-verticals/other/flow.md)</td>
      <td>`flow`</td>
    </tr>

    <tr>
      <td>[Hedera](https://tokenterminal.com/docs/catalog/chain-verticals/other/hedera.md)</td>
      <td>`hedera`</td>
    </tr>

    <tr>
      <td>[NEAR](https://tokenterminal.com/docs/catalog/chain-verticals/other/near.md)</td>
      <td>`near`</td>
    </tr>

    <tr>
      <td>[Ripple](https://tokenterminal.com/docs/catalog/chain-verticals/other/ripple.md)</td>
      <td>`ripple`</td>
    </tr>

    <tr>
      <td>[Starknet](https://tokenterminal.com/docs/catalog/chain-verticals/other/starknet.md)</td>
      <td>`starknet`</td>
    </tr>

    <tr>
      <td>[Stellar](https://tokenterminal.com/docs/catalog/chain-verticals/other/stellar.md)</td>
      <td>`stellar`</td>
    </tr>

    <tr>
      <td>[TON](https://tokenterminal.com/docs/catalog/chain-verticals/other/ton.md)</td>
      <td>`ton`</td>
    </tr>

    <tr>
      <td>[Tron](https://tokenterminal.com/docs/catalog/chain-verticals/other/tron.md)</td>
      <td>`tron`</td>
    </tr>
  </tbody>
</table>

## Tables

Each chain's tables are listed on its own page above, with every column and the month its history starts. Two habits hold across every chain here, whatever its tables are called.

A table with one row per transaction or per event is split by day on `block_timestamp`, and a table of blocks on `timestamp`. Filter on that column in every query: without a filter the query reads the whole table.

Identifiers reuse the familiar names wherever the chain has a matching idea: `block_number`, `transaction_hash`, and `*_index` for a position within something.

## Exceptions

* Ripple and Stellar call their blocks ledgers; on both chains the ledgers land in `blocks`.
* Stellar splits a transaction into a list of operations, so `operations` holds what a transaction did and `effects` holds what each operation changed.
* TON's `block_headers` and `shards` are unpartitioned, so a query against either reads the whole table. Its `transactions` and `messages` split by day on `block_timestamp`, and `blocks` on `timestamp`, as usual.
* Tron writes each address in two forms and both are here: the `*_hex` columns hold the form that looks like an Ethereum address, and the plain `address`-style columns hold the base58 form that starts with a T. Pick whichever matches the addresses you are joining against.


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