The round

The line from HyperCore

The keeper reads the round from HyperCore's public info endpoint. These are the exact requests and fields.

The outcome

POST https://api.hyperliquid.xyz/info
{"type": "outcomeMeta"}

{ "outcome": 20745, "name": "Recurring",
  "description": "class:priceBinary|underlying:BTC|expiry:20261031-0600|targetPrice:78521|period:1d",
  "sideSpecs": [{"name": "Yes"}, {"name": "No"}], "quoteToken": "USDC" }

The round is the outcome named Recurring whose description has class:priceBinary, underlying:BTC and period:1d. expiry gives the round id (its date) and targetPrice the line. HyperCore guarantees at most one recurring series per type, underlying and period.

How the description maps onto a round.

The live Yes price

Outcome sides trade like spot tokens. For outcome o, the Yes side is coin #<10·o> and the No side #<10·o + 1>; the asset id for orders is 100000000 + 10·o. The site reads {"type":"allMids"} and takes the mid of #207450 for outcome 20745.

HyperCore's settlement rule

HyperCore settles Yes if and only if the BTC mark price, linearly interpolated between the mark updates just before and just after 06:00 UTC, is at or above the target. LiquidRise does not compute this; it reads HyperCore's result.