Hyperliquid HIP-4: Outcome Markets, Settlement, and Risk

Hyperliquid HIP-4 looks simple until a 62-cent contract settles at zero. The framework adds bounded outcome markets to Hyperliquid, with separate tokens for the possible sides of a defined event or price condition. Before placing an order, read the exact contract description, expiry, settlement source, spread, and current fee preview. A correct hunch can still become a poor trade.

What HIP-4 changes

Perpetual futures have a continuously moving profit and loss figure. They use margin, funding, and liquidation rules. An outcome contract has a bounded result tied to a condition and a time boundary.

That difference changes the whole reading process.

Hyperliquid's official asset ID documentation says each outcome side has its own token representation. The API derives that representation from an outcome ID and a binary side. In the current encoding, side 0 and side 1 become separate assets that can be quoted and traded.

The official outcomeMeta response exposes fields including the outcome name, a machine-readable description, and sideSpecs. Its example describes a price-binary market with an underlying asset, an expiry, a target price, and a period.

That metadata is the contract. The colorful market title is packaging.

1. 01

   Read

   Identify the event, measurement source, cutoff time, fallback language, and every possible side.

2. 02

   Price

   Compare the best bid and ask with your own probability estimate. Use executable prices rather than the midpoint.

3. 03

   Size

   Walk the book for your full order. A small top quote can hide expensive slippage underneath.

4. 04

   Settle

   Follow the stated resolution process and keep a record of the exact rules you traded.

How the payoff works

Suppose a Yes contract trades at 0.62 and pays 1.00 if the stated condition resolves Yes. Spending $124 buys 200 shares before fees and spread.

If Yes wins, the gross redemption is $200. The gross trading profit is $76. If No wins, the 200 shares settle at zero and the $124 purchase is lost.

The arithmetic feels clean. Execution makes it messier.

Now change the executable price from 0.62 to 0.68 because the ask is thin. The same 200 shares cost $136; upside falls to $64. Your view did not change. The trade did.

I find cents easier to audit than percentages here. Write 62 cents paid, 100 cents possible on a scratch line before looking at the chart again. That tiny habit exposes trades whose expected payout never covered the entry price.

Binary, multi-outcome, and price-bucket markets

The API model supports more than one presentation.

Binary outcomes give you two sides. A price condition might ask whether BTC finishes above a stated threshold at a specified timestamp.

Labelled binary markets can replace generic Yes and No labels with named sides. Read the underlying condition anyway. Two friendly labels can conceal an awkward fallback.

Multi-outcome questions group several possible results. Capital accounting gets trickier because linked outcomes should be considered together. A complete set may sum toward one unit at settlement, while individual books can trade with different spreads.

Price buckets divide a range into several bands. Boundary language deserves a slow read. “Above 100,000” and “at or above 100,000” resolve differently when the observed value is exactly 100,000.

The official docs currently give developers enough metadata to identify the sides, but they are terse for ordinary traders. Keep the description visible while comparing prices (a screenshot with the timestamp is useful, even if it sits in a boring folder you never expect to open).

Settlement deserves its own risk budget

A market needs an authority or deterministic input that converts an unresolved question into a final result. Price-based contracts may reference a defined mark or index. Event markets may depend on an official publication, validator process, or another named source.

Inspect five things before buying.

• Exact source. A government release, exchange mark, oracle, newswire, or validator vote can produce different answers during revisions and outages.
• The timestamp, including timezone. “End of day” is weak language unless the market defines the day.
• Rounding. A value published as 3.0% might come from an unrounded 2.96%. The contract should say which figure counts.
• Postponement language. Weather, sports, governance votes, and data releases all move.
• A fallback path for missing or disputed data. Silence here adds real risk.

An outcome token can reach the right economic conclusion and still lose under the written rule. Read the rule you are trading rather than the story in your head.

Rollout status needs live verification

There is a documentation mismatch as of August 24, 2026.

Hyperliquid's official Info endpoint page labels the outcomeMeta request testnet-only. Its asset-ID page was updated more recently and documents outcomes without the same prominent qualifier. Meanwhile, several current ecosystem guides report mainnet activity and expanded market types.

So this article will not pretend the rollout boundary is settled in prose. Open the official Hyperliquid interface from a trusted bookmark, check the current network indicator, and inspect the order preview. If the feature is absent, the article is educational until the official interface and documentation agree.

The official developer pages document outcome encodings and metadata, but the Spot API page still includes a testnet-only label. Current independent guides describe a broader launch. That disagreement is why every time-sensitive statement here is dated and why we avoid linking to an unfamiliar trading frontend.

Fees, spread, and the cost nobody puts in the headline

Public HIP-4 explainers currently disagree about fees. Some describe zero-fee opening trades. Others describe charges during closing or settlement, and several map the product to a spot-style schedule.

Use the live preview.

Before signing, record the amount paid, estimated amount received, explicit fee, and minimum output. Repeat the quote at your intended size. If the preview does not show the economics clearly, stop there.

