Most of the catalog is queryable for BOB, from the blocks themselves to the daily activity of the projects that run on it.
The chain’s own record sits in the bob dataset: one row per block, transaction, log and internal call. Everything above that sits in the catalog, where the BOB rows are selected with chain_id = 'bob'.
The section mirrors the catalog itself: the core entities, then the market verticals with data on BOB.
Layers
| Layer | Since | What it holds |
|---|
| Raw | 2024-04 | Blocks, transactions, logs and internal calls. |
| Projects | 2024-09 | Daily trading and bridge volume for each tracked app and project, broken out to BOB. |
| Assets | 2025-02 | Every curated asset issued on BOB, with daily supply, holders and transfer activity. |
| 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. |
| Stablecoins | 2025-02 | Every stablecoin issued on BOB: supply, holders and transfers. |
| Bridges | 2024-09 | Cross-chain transfers that left BOB or arrived on it, matched leg to leg. |
Filtering
chain_id reads bob in every catalog table that mentions a chain, so the same filter selects BOB everywhere. Bridge transfers are the one exception: a transfer has a chain on each end and carries source_chain_id and destination_chain_id instead.
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.
