Stats
Stats & Transparency
Topaz publishes a full, snapshot-backed analytics surface — protocol KPIs, every pool, the foundation's veTOPAZ activity, and concentrated-liquidity fee dynamics. Browse it in the dashboard or pull it from the public JSON API.
What's published
Three layers, one source of truth. The dashboard, the docs, and the API all read from the same hourly snapshot tables — so what you see on the page is exactly what an integrator gets from the API at the same timestamp.
Overview
/stats ↗Protocol-wide TVL, volume, fees, and emissions, plus a 30-day TVL chart, top pools by TVL, and a snapshot of foundation positioning.
Pools
/stats/pools ↗Every v2 and Slipstream pool ranked by TVL, 24h volume, 24h fees, or fee APR. Filter by pool type and drill into per-pool history.
Foundation
/stats/foundation ↗Foundation veTOPAZ holdings, the gauges they vote on each epoch, bribes claimed, and a per-gauge KPI classification (scale / repeat / monitor / reduce / stop).
Dynamic Fees
/stats/dynamic-fees ↗Concentrated-liquidity pools with dynamic fees enabled — live fee level, baseline, and how often the fee has flexed in response to volatility.
Methodology
/stats/methodology ↗Every number on this dashboard, defined: data sources, snapshot cadence, KPI formulas, and known caveats. Versioned so you can pin to a methodology revision.
How the data is produced
A scheduled job (/api/cron/analytics-snapshot) runs hourly, reads the Topaz v2 and Slipstream subgraphs plus on-chain state via BNB Chain RPC, and writes a versioned snapshot row per dataset (protocol totals, pools, gauges, votes, bribes, ve stats, dynamic-fee pools, foundation KPIs). The dashboards and the API both serve from these snapshot tables, never from live RPC — which means every reader at a given moment is looking at the same numbers.
snapshotAt timestamp it was generated from, so you can always tell how fresh a number is. Hot reads (/api/stats/live/dynamic-fees) bypass the snapshot layer and hit RPC directly with a short edge cache.Foundation transparency
The Foundation page publishes the protocol's own veTOPAZ activity in full: which veNFTs the foundation holds, where it votes each epoch, every bribe it has claimed, and a per-gauge KPI classification that scores whether the foundation's vote on that pool is actually earning its keep. The same data is available via the API under /api/stats/foundation for independent verification.
The list of foundation veNFT IDs and the foundation wallet are published openly in the config endpoint — anyone can audit the inputs.
Build on the data
Everything the dashboards render is exposed as a typed JSON API. Pull protocol KPIs into your own dashboard, monitor pool TVL changes, watch dynamic-fee triggers in real time, or verify foundation vote behavior — all without running an indexer.
See the Data API reference for the full endpoint list, the shared response envelope, query parameters, and curl examples.
Continue reading
Data API Reference →
Every public JSON endpoint with parameters, response shapes, caching, and examples.
Methodology →
Source-of-truth notes for every metric — formulas, data sources, version pinning.
Foundation Dashboard →
Live view of foundation veTOPAZ holdings, voting, and KPI effectiveness.
Contracts →
Every deployed contract address with verified BscScan links.