Spread can cost more than the posted fee. A 0.57 bid and 0.63 ask create a six-cent gap. Buying at 0.63 and immediately selling at 0.57 loses roughly 9.5% of the purchase amount before any explicit charge.

The midpoint, 0.60, was never available to either side.

Market orders deserve particular care. On a thin book, the first few shares may fill near the displayed ask while the rest climb through several price levels. A limit order caps the entry price, though it can remain unfilled or fill only in part.

HIP-4 compared with perpetual futures

Lower mechanical complexity does not make the trade gentle. Paying 90 cents for a claim that returns one dollar leaves 10 cents of gross upside and 90 cents of downside. The payout is bounded while the asymmetry can still be severe.

If you also trade perps, review Hyperliquid fees and the crypto trading calculator. Those pages cover costs that outcome contracts handle differently.

How to evaluate liquidity

Start with the full book. Look beyond the last traded price.

For a $500 order, add the shares available at each ask until the order is covered. Divide total dollars spent by total shares to find the volume-weighted average entry. Compare that figure with the headline price.

Then test the exit. A position can show a mark near your entry while the bid side has little depth. Settlement may be the only practical route out, which changes a short-term opinion into a locked event exposure.

Watch for these patterns.

• One tiny order sets an attractive top-of-book price.
• Wide silence. Several cents separate bids and asks, with almost no resting size.
• Related outcome prices fail to add up sensibly after spread.
• A market becomes active around news and empties immediately afterward.
• The book is deep for $50 and ugly for $5,000.

Avoid treating reported volume as available liquidity. Volume describes completed trades. Depth describes what you can execute now.

Common failure modes

You read the headline and skipped the description

A phrase such as “BTC above $100K Friday” can omit the exchange, index, timestamp, timezone, equality rule, and fallback. Any one of those can decide settlement.

You bought after the information moved

Outcome prices can jump faster than a page refresh. Recheck the live ask before signing. A stale 55-cent idea filled at 74 cents is a different position.

You used the midpoint in your expected-value calculation

Use the ask for entry and the bid for an immediate exit. Midpoints are helpful chart references; they do not promise a fill.

You confused bounded loss with small loss

A position can lose 100% of the capital committed to that outcome. Set the dollar allocation before you open the trading page. Moving the size upward because the result “feels obvious” is still leverage of conviction, even without borrowed funds.

You followed a third-party frontend from social media

HIP-4's growing attention invites lookalike sites. Start from Hyperliquid's official documentation or a saved official domain. Never type a seed phrase, and review token permissions with a token approval checker after interacting with an unfamiliar app.

HIP-4 pre-trade checklist

1. Copy the complete market definition

   Save the description, possible outcomes, settlement source, expiry, timezone, boundary wording, and fallback. A market title alone is insufficient.

2. Confirm the official network and interface

   Reach the venue from a trusted bookmark. Check whether you are on mainnet or testnet and verify that the feature appears in the official product.

3. Calculate the payout in dollars

   Divide capital by the executable entry price to estimate shares. Subtract capital and every displayed charge from the possible redemption.

4. Walk the order book at full size

   Calculate an average fill using all relevant levels. Repeat the exercise on the bid side to understand an early exit.

5. Set a fixed loss amount

   Assume the position can settle at zero. Use an amount that does not disturb bills, emergency savings, taxes, or other commitments.

6. Review the final wallet request

   Confirm domain, network, asset, amount, minimum received, and approval scope. Reject blind signatures you cannot interpret.

Three things to keep visible

• The complete contract description, preferably beside the order ticket.
• Your executable average entry rather than a chart midpoint.
• A calendar reminder before expiry so you can review liquidity and settlement updates.

Hyperliquid HIP-4 FAQ

›What is Hyperliquid HIP-4?

HIP-4 is Hyperliquid's framework for outcome contracts. Each possible side is represented separately, and the contract resolves according to a defined event, price condition, or result.

›Can a HIP-4 position be liquidated?

A fully collateralized outcome position does not use the conventional margin-liquidation process of a leveraged perpetual. The amount spent can still fall to zero at settlement, and product rules can change, so verify the live contract.

›Does a 70-cent price mean a 70% chance?

It is often read as a market-implied 70% value on a one-dollar payout. That interpretation depends on liquidity, spreads, information quality, fees, and trustworthy settlement. It is a price rather than a verified probability.

›Are HIP-4 trades free?

Current public descriptions conflict on when fees apply. Check the live order preview for opening, closing, builder, and settlement charges. Spread and price impact can exceed the displayed fee.

›Is HIP-4 available on mainnet?

Several current ecosystem sources report mainnet activity, while Hyperliquid's official Info endpoint documentation still labels outcomeMeta as testnet-only as of August 24, 2026. Confirm availability through the official interface before funding a trade.

Sources

• Hyperliquid asset IDs for the official outcome-side encoding.
• Hyperliquid Info endpoint for outcomeMeta, descriptions, and sideSpecs.
• Hyperliquid fees documentation for the venue's current spot and perpetual fee schedules.
• Hyperliquid liquidations documentation for the mechanics that distinguish leveraged perpetuals from bounded outcome positions.