Schemas
Column reference for the raw captured datasets. Raw event tables carry the live stream's exact field set plus two archive columns (height, block_time). Backtest on history, deploy on the feed with minimal remapping. Use this reference when you request an export.
Conventions
- Raw financial values (prices, sizes, notionals, PnL, fees) use decimal strings rather than binary floats. Calculated custom fields are documented with the delivery.
- Sides are
B(buy/bid) andA(sell/ask); market symbols cover perps (BTC), spot (@N), and HIP-3 (dex:SYMBOL). - Every raw table is ordered and partitioned by time. Filter
block_time(andcoinwhere present) before anything else.
trades
One row per executed fill, currently growing by ~6.5M rows a day. Captured rows can include trader address, position context, realized PnL, fees, maker/taker, and liquidation linkage.
Live equivalent: Trades & swaps. The liquidation object is preserved as a nested column; for flat liquidation analysis use the liquidations derived table below.
transactions
One row per order-status event: placements, cancels, fills, triggers, rejections. 1.65B+ events archived, ~725M added per day.
Live equivalent: Order lifecycle.
book_updates
One row per captured order-book delta. Apply deltas inheight order to a compatible snapshot when rebuilding a book within the available captured range.
Live equivalent: Raw book diffs.
top_of_book
One row per best-bid/ask tick per market.
Live equivalent: L2 book subscribed with n_levels: 1.
twaps
One row per TWAP status or progress event. executed_ntl / executed_sz gives the average fill price so far; twap_id joins to the same column on trades.
Live equivalent: TWAP algos.
corporate-actions
One row per ledger or market event: per-user funding payments with the applied rate, liquidations, deposits, withdrawals, and position updates, discriminated by type.
Live equivalent: Events.
Need a calculated schema?
OHLCV, wallet PnL, liquidation, funding, and other derived shapes are custom dataset examples, not precomputed self-serve tables. Include the required fields and calculation rules when you contact us; we confirm the source coverage and return an agreed schema with the scope.