# Hyperliquid Canonical Outcome Markets - Validator-Deployed Prediction Markets on Offchain Events > Hyperliquid validators now deploy and settle canonical outcome markets on offchain events via automated newsfeed software, opening prediction markets on sports, politics, and news natively on HyperCore. *Source: https://hyperliquidguide.com/ecosystem/hyperliquid-canonical-outcome-markets* ## Canonical Outcome Markets Are Live on Hyperliquid Hyperliquid now supports **canonical outcome markets based on offchain events**. The markets are published by automated newsfeed software that validators run as part of their regular chain operations. Validators vote on deployment and settlement of each market based on a variety of factors — including unambiguous rules, correctness of the reference data, and the subjective quality of the proposed market. This expands what prediction markets on Hyperliquid can cover. The [HIP-4 outcome primitive](/ecosystem/hip-4-outcome-trading) shipped on May 2, 2026 with a recurring binary BTC market that settles to the on-protocol mark price, so it carried no oracle dependency — and correspondingly could only settle questions Hyperliquid already produces data for. Canonical markets lift that constraint by routing offchain resolution through validator consensus. Corporate news is the obvious category to follow sports and scheduled economic releases. A validator newsfeed that can settle "did this company announce that, before this date" answers a question no price feed answers on its own. The effect is largest on smaller listed names, where one headline can matter more to the chart than the quarter's numbers do. That group includes [the BB perpetual market on Hyperliquid](/markets/xyz/bb), and a trader with a view on a specific announcement would rather price the announcement than the drift around it. Event markets also sit naturally alongside the equity perps already listed through trade.xyz. A trader holding [Oracle (ORCL) on Hyperliquid](/markets/xyz/orcl) into an earnings date, or [the SpaceX perpetual on Hyperliquid](/markets/xyz/spcx) into a launch window, can now express the event itself in the same wallet instead of approximating it with a directional position. Sector contracts work the same way. Someone following [the DRAM market page](/markets/xyz/dram) through a memory pricing cycle could pair that perp with an event question about one specific supply announcement. > **Key takeaway:** Canonical outcome markets are HIP-4 contracts that validators themselves deploy and settle, via automated newsfeed software run as part of normal block production. Sports, elections, news, scheduled economic releases — anything with unambiguous resolution criteria — can now resolve directly through validator voting, with no external oracle or separate dispute mechanism required. ![Hyperliquid Outcomes page with All, Crypto, Economics, and Sports category tabs above live daily binary markets on BTC, HYPE, ETH, and SOL](/images/ecosystem/shared/hyperliquid-outcomes-page.webp) *The Outcomes tab on **[app.hyperliquid.xyz](https://app.hyperliquid.xyz/join/Concept211)**. The Economics and Sports category tabs alongside Crypto are where canonical event markets surface, since those are the contracts that resolve through validator consensus rather than an onchain price feed.* --- ## What "Canonical" Means The word *canonical* is doing real work here. Hyperliquid distinguishes between markets that are deployed by individual actors and markets that are deployed by the protocol itself: - **HIP-1 spot markets** are deployed via [Dutch auction](/ecosystem/hyperliquid-auctions-explained) — a single deployer wins a slot and lists the asset. - **[HIP-3 builder-operated perps](/ecosystem/hip-3-builder-codes)** are deployed by builders who pay an auction fee for a deployer slot and run their own market parameters. - **HIP-4 canonical outcome markets** are deployed by the validator set itself. No auction, no individual deployer, no concentrated counterparty. When something is canonical on Hyperliquid, it means the validators have collectively voted to deploy and settle it. The market carries the full credibility of the validator set rather than the reputation of a single team. That distinction matters most for prediction markets, where settlement integrity is the entire product — a binary contract is only as good as the process that resolves it. --- ## The Validator Newsfeed The mechanism that makes canonical markets possible is a piece of **automated newsfeed software that validators run as part of regular chain operations**. This is not a separate off-protocol service or a third-party oracle bolted on after the fact — it is part of the validator client itself. ### What the newsfeed does The newsfeed watches for real-world events that meet the criteria for an outcome market: - **Scheduled events with clear resolution timing** — game finals, election dates, central bank meetings, scheduled economic data releases - **Unambiguous resolution rules** — "team A wins the championship" rather than "team A has the best season" - **Verifiable reference data** — results that come from public, agreed-upon sources When the newsfeed identifies a candidate market, it proposes the contract to the validator set: the underlying event, the resolution rules, the expiration time, the reference source. Validators then vote on whether to deploy. After the event resolves in the real world, the newsfeed surfaces the result back to the validator set, which votes again on the settlement value. The same software that proposed the market now drives its resolution. ### Why this is different from an oracle Traditional oracle designs — Chainlink, UMA, Pyth — sit between the chain and the outside world as a separate trust layer. Reporters submit data, disputes happen in a separate venue, and the chain treats the oracle's output as input to settle markets. The Hyperliquid approach collapses that into a single layer. The validators **are** the oracle, because settling a canonical market is just another vote that happens during normal block production. There is no separate set of reporters, no separate dispute application, no escalation game. The chain reaches consensus on the outcome the same way it reaches consensus on every other state transition. > **Note:** Validators are economically aligned through HYPE staking, and canonical settlement runs through the same validator set that secures the chain. Note that this site does not assert what specific penalty attaches to a bad settlement: Hyperliquid does not implement automatic slashing for validator misbehavior (see the [staking guide](/ecosystem/hype-staking-yields-guide)), so the deterrent here is delegation and reputational rather than an automatic protocol penalty. Check the current validator documentation for what is actually enforced. --- ## How Validators Vote Validators vote on canonical markets at two stages: deployment and settlement. The criteria are stated explicitly by the protocol team — markets must clear a bar on each axis to pass. ### Deployment vote criteria When the newsfeed proposes a new market, validators evaluate three dimensions: 1. **Unambiguous rules.** The resolution criteria must be specific enough that there is no realistic post-hoc dispute. A market on "whether the Fed cuts rates at the June meeting" is fine because the resolution is binary and publicly announced. A market on "whether the economy will improve" is not — there is no agreed-upon definition. 2. **Correctness.** The proposed reference data has to be verifiable and accurate. If the newsfeed surfaces a game time and a result source, validators check that the time is right, the source is authoritative, and the resolution mapping is correct. 3. **Subjective quality.** This is the most interesting criterion. Validators consider whether the market is genuinely useful and well-formed — reasonable expiration timing, not trivially manipulable, not too niche to attract liquidity, not a duplicate of something already trading. Validators can vote against a technically valid market simply because they do not think it deserves a slot. A market only goes live if it passes the deployment vote on all three. ### Settlement vote criteria After the event resolves, the newsfeed surfaces the result, and validators vote again. The settlement vote is mostly a check on correctness — did the event resolve as proposed, was the reference data observed accurately, and does the settlement value map cleanly to the contract's outcome buckets. Edge cases (cancelled events, postponed games, ambiguous results) are surfaced for the validator set rather than handled by hardcoded rules. --- ## Why This Unlocks Event-Driven Trading Until canonical markets shipped, HIP-4 on Hyperliquid was a powerful primitive without a way to express most of what people actually want to trade. The recurring binary BTC market and the [multi-outcome BTC range market](/ecosystem/hyperliquid-multi-outcome-markets) are clean test cases, but they both settle to data the protocol already produces — which excludes nearly every interesting prediction market. Canonical markets fix this in one move. The same primitive that already supports daily-settling [BTC, ETH, HYPE, and SOL outcome contracts](/ecosystem/hip-4-outcome-trading) can now support: - **Sports outcomes** — game results, tournament winners, season totals - **Election markets** — primary results, general election outcomes, vote shares - **Macro events** — Fed rate decisions, CPI releases, GDP prints - **Scheduled news events** — earnings surprises, IPO pricing, regulatory decisions - **Crypto-specific milestones** — protocol launch dates, governance vote outcomes, network upgrades Settlement criteria are where this gets hard, and earnings show why. "Did the company beat expectations" is ambiguous, because consensus figures differ by data provider. "Did reported revenue exceed a stated figure" is not. Validators vote on the quality of a proposed rule as well as on the reference data behind it, so the markets that clear that filter will be the ones written against a single published number. For a chip name carrying several scheduled catalysts a year, [AMD perpetual futures on Hyperliquid](/markets/xyz/amd) being the obvious example around product launches and quarterly reports, the gap between those two phrasings decides whether a market settles cleanly or ends in argument. The mechanics are unchanged. Markets are still 100% collateralized with no leverage. They still use the [15-minute opening call auction](/ecosystem/hip-4-outcome-trading) for price discovery. Split, negate, and merge still work for multi-outcome variants. The only thing different is where the settlement value comes from — and that is the entire reason this category of market has been impossible on Hyperliquid until now. **Trade Outcome Markets on Hyperliquid** — Get a 4% lifetime fee discount when you sign up with our referral link. [Start Trading](https://app.hyperliquid.xyz/join/Concept211) --- ## Comparison: Hyperliquid vs. Polymarket vs. Kalshi Canonical markets put Hyperliquid in direct competition with the two largest prediction market venues. The mechanisms are very different. The key structural advantage Hyperliquid has is **cross-margin composability**. A trader on Polymarket or Kalshi holds an isolated position — capital posted to a binary market is locked there and earns nothing else. A trader on Hyperliquid can offset a canonical outcome position against negatively correlated perp or spot exposure inside the same account, because all of it sits on HyperCore. That is genuinely impossible on a standalone prediction market venue. Our [Hyperliquid vs Polymarket comparison](/compare/hyperliquid-vs-polymarket) breaks down this and every other difference — fees, market creation, and liquidity — in detail. The key structural advantage Kalshi has is **US regulatory access** — it is a CFTC-regulated designated contract market and serves US residents directly. Hyperliquid does not, and canonical outcome markets do not change that. Whether that gap narrows is an open regulatory question rather than a product one: see [Is Hyperliquid coming to the US?](/privacy/is-hyperliquid-coming-to-the-us) for the CFTC process and what has actually been announced. --- ## Where AQAv2 Fits The [AQAv2 spec announced May 14, 2026](/ecosystem/aqav2-usdc-aligned-quote-asset) named canonical outcome markets as one of the venues migrating to USDC settlement, and that migration has now shipped. The relevant section of the AQAv2 design treats HIP-4 canonical markets and validator-operated perp markets together — both are protocol-blessed venues, and both use the AQAv2-aligned quote asset. What this means in practice: - **Today**: Canonical markets settle in USDC. Coinbase is the treasury deployer, Circle is the technical deployer, and the AQA rate is shared with the protocol via Coinbase's HYPE stake. - **The USDH sunset is complete**: Markets originally settled in [USDH](/ecosystem/usdh-stablecoin-guide), but all USDH-denominated markets on HyperCore have finished settlement. If you still hold USDH, swap it to USDC — feeless via Across on HyperEVM, or on the HyperCore spot order book. The mechanics described in this article — validator newsfeed, deployment vote, settlement vote, opening call auction — apply identically to USDC-denominated markets. The only thing that changed is the quote asset. --- ## What This Means for HYPE Stakers Canonical outcome markets are settled by the validator set, and validators are economically anchored by [HYPE staking](/ecosystem/what-is-hype-token). Three implications worth flagging: 1. **Validator responsibility grows.** Resolving canonical markets is now part of the job. Validators that vote poorly — approving ambiguous markets, missing settlement disputes, mis-mapping reference data — damage the protocol's most reputation-sensitive product. The same staking economics that secure block production now secure prediction market integrity. 2. **Delegators choose carefully.** When you delegate HYPE to a validator, you are implicitly signing off on their newsfeed operation and voting record. Over time, the canonical-markets track record becomes a meaningful factor in delegate selection, alongside uptime and fee policy. 3. **New revenue surface for the protocol.** Canonical market volume generates trading fees and quote-asset yield (via AQAv2) that flow into the protocol's existing revenue model. Analyst estimates of prediction-market addressable market — $1.5–3M monthly from event contracts, plus large adjacent options markets — represent meaningful upside if even a fraction of Polymarket/Kalshi volume migrates. **Stake HYPE and Help Settle Canonical Markets** — Delegate HYPE to a Hyperliquid validator and earn rewards while securing the chain — and the canonical markets it now runs. [Get Started](https://app.hyperliquid.xyz/join/Concept211) --- ## What to Watch Next Three things to track as canonical markets scale out from here: - **First non-financial canonical market.** The launch primitives all settled to onchain price data. The first canonical market that settles on a non-financial event — a sports result, an election, a scheduled news release — is the real proof that the validator newsfeed works under live conditions. - **Validator disagreement rate.** If most settlements pass unanimously, the system is working as intended. If disputes start clustering on specific event types or specific validators, that signals where the mechanism needs refinement. - **Builder front-end activity.** Canonical markets are the validator-blessed default, but the surface is open — builders can wrap canonical markets in branded interfaces. Expect more front-ends to ship as canonical event markets go live. - **The shift to permissionless deployment.** In July 2026, Hyperliquid published preliminary specs for **[HIP-4 permissionless deployment](/ecosystem/hip-4-permissionless-deployment)** — a 500k HYPE stake plus validator-voted templates that let anyone deploy their own outcome markets. Once it ships, validator-deployed canonical markets are expected to become rare, "ideally fewer than 10 outcomes or questions per year," with the long tail of markets flowing through permissionless deployers instead. - **Fees arriving on canonical markets.** Validator-deployed outcome markets, canonical ones included, trade with no fee at all today. Hyperliquid said on August 14, 2026 that the next network upgrade turns fees on, explicitly as preparation for the deployer fee scale that permissionless markets will carry. The stated target is an **average outcome fee of half ordinary spot trading**, and the charge lands on closes and settlements rather than on opening a position. That upgrade is the clearest signal that permissionless deployment is close, since a deployer's fee share needs a fee to exist first. Sports templates are also now live on testnet, which partly answers the first bullet from a different direction: the `sportsContestResult` and `policyRateDecision` template families let a permissionless deployer launch fixtures and central bank decisions without a validator vote per market. Canonical deployment and template-based deployment are converging on the same event categories from opposite ends. The validator newsfeed is the most architecturally novel piece Hyperliquid has shipped in months. It is the difference between HIP-4 being a clean primitive without obvious users and HIP-4 being a direct, scaled competitor to Polymarket and Kalshi on a venue that already does more daily perp volume than most of crypto combined. **Start Trading on Hyperliquid** — 4% lifetime fee discount, full HIP-4 outcome market access, cross-margin with perps and spot. [Open Account](https://app.hyperliquid.xyz/join/Concept211)