Outcome Review: Prediction Markets Inside Hyperliquid

Disclosure: CoinCodeCap has no commercial relationship with Outcome and earns nothing from this page. There are no affiliate links here. We publish it because readers keep asking what the Hyperliquid prediction-market venues actually are.

How we reviewed this: every claim below was checked against Outcome’s own documentation and Hyperliquid’s protocol docs on 2 September 2026, not against third-party summaries. Where two of Outcome’s pages disagree, we say so and quote both. We did not fund an account, so nothing here is a report of live fill quality. Figures move; check the source pages before you trade.

That string is a whole prediction market. It says: will Bitcoin be at or above $78,213 at 06:00 UTC, settled daily. Outcome publishes it in its docs as the contract specification format, and understanding it tells you most of what you need to know about the product.

Outcome doesn’t run a matching engine. It doesn’t hold your money. It writes specs like that one, posts a bond against them, and lets Hyperliquid do everything else.

TL;DR: Outcome is a front end and market deployer for HIP-4 outcome contracts on Hyperliquid. Positions are fully collateralised and settle at exactly 1 USDC or 0, so there’s no leverage and nothing to liquidate. Trading fees are Hyperliquid’s own, and Outcome’s builder fee is currently zero. It has posted a 500,000 HYPE bond that validators can slash for a badly written or wrongly settled market, which is a genuinely different quality model from anything its competitors run. The weak spot is resolution: three of Outcome’s own pages describe who settles an event market three different ways. US and some Canadian residents are blocked.

What Outcome actually is, and what it isn’t

Hyperliquid’s HIP-4 standard added outcome markets as a native primitive on HyperCore, the same execution layer that runs its perpetuals and spot books. HIP-4 contracts are fully collateralised binary instruments. They trade between 0 and 1 and settle to 0 or 1 against a real-world event.

Outcome calls itself a HIP-4 deployer venue and a frontend. That’s accurate. Hyperliquid validators vote on templates that fix each market’s display text, side names and typed keywords, and Outcome fills those templates in with concrete values, sets the deployer fee scale that applies to trades on its markets, and settles them onchain.

Your funds never sit with Outcome. If outcome.xyz went dark this afternoon, your positions would still be on Hyperliquid and you could close them through any other interface that supports HIP-4 markets, or straight through the Hyperliquid API. That is a much stronger failure story than most venues in this category can tell, and it’s a direct benefit of building inside an existing on-chain trading stack rather than beside one.

There’s also no separate Outcome account. The wallet you use here is the same Hyperliquid wallet you use on the main app and every other builder on the network, with one unified margin balance across all of it.

How trading works: one dollar, or nothing

Prices move between 0.001 and 99.999 cents while a market is open. A price of 40 cents means the book is collectively calling the event 40% likely. At resolution the token settles to exactly 1 USDC if the event happened, and 0 if it didn’t.

Buy 100 YES tokens at 40 cents and you’ve paid 40 USDC. If the event lands, they’re worth 100 USDC. If it doesn’t, they’re worth nothing. That’s the entire payoff structure, and it’s why Outcome’s docs are able to say there’s no leverage, no liquidation and no margin call.

Outcome’s own risks page is blunt about what that does and doesn’t buy you: “no liquidation is not the same as no risk.” Every position can still settle at zero. What you’re actually getting is a known, capped maximum loss at the moment you open the trade, which is the opposite of the risk profile on the perp DEXs running on the same chain.

The four market types you can trade

Markets split along two axes: how many outcomes are possible, and whether a price reading or a real-world event decides it.

The Price Touch detail is a small thing that tells you the design has been thought about. Because the trigger runs on a one-second average rather than any individual print, a single wick that reverts inside the same second won’t necessarily register a touch. Anyone who has been stopped out by a one-tick spike on a centralised exchange will recognise the problem being solved.

Categories currently span sports, politics, macroeconomics, crypto, traditional finance and culture.

Who decides an event market? The docs give three answers

This is the part of Outcome we’d want cleared up before putting size on an event market.

Three pages in Outcome’s own documentation describe event resolution three different ways, as of 2 September 2026:

Those aren’t necessarily contradictory once you know the full design. A proprietary system could be the thing that feeds a validator vote, and Outcome could be the party that submits the settlement transaction. But a trader reading the docs today can’t tell which, and none of the three pages links to the others to reconcile them.

The gap that matters more is what none of the three pages mentions. There’s no published dispute window, no challenge bond and no appeal path for a resolution you think is wrong. Compare that with Polymarket’s UMA-based optimistic oracle, where anyone can post a bond to dispute a proposed answer and the process runs in the open. Outcome’s docs say resolution is “currently in Beta” and that the target during mainnet rollout is settling real-world events within four hours of official settlement, coming down over time.

Price markets don’t carry this problem. They settle off HyperCore mark prices by linear interpolation between the mark updates either side of the settlement timestamp, which is arithmetic anyone can reproduce.

The 500,000 HYPE bond behind every settlement

HIP-4 deployment requires a stake of 500,000 HYPE. Outcome holds it, publishes its deployer address (0x423d7f725ae7056f03f7ef57f9d0303f91c62e06) so you can check it onchain, and states plainly that validators can slash the stake if a market is poorly defined or settled incorrectly. It can’t be withdrawn until every outstanding market has settled.

Set that against the resolution ambiguity and it reads better than the docs alone suggest. Outcome’s own capital is exposed on every settlement it makes, which is a harder incentive than the one a curated venue operates under, where the downside for a bad resolution is reputational.

