Projects

The top of the catalog breaks activity down by who ran it. A project is the entity behind a protocol, such as Uniswap; its apps’ figures on Optimism sit on Apps.

metrics_project_chains: one table per measure, one row per project per chain per day.

Every column is documented at Projects ▸ Metrics.

Sample queries

One project's series
Optimism's share

Read one project’s daily Optimism fees.

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 = 'optimism'
  and daily.project_id = 'uniswap'
order by daily.timestamp

Work out how much of a project runs on Optimism. Dropping the chain filter and grouping by chain turns the same table into a comparison across every chain the project operates on.

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

Notes

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 Apps page carries the app side. 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.

Overview

Core entities

Core datasets

Market verticals

Chain verticals

Sample queries

Notes

​Sample queries

​Notes

Sample queries

Notes