Most roadmaps are wish lists with dates attached. The Hyperliquid roadmap stands out because several major developments have already launched. That's why traders and builders keep asking what comes next.
Hyperliquid is a layer 1 blockchain built around on-chain trading. Its plans now center on three ideas: more markets, more builders, and a wider validator set.
This guide walks through the Hyperliquid roadmap, covering what's live, what's still planned, and where the docs go. Facts here come from the official Hyperliquid documentation, reviewed on 18 October 2026. Plans are labelled as plans.
Start with the record. Before looking ahead, it helps to see what the team has actually shipped.
Milestone | Timing | What it did |
Points program | Nov 2023 | Rewarded early users |
HYPE token launch | Nov 2024 | Put the native token live |
Staking | Dec 2024 | Let holders delegate to validators |
HyperEVM mainnet | Feb 2025 | Added smart contracts |
HIP-3 | Oct 2025 | Opened perp listings to builders |
HIP-4 | May 2026 | Added outcome markets |
The official docs say the Hyperliquid Points Program began on 1 November 2023 and ran in two phases, ending in November 2024.
Notice the pattern. Each step widened who can take part. Early users came first. Then token holders, then developers, then market creators.
HIP-3 changed who gets to list a market. HIP stands for Hyperliquid Improvement Proposal, which is a formal protocol upgrade. This one lets builders deploy their own perpetual futures. Those are contracts that track an asset's price with no expiry date.
Deployers carry real responsibility. Per the HIP-3 documentation, they define the oracle and contract specs, set leverage limits, and run the market day-to-day.
To do that, a deployer must stake 500,000 HYPE. The docs say this requirement should fall as the infrastructure matures. The stake stays locked for at least 183 days after deployment.
And it can be cut. Validators can slash up to 100% of it for irregular inputs that cause invalid state changes or long downtime. The docs call slashing unlikely on the mainnet. That's the project's view, not a guarantee.
Several Hyperliquid ecosystem projects now run on this framework, which is why the Hyperliquid roadmap leans on it so heavily.
HIP-4 is the newest layer. It adds outcome markets, which are fully collateralized contracts that settle inside a fixed range. Think of a yes-or-no question that pays out once the answer is known.
The docs on HIP-4 outcome markets say these contracts involve no leverage and no liquidations. That's a sharp contrast with perps.
The first market is a recurring binary outcome. It settles daily at 06:00 UTC against the BTC mark price on HyperCore. Fees are currently zero, which the docs describe as initial testing.
Multi-outcome markets are supported by design but weren't part of the initial mainnet release. The docs say more features will roll out in stages.
There's also a builder question. The developer docs label HIP-4 deployer actions as testnet-only. That suggests outside teams can't yet deploy their own outcome markets on mainnet. It's an interpretation, not a confirmed date.
If HIP-3 is the template, open deployment could be the logical next step. For the Hyperliquid roadmap, that's the biggest open item. The docs don't promise it, so treat it as a possibility.
HyperCore runs the order books. HyperEVM runs smart contracts, which are programs that execute automatically on-chain.
The docs say HyperEVM isn't a separate chain. The same HyperBFT consensus secures both, so apps can talk directly to spot and perp order books. A lending app, for example, could read prices from HyperCore and send liquidation orders there. No bridge sits in between.
The docs also describe HyperEVM as being in alpha, with a gradual rollout. That page says higher throughput and write system contracts weren't live when it was written.
Earlier roadmap notes listed a write contract, CoreWriter, as shipped in July 2025. Docs pages don't always update in step, so check the announcements feed before trusting either version.
Speed means little if only a few operators control the chain. That's why decentralization sits near the top of the Hyperliquid roadmap.
Running validating and non-validating nodes is permissionless, says the validator documentation. The active set is the top 27 by stake.
Earlier roadmap notes called full decentralization a multi-phase goal. They also listed open-sourcing node code and running multiple software clients as planned items. Client diversity matters because one bug can hit every validator if they all run the same software.
The docs reviewed don't confirm either item as finished. That's a gap worth watching. Centralized venues face none of this.
They answer to a company, not a validator set. It's one reason people compare Hyperliquid vs Binance Futures so often.
Plans slip. And the official risk page is blunt about why.
Newer chain: Hyperliquid runs its own layer one, which hasn't faced the same scrutiny as older networks like Ethereum.
Oracles: Price data comes from oracles that validators maintain.
Slippage: Thin liquidity can cause large price slippage.
Open interest caps: Restrictions apply based on liquidity, basis and leverage.
Deployer quality: HIP-3 markets depend on how carefully deployers pick oracles and specs.
Leverage adds another layer, and the guide to Hyperliquid leverage trading risks shows how fast losses build.
Market talk about options and other new products circulates too. None of it appears on the official pages reviewed, so it's unverified.
Skip the screenshots and start at the source.
Official docs: The HIP pages show current specs.
App announcements: Hyperliquid posts upgrade notices in its app.
Developer pages: Labels like "testnet-only" reveal what hasn't reached mainnet.
Check the date on every page. Older roadmap material may list items as planned that have since shipped.
The Hyperliquid roadmap reads less like a calendar and more like a direction. Widen what trades on HyperCore, widen who can list it, and widen who can validate it.
HIP-3 and HIP-4 are the proof so far. HyperEVM is the bridge for developers. The open questions sit at the edges: outcome-market deployment, node code and client diversity.
Next, check the HIP pages for status changes, watch the announcements feed, and confirm any claim against the docs before acting on it.
Disclaimer: This article is for information only and isn't financial advice. Crypto, perpetual futures and outcome contracts carry high risk, including total loss. Roadmap items are plans and may change, so research independently before acting.