The chain’s own record is queryable for Gravity Alpha, with its eligible catalog layers above it.
The chain’s own record sits in the gravityalpha dataset: one row per block, transaction, log and internal call. Everything above that sits in the catalog, where the Gravity Alpha rows are selected with chain_id = 'gravityalpha'.
The section mirrors the catalog itself: the core entities, then the market verticals with data on Gravity Alpha.
Layers
| Layer | Since | What it holds |
|---|
| Raw | 2024-05 | Blocks, transactions, logs and internal calls. |
| Projects | 2024-07 | Daily trading and bridge volume for each tracked app and project, broken out to Gravity Alpha. |
| Tokens | In progress | Every ERC-20 transfer, both sides of every balance move, holder balances at query time, and daily prices. |
| Accounts | In progress | Wallets and contracts labeled with the projects that own them. |
| Bridges | 2024-07 | Cross-chain transfers that left Gravity Alpha or arrived on it, matched leg to leg. |
Filtering
chain_id reads gravityalpha wherever a catalog table carries a chain, so the same filter selects Gravity Alpha everywhere. Some shapes ask for something else. The asset tables key on the asset or its deployment, so the chain comes from dimensions.asset_tokens, as the query below does. Project and app totals span every chain a project runs on, so one chain’s share reads from metrics_project_chains and metrics_app_chains. A bridge transfer has a chain on each end and carries source_chain_id and destination_chain_id.
Every table splits by day: the raw and event tables on block_timestamp, the daily tables on timestamp. Bound that column in every query; without a bound the query reads the whole table.
