Hyperliquid’s Next Tradeable Surface Is Already on Testnet

The detail that made the change click: outcomes use the same spot-like asset machinery, but settle as fully collateralized, dated contracts. That puts Hyperliquid trading on a path beyond perpetuals without bolting on a separate venue.

HIP-4 is now live on testnet. The first implementation is deliberately narrow: recurring binary markets tied to HyperCore mark prices. No leverage. No liquidations. Each contract settles within a fixed range, so the payoff is nonlinear while the collateral requirement stays explicit.

The initial mainnet plan is one-day binary markets on BTC and HYPE. Multi-outcome markets are supported by the design but are not part of the first release. That sequencing matters. The hard problem is not displaying “yes” and “no.” It is creating, pricing, and settling markets without leaving ambiguous edge cases for the matching engine or the oracle layer.

What changed in Hyperliquid

Until recently, the important expansion story was HIP-3: permissionless builder-deployed perpetuals. A deployer can define the market, operate its oracle, set leverage limits, and manage settlement. The mainnet staking requirement is 500,000 HYPE, and each deployer gets an independent perp DEX with its own margining and order books.

That already changed who can list an instrument. HIP-4 changes what an instrument can be.

The practical difference is duration and payoff. A perpetual has no expiry and continuously transfers funding between traders. An outcome market has a fixed resolution window and a binary result. That makes it suitable for event-style exposure, short-horizon price ranges, and structured products that do not map neatly onto a leveraged perp.

There is also a quieter operational change. Cross margin is now available for HIP-3 DEXs on mainnet, but deployers must enable it asset by asset. It works with unified accounts and portfolio margin, not DEX abstraction. That turns account mode into a trading constraint, not a settings detail.

For an automated trader, the first check is therefore not the chart. It is the account configuration. Unified account is the useful default when spot, validator-operated perps, and eligible HIP-3 positions need shared collateral. Standard abstraction remains the better fit for systems that care about higher rate limits. DEX abstraction is on the way out.

What this opens up

For builders, the opportunity is a single settlement environment for more than one market shape: spot assets, perpetuals, outcome contracts, and eventually applications on HyperEVM. The same on-chain state can feed interfaces, risk systems, portfolio tools, and custom execution logic.

For traders, the useful question is not whether HIP-4 sounds like prediction markets. It is whether the contract specification is clear enough to trade mechanically. Before touching a testnet market, inspect the outcome ID, side encoding, settlement window, mark-price source, and collateral rules. Outcome assets use a distinct encoding: the outcome ID is multiplied by ten and the binary side is added to it. Side 0 and side 1 are the only valid values.

That small implementation detail is the tell. Hyperliquid is treating outcomes as protocol-native instruments, not as a frontend wrapper around an external oracle. If testing holds, the next competitive layer will be market design: who creates useful contracts, how they seed liquidity, and how interfaces expose the risk without hiding the mechanics.

The platform is still testing the edges. That is exactly where the opportunity is. The next serious integrations will be built by operators who read the asset model first and the marketing second.