It cuts the other way too. A slashing event, or a long-running market that locks the bond, is a live risk to the deployer rather than an abstraction. If you’re sizing a position on an ambiguous question, the bond is a reason to expect care in settlement, not a guarantee of the answer you want.

What it costs

Outcome doesn’t publish a fee schedule of its own. Trades run on Hyperliquid’s protocol-wide rates, which are set by your rolling 14-day volume across every Hyperliquid product.

The unpublished settlement fee is the one to watch. On a contract that pays 1 USDC, a fee taken out of the payout is a direct cut of your edge, and you only see it in the individual market spec. Check it before you size a position rather than after.

One structural note: adding Outcome’s builder code to your Hyperliquid account is mandatory, not optional. It’s a one-time approval at signup that authorises the interface to route your trades. The code’s address is published in the docs and you can verify what’s attached to your account from Hyperliquid’s own settings.

Wallets, deposits and who’s locked out

You can connect a self-custody wallet such as MetaMask or Rabby, or use a social login through Privy that creates a wallet for you and splits the key material so no single system holds all of it. Both are non-custodial. Outcome never holds funds either way.

Settlement is in USDC. Deposits of USDC use Circle’s CCTP, and anything else routes through Across, with the cost shown in the deposit screen before you confirm.

⚠️ Access: Outcome’s risks page states the platform is not available in the United States, certain Canadian provinces, or territories under international sanctions. If you’re in the US, this venue is closed to you and a CFTC-regulated exchange is the lane that’s actually open. Confirm your own jurisdiction before signing anything.

The risks Outcome publishes, and the one it inherits

The risks page is unusually honest for a crypto product. It names total loss, smart-contract and network risk, oracle and settlement risk, liquidity risk, bridge risk through Across, USDC issuer and peg risk, the geographic block, and unsettled tax and securities treatment. Two of those are worth pulling out.

• Liquidity is the one that bites first on a young venue, well before anything exotic. Outcome says spreads “can be wide in less active markets,” and that books may thin further as a market approaches resolution, which is exactly when you’re most likely to want out.
• The only audit named anywhere in the docs is Zellic’s, and it covers the Hyperliquid bridge contract, which is not an audit of Outcome. Because Outcome deploys through Hyperliquid’s own primitive rather than shipping its own contract stack, there may be little bespoke code to audit. The docs don’t say so, and no Outcome-specific report is published.

Then there’s the risk no Outcome page can fix. Building inside HyperCore means settlement depends on Hyperliquid’s mark prices and its validator set, and Hyperliquid has had oracle incidents on thinly traded markets. A price-settled contract is only as good as the feed underneath it. Unified margin and no bridge hop is what you get in exchange.

How Outcome compares

If you want a broader map of the category rather than a single venue, our guide to crypto prediction markets and the Polymarket vs Limitless vs Opinion vs Kalshi comparison cover the alternatives in more depth.

Pros and cons

Expert tip: start on price markets, not event markets. Price contracts settle off a published TWAP formula you can verify yourself, so the only thing you’re betting on is your read of the market. Event contracts add a second bet on top: whether the resolution process reads the world the way you do. Until Outcome publishes the full mechanics and names its resolution partners, that second bet is one you’re taking blind, and it’s worth sizing accordingly.

Bottom line: Outcome takes a different route to on-chain prediction markets than its competitors: it runs them inside an exchange that already works rather than building one alongside. The non-custodial design, the capped downside and the slashable 500,000 HYPE bond are real advantages over a curated venue, and none of them depend on trusting an interface. What holds it back is documentation rather than architecture. Nobody should be putting meaningful size on an event contract while three of the venue’s own pages disagree about who settles it and there’s no published way to dispute an answer. Price markets are the sensible place to start. Keep event positions small until the resolution mechanics are published in full, and read the settlement fee in the market spec before every trade.

Reviewed 2 September 2026 against Outcome’s documentation and Hyperliquid’s protocol docs. Fees, market types and jurisdiction rules change; verify current terms on the venue before trading. Nothing here is financial advice, and prediction-market contracts are treated differently across jurisdictions.

Related reading

Prediction market venues

• Crypto prediction markets (the category map, start here)
• Kalshi review (the CFTC-regulated route for US traders)
• Polymarket alternatives (venues worth comparing before you pick one)
• Overtime review (sports-focused on-chain markets)

Head-to-head comparisons

• Polymarket vs Kalshi (regulated versus permissionless, in detail)
• Polymarket vs Limitless vs Opinion vs Kalshi (four-way on fees and resolution)
• Limitless vs Polymarket vs Myriad vs Opinion (the newer on-chain challengers)

Hyperliquid ecosystem

• Best Hyperliquid alternatives (if you want the perps without the ecosystem lock-in)
• dYdX vs GMX vs Hyperliquid vs Vertex (how the base layer stacks up)
• Hyperliquid RPC providers for HyperEVM and HyperCore (for builders reading the chain directly)
• Perp DEX airdrops worth farming (adjacent incentive programmes)

Tools and data

• Prediction trading terminals (front ends with better order tooling)
• Prediction market APIs (pulling market data programmatically)
• Polymarket analytics tools (position and flow tracking)
• Kreo review (copy trading across Polymarket and Kalshi)

Regulation and the wider fight

• ESMA puts prediction market operators on notice (the EU binary-options position)
• CFTC warns against blanket contract certifications
• Insider trading laws apply to prediction market traders
• a16z backs the CFTC in the federal-state clash
• Wintermute enters prediction markets as a liquidity provider