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

# Cosmos Hub

> Standardized Cosmos Hub tables.

`cosmoshub` holds the standardized Cosmos Hub tables, following the schema documented in [the family overview](/docs/catalog/chain-verticals/cosmos/index) exactly, with no differences.

## Tables

<table>
  <thead>
    <tr>
      <th width="200">Table</th>
      <th width="90">Since</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td><code>blocks</code></td>
      <td>2019-12</td>
      <td>One row per block, with its transaction count and proposer.</td>
    </tr>

    <tr>
      <td><code>transactions</code></td>
      <td>2021-02</td>
      <td>One row per transaction, with its fee and result code.</td>
    </tr>

    <tr>
      <td><code>transaction\_messages</code></td>
      <td>2021-02</td>
      <td>One row per message inside a transaction.</td>
    </tr>

    <tr>
      <td><code>message\_events</code></td>
      <td>2021-02</td>
      <td>One row per event emitted during transaction execution.</td>
    </tr>

    <tr>
      <td><code>block\_events</code></td>
      <td>2021-02</td>
      <td>One row per event emitted outside a transaction.</td>
    </tr>
  </tbody>
</table>

## Sample queries

<Tabs>
  <Tab title="Daily success rate">
    **Count daily transactions and their success rate over one week.**

    ```sql theme={null}
    select
        timestamp_trunc(block_timestamp, day) as day,
        count(*) as transactions,
        countif(transaction_code = 0) as successful
    from `cosmoshub.transactions`
    where block_timestamp >= timestamp('2026-08-16')
      and block_timestamp < timestamp('2026-08-23')
    group by day
    order by day
    ```
  </Tab>

  <Tab title="Tokens tracked">
    **List the Cosmos Hub tokens we track, with the name the chain knows each one by.** Cosmos chains identify a token by a string called its denom, and that is what `token_address` holds: an `ibc/` hash for a voucher, or a `factory/` path for one the token factory minted.

    ```sql theme={null}
    select
        token_id,
        symbol,
        name,
        decimals,
        token_address
    from `dimensions.tokens`
    where chain_id = 'cosmoshub'
      and symbol is not null
    order by created_at
    limit 20
    ```
  </Tab>
</Tabs>

## Notes

The transaction tables begin on 2021-02-18, at the Cosmos Hub 4 upgrade, while `blocks` also covers the hub version before it.

The rest of the catalog holds one slice of Cosmos Hub: its tokens. Some arrived from another chain over IBC, the Cosmos transfer protocol, and are held as vouchers; the others were minted on Cosmos Hub itself by its token factory. No app, pool or tokenized asset table covers Cosmos Hub, so its activity comes from the raw tables above.

[Tokens](/docs/catalog/tokens/index) covers the token list and the daily price table built beside it. [Chains](/docs/catalog/chains/index) covers the list of chains we track.