HIP-4 Outcome Markets

Query HIP-4 outcome market metadata, registrations, settlements, and outcome-specific fills from the Dwellir Hyperliquid Index.

HIP-4 adds outcome markets to HyperCore. Dwellir's Hyperliquid Index exposes outcome metadata, lifecycle events, and outcome-side fills through the same REST-style /info and JSON-RPC surfaces used by indexed fills and candles.

Use these methods when you need to discover active outcomes, backfill registration and settlement history, or retrieve fills for outcome instruments such as #30 and #31.

Endpoints

REST-style Info API:

Text

POST https://api-hyperliquid-index.n.dwellir.com/YOUR_API_KEY/info

JSON-RPC:

Text

POST https://api-hyperliquid-index.n.dwellir.com/YOUR_API_KEY/jsonrpc

For /info, set type to the method name. For JSON-RPC, set method to the same value and pass request fields under params.

Outcome Asset IDs

HIP-4 outcome sides are encoded as #<encoding> coins:

Value	Meaning
`outcomeId`	Numeric outcome ID assigned in registration order.
`side`	`yes`, `no`, `0`, or `1`.
`Yes` coin	`#(10 * outcomeId)`.
`No` coin	`#(10 * outcomeId + 1)`.

For outcome ID 3, the Yes side is #30 and the No side is #31.

Methods

Method	Use case
`outcomeMeta`	Current active outcome metadata and `sideSpecs`.
`outcomeFills`	Recent fills for all outcome coins or one outcome side.
`outcomeFillsByTime`	Outcome fills inside a bounded time window.
`registeredOutcomes`	Recent registered outcomes that have not settled yet.
`registeredOutcomesByTime`	Registered outcomes inside a bounded registration-time window.
`registeredOutcomesById`	Registered outcomes by `outcome_ids` or `asset_ids`.
`settledOutcomes`	Recent settled outcomes.
`settledOutcomesByTime`	Settled outcomes inside a bounded settlement-time window.
`settledOutcomesById`	Settled outcomes by `outcome_ids` or `asset_ids`.

Billing

Outcome fill and outcome lifecycle list responses are billed by returned objects through X-Iris-Billing-Weight.

Method family	Billing weight
`outcomeFills`, `outcomeFillsByTime`	Number of returned fill objects.
`registeredOutcomes`, `settledOutcomes`	Number of returned outcome objects.
`outcomeMeta`	Regular single metadata response; no bundled-response billing header.

Empty arrays return billing weight 0. Error responses are not charged.

Pagination

By-time methods page oldest to newest:

Method family	Cursor format	Sort key
`outcomeFillsByTime`	`time_txIndex`	Fill timestamp, then fill `txIndex`.
`registeredOutcomesByTime`	`time_outcomeId`	Registration event time, then outcome ID.
`settledOutcomesByTime`	`time_outcomeId`	Settlement event time, then outcome ID.

When cursor is supplied, the service resumes after the cursor and ignores startTime. Keep the same endTime across pages for a stable window.

Indexing Model

Dwellir derives these endpoints from Hyperliquid L1 data and stores the customer-facing records needed for serving queries:

outcome registration and settlement events
current outcomeMeta snapshots for metadata and sideSpecs
outcome-side fills from the indexed fill stream

You do not need to parse raw replica_cmds to use these HIP-4 query methods. Dwellir indexes the required L1 data and serves outcome market records directly. Use the L1 gRPC Streaming API only when your application needs raw live block payloads.