Hyperliquid review

Hyperliquid is primarily a perpetual-futures and spot venue running on its own layer-1 — “a layer one blockchain (L1) written and optimized from first principles”. The event-contract product is new, narrow, and worth understanding as an extension of that rather than as a prediction market in its own right.

The specification, HIP-4, defines outcome markets as “fully collateralized contracts that settle within a fixed range”, described as a “general-purpose primitive” for prediction markets, settling via a fraction of 1 for a binary yes and 0 for a binary no. The documentation states these are live on mainnet and that “the first market is a recurring binary outcome that settles daily at 06:00 UTC to the BTC mark price”. Multi-outcome markets “will be supported but are not part of the initial mainnet release”.

So the honest description of the scope is one recurring BTC binary, with the machinery for more. Read this page as a review of that machinery, because that is what there is to assess.

This is the part Hyperliquid does better than almost anyone here. Question templates are voted on by validators before any market instantiates them, so the wording is agreed in advance by a distributed set of parties rather than drafted by whoever lists the contract.

And the templates pre-specify the messy cases instead of leaving them to a committee. A sports market “resolves to 0.5 if the Contest Result is a draw, records a no contest or no winner, names an unlisted winner, or is not established by {resolutionDeadline} UTC”. A price market states what happens “If {perp} is delisted before this market settles”. These are the exact situations that produce disputes elsewhere, answered in the contract text before anyone trades it.

The settlement record is also fully public and enumerable with no wallet, through the settled-outcome endpoint. Being able to list every settlement a venue has ever made, without an account, is better than most venues on this site manage.

A single staked deployer key settles a market by submitting a fraction. We searched Hyperliquid’s entire documentation corpus for dispute, challenge, bond, appeal and arbitration and found nothing — there is no window, no bond and no escalation of any kind documented anywhere.

That is not the same as the venues here whose dispute process is weak or vague. It is an absence. Once the deployer submits, the number stands, and the documentation describes no route by which anyone could say otherwise.

The documentation is also behind the product on precisely this question. The only page specifying who settles a deployer-registered market is subtitled “Testnet-only”, while three deployer venues carry live mainnet outcomes. And template settlements must send an empty details field, so newer markets publish a machine-readable fraction with no stated reasoning, where older ones carried one — the audit trail is getting thinner as the product grows, not richer.

No licence, registration, operating entity, jurisdiction, restricted-jurisdiction list, minimum age or identity-verification requirement appears in the documentation we read, and hyperliquid.xyz/terms returned HTTP 403 to our fetcher. So the ordinary questions — who operates this, under what law, and who may use it — are unanswered from primary sources.

We have also not verified whether outcome markets have expanded beyond the single BTC binary since we read the documentation. That is material to how much of this page applies, and it is the first thing we will re-check.