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

# Assets

> Every curated asset issued on MegaETH, with daily supply, holders and transfer activity.

An asset is a financial instrument someone has put onchain, and a deployment is one asset on one chain at one contract address. The first query below counts what MegaETH holds, by kind.

* [`dimensions.asset_tokens`](https://tokenterminal.com/docs/catalog/assets/registry): one row per deployment.
* [`metrics_asset_tokens`](https://tokenterminal.com/docs/catalog/assets/metrics): one table per measure, one row per deployment per day.

Every column is documented at [Assets](https://tokenterminal.com/docs/catalog/assets/index.md). [Real-world assets](https://tokenterminal.com/docs/catalog/chain-verticals/evm/megaeth/real-world-assets.md) scopes this layer further.

## Sample queries

> [tab] Largest assets
>
> **Rank the assets on MegaETH by circulating market cap.** Circulating market cap is the supply held by the public, valued in USD, with tokens the issuer has minted but not released left out.
>
> ```sql theme={null}
> select
>     assets.symbol,
>     assets.asset_type,
>     daily.market_cap_circulating
> from `metrics_asset_tokens.market_cap_circulating_daily` as daily
> join `dimensions.asset_tokens` as deployments
>     using (asset_token_id)
> join `dimensions.assets` as assets
>     using (asset_id)
> where daily.timestamp >= timestamp('2026-08-22')
>   and daily.timestamp < timestamp('2026-08-23')
>   and deployments.chain_id = 'megaeth'
> order by daily.market_cap_circulating desc
> limit 20
> ```

> [tab] Deployments by kind
>
> **Count MegaETH deployments by asset kind, and how many were issued on MegaETH itself.** A deployment is native when the issuer minted the token on MegaETH, and bridged when the token stands in for supply issued somewhere else.
>
> ```sql theme={null}
> select
>     assets.asset_type,
>     count(*) as deployments,
>     countif(deployments.bridged_status = 'native') as native
> from `dimensions.asset_tokens` as deployments
> join `dimensions.assets` as assets
>     using (asset_id)
> where deployments.chain_id = 'megaeth'
> group by assets.asset_type
> order by deployments desc
> ```

> [tab] One deployment's series
>
> **Read one MegaETH deployment's daily supply and holders.** `asset_token_id` is the asset, the token address and the chain with dashes. Each measure is its own table, so reading two means a join on `asset_token_id` and `timestamp`. Both tables here read the native side of the deployment. A bridged deployment reads the `_bridged` pair instead.
>
> ```sql theme={null}
> with supply as (
>     select
>         timestamp,
>         market_cap_circulating_native
>     from `metrics_asset_tokens.market_cap_circulating_native_daily`
>     where asset_token_id = 'cusd-0xcccc62962d17b8914c62d74ffb843d73b2a3cccc-megaeth'
>       and timestamp >= timestamp('2026-08-16')
>       and timestamp < timestamp('2026-08-23')
> ),
>
> holders as (
>     select
>         timestamp,
>         holders_native
>     from `metrics_asset_tokens.holders_native_daily`
>     where asset_token_id = 'cusd-0xcccc62962d17b8914c62d74ffb843d73b2a3cccc-megaeth'
>       and timestamp >= timestamp('2026-08-16')
>       and timestamp < timestamp('2026-08-23')
> )
>
> select
>     timestamp,
>     supply.market_cap_circulating_native,
>     holders.holders_native
> from supply
> left join holders
>     using (timestamp)
> order by timestamp
> ```


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