How to build real-time Hyperliquid Hypercore data pipelines

Overview

Goldsky provides curated Hyperliquid Hypercore datasets for blocks, fills, trades, transactions, and miscellaneous events, making it easy to build pipelines for perp and spot market analysis.

Reach out to support@goldsky.com for dataset access.

Available datasets:

hypercore.blocks — Per-block metadata (height, time, proposer, hardfork)
hypercore.fills — Every individual fill (a single execution against a resting order), including liquidation details
hypercore.trades — Market trades, one row per trade, reconstructed by pairing the two fills under the same trade
hypercore.transactions — Signed-action transactions with their paired execution response
hypercore.misc_events — Miscellaneous event data

Schema Reference

`hypercore.blocks` (v1.0.0)

Per-block metadata.

Column	Type	Description
`id`	string	pk
`block_number`	uint64	Block height
`block_time`	int64	Block time, epoch ms
`parent_round`	uint64	Parent block height (`abci_block.parent_round`)
`proposer`	string	Proposing validator address
`hardfork_version`	uint32	Active hardfork version
`hardfork_round`	uint64	Activation round of the active hardfork

`hypercore.fills` (v1.0.0)

Every individual fill — a single execution against a resting order. Liquidation fills carry the extra liquidation_* columns.

Column	Type	Description
`id`	string	pk
`block_number`	uint64	Block height
`block_time`	int64	Block time, epoch ms
`fill_index`	int	Position in the block’s `fills` list
`timestamp`	int64	Fill time, epoch ms
`user`	string	Address whose order executed
`coin`	string	Perp symbol or spot pair id
`side`	string	`B` (buy) / `A` (sell)
`dir`	string	Direction, e.g. `Open Long`, `Close Short`
`price`	decimal(38,18)	Fill price
`size`	decimal(38,18)	Fill size
`fee`	decimal(38,18)	Fee, denominated in `fee_token`
`fee_token`	string	Fee denomination token
`closed_pnl`	decimal(38,18)	Closed PnL, USD
`start_position`	decimal(38,18)	Position before the fill
`hash`	string	Fill hash
`order_id`	uint64	Order id (`oid`)
`trade_id`	uint64	Trade id (`tid`). The two fills of a trade share it.
`crossed`	bool	Whether the fill crossed the spread (was the aggressor)
`builder_fee`	decimal(38,18)	Builder fee
`hip3_deployer_fee`	decimal(38,18)	HIP-3 deployer fee
`client_order_id`	string	Client order id (`cloid`)
`twap_id`	int64	TWAP order id
`liquidation_liquidated_user`	string	Address whose position was liquidated
`liquidation_mark_px`	decimal(38,18)	Mark price at liquidation
`liquidation_method`	string	Liquidation method, e.g. `market` / `backstop`

`hypercore.trades` (v1.0.0)

Market trades — one row per trade, reconstructed by pairing the two fills under the same trade.

Column	Type	Description
`id`	string	pk
`block_number`	uint64	Block height
`block_time`	int64	Block time, epoch ms
`trade_index`	uint32	Position of the trade within the block
`timestamp`	int64	Trade time, epoch ms (from the canonical leg)
`coin`	string	The traded asset. For a HIP-4 row, the side-0 (canonical) token.
`price`	decimal(38,18)	Trade price, canonical-leg
`size`	decimal(38,18)	Trade size
`side`	string	The crossing (taker) fill’s side: `B` / `A`
`transaction_hash`	string	Fill hash; NULL when the source hash is all-zero (Hyperliquid’s absent hash).
`trade_id`	uint64	The canonical (side-0) leg’s `tid`
`is_outcome_market`	bool	True when the row came from HIP-4 pairing
`outcome_id`	uint64	The outcome market id (`750` for assets `#7500` / `#7501`); NULL for ordinary trades.

`hypercore.transactions` (v1.0.0)

Signed-action transactions with their paired execution response.

Column	Type	Description
`id`	string	pk
`block_number`	uint64	Block height
`block_time`	int64	Block time, epoch ms
`transaction_index`	int	Position in the block’s `transactions` list
`bundle_hash`	string	Hash of the enclosing signed-action bundle. Not unique per row.
`broadcaster`	string	Address that broadcast the bundle
`broadcaster_nonce`	int64	The bundle’s broadcaster nonce
`signer_r`	string	ECDSA signature `r`
`signer_s`	string	ECDSA signature `s`
`signer_v`	int64	ECDSA signature `v`
`vault_address`	string	Vault/subaccount the action was placed on behalf of
`nonce`	int64	The action’s own nonce
`expires_after`	int64	`expiresAfter`, epoch ms
`action_type`	string	The inner action’s `type` (e.g. `order`, `cancel`, `modify`, `setOracle`)
`action`	string	The full raw inner `action` object as a JSON document. Shape varies by type.
`resp_user`	string	Address the execution response is attributed to
`resp_status`	string	Execution status: `ok` / `err`. NULL if no response was paired.
`resp_response`	string	`res.response` when it is a JSON object (the `ok` path), as a JSON document
`resp_error`	string	`res.response` when it is a bare string — the plain error message on the `err` path

`hypercore.misc_events` (v1.0.0)

Miscellaneous event data.

Column	Type	Description
`id`	string	pk
`block_number`	uint64	Block height
`block_time`	int64	Block time, epoch ms
`event_index`	int	Position in the block’s `misc_events` list
`timestamp`	int64	Event time, epoch ms
`hash`	string	Event hash
`event_type`	string	The event type
`event`	string	The raw `inner` event object as a JSON document

action, resp_response, and event are JSON-encoded strings. Use json_extract or your sink’s JSON functions to parse them downstream.

Turbo

Reference

Hyperliquid HyperCore sources for Turbo pipelines

Overview

Schema Reference

`hypercore.blocks` (v1.0.0)

`hypercore.fills` (v1.0.0)

`hypercore.trades` (v1.0.0)

`hypercore.transactions` (v1.0.0)

`hypercore.misc_events` (v1.0.0)

​Overview

​Schema Reference

​hypercore.blocks (v1.0.0)

​hypercore.fills (v1.0.0)

​hypercore.trades (v1.0.0)

​hypercore.transactions (v1.0.0)

​hypercore.misc_events (v1.0.0)

Overview

Schema Reference

`hypercore.blocks` (v1.0.0)

`hypercore.fills` (v1.0.0)

`hypercore.trades` (v1.0.0)

`hypercore.transactions` (v1.0.0)

`hypercore.misc_events` (v1.0.0)