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

# Projects

> Daily Fees and Revenue for each tracked app and project, broken out to Hedera EVM.

The top of the catalog breaks activity down by who ran it. A project is the entity behind a protocol, such as Uniswap. An app is one deployed version that project runs, such as `uniswap-v3`.

* [`metrics_app_chains`](/docs/catalog/projects/metrics): one table per measure, one row per app per chain per day.
* [`metrics_project_chains`](/docs/catalog/projects/metrics): one table per measure, one row per project per chain per day.

Every column is documented at [Projects ▸ Metrics](/docs/catalog/projects/metrics).

## Sample queries

<Tabs>
  <Tab title="Apps on Hedera EVM">
    **Rank the apps active on Hedera EVM by fees over one week.**

    ```sql theme={null}
    select
        apps.name,
        sum(daily.fees) as fees
    from `metrics_app_chains.fees_daily` as daily
    join `dimensions.apps` as apps
        using (app_id)
    where daily.timestamp >= timestamp('2026-08-16')
      and daily.timestamp < timestamp('2026-08-23')
      and daily.chain_id = 'hederaevm'
    group by apps.name
    order by fees desc
    ```
  </Tab>

  <Tab title="One project's series">
    **Read one project's daily Hedera EVM fees.**

    ```sql theme={null}
    select
        daily.timestamp,
        daily.fees
    from `metrics_project_chains.fees_daily` as daily
    where daily.timestamp >= timestamp('2026-08-16')
      and daily.timestamp < timestamp('2026-08-23')
      and daily.chain_id = 'hederaevm'
      and daily.project_id = 'uniswap'
    order by daily.timestamp
    ```
  </Tab>

  <Tab title="Hedera EVM's share">
    **Work out how much of a project runs on Hedera EVM.** Dropping the chain filter and grouping by chain turns the same table into a comparison across every chain the project operates on.

    ```sql theme={null}
    with by_chain as (
        select
            chain_id,
            sum(fees) as fees
        from `metrics_project_chains.fees_daily`
        where timestamp >= timestamp('2026-08-16')
          and timestamp < timestamp('2026-08-23')
          and project_id = 'uniswap'
        group by chain_id
    )

    select
        chain_id,
        fees,
        fees / sum(fees) over () as share
    from by_chain
    order by fees desc
    limit 20
    ```
  </Tab>
</Tabs>

## Notes

The two tables hold the same measures at two levels. A project figure for one chain and one day is the sum of its apps on that chain and day, worked out once and served at both levels. The same holds across chains: a project's chain rows for one day sum to what `metrics_projects` serves without the chain breakout, so use the chain tables when the chain breakdown is the question.

Each app's activity has a finer table beneath it: bridge volume breaks down transfer by transfer on [Bridges](/docs/catalog/chain-verticals/evm/hederaevm/bridges). Start with the daily figures and drop down when the question needs the detail.