Analytics.
PERIOD SHAREStacked venue analytics from our owned daily metrics table. Use the period controls on each chart to compare daily, weekly, monthly and quarterly venue activity as the dataset fills.
Perps volume
Notional trading volume stacked by venue
Open interest
Open interest stacked by venue
Daily active users
Venue-level unique users once user activity sources are wired
Fees
Estimated trading fees stacked by venue
Revenue per platform
Estimated platform revenue using an 85/15 taker-maker mix
RWA vs crypto — volume
Real-world-asset (stocks, FX, commodities, indices) share of perp volume — owned, forward-only
RWA vs crypto — open interest
Real-world-asset share of perp open interest — owned, forward-only
Venue onboarding checklist
Minimum inputs needed to add venues cleanly to the landing page and analytics page.
Venue metadata: id, display name, color, logo, website, trading URL and referral URL.
Market catalog: tradable pairs, canonical asset mapping, active/delisted status and contract type.
Core market data: mark price, index price, 24h change, 24h volume and open interest in USD terms.
Funding data: funding rate, native interval, countdown/next funding timestamp and unit convention.
Historical backfill: daily venue-level volume, open interest, fees, revenue and user activity, plus source labels and timezone rules.
Fees and revenue: maker/taker schedule, fee tiers, spread model or direct fee/revenue endpoint.
User activity: daily unique traders or wallets by venue, with a clear definition and deduping rules.
API operations: auth needs, rate limits, pagination, freshness timestamp, retries and failure modes.
Validation: unit checks, stale-data detection, duplicate market handling and sample payload fixtures.
Implementation: exchange registry entry, fetcher, landing-page card fields, analytics inclusion and test route.