Hyperliquid Wiki Protocol & Ecosystem Knowledge Base
🔍

Gas Economics, Free Cancellations & Mark Price Oracles

Hyperliquid's Layer-1 introduces a custom economic model that eliminates toxic gas bidding wars, provides zero-gas limit order cancellations, and computes high-frequency mark price feeds via sub-second consensus oracle medianizers.

1. The Problem with Standard EVM Gas for Trading

In traditional blockchain environments like Ethereum or standard rollup L2s, every state write incurs variable gas fees denominated in volatile native assets (official docs). For automated market makers (AMMs) and quantitative trading firms, this creates critical vulnerabilities:

  • Gas Spikes on Volatility: When market prices move sharply, network congestion increases gas fees by 10x–100x. Market makers cannot update bids or cancel stale quotes without paying exorbitant fees.
  • Stale Quote Exploitation (Sniping): Latency arbitrageurs front-run market maker cancellations in public mempools, leading to adverse selection and wider bid-ask spreads.
  • Failed Cancellations: Out-of-gas errors during market turbulence can lead to catastrophic losses for liquidity providers.
💡
Hyperliquid's Zero-Gas Cancellation Paradigm: Hyperliquid treats order cancellations as first-class, gas-free protocol primitives. Cancelling an order or updating a quote incurs zero gas fees (open trading terminal), ensuring market makers can continuously provide tight liquidity across all market conditions.

2. Dynamic Priority Fees & Spam Mitigation

To prevent malicious actors from spamming the validator network with millions of useless orders without cost, Hyperliquid utilizes an adaptive rate-limiting and priority fee mechanism based on account fill-to-cancel ratios and nonces:

🛡️ Hyperliquid Priority & Rate Limiting Engine
[User Order Stream] ──► [Fill-to-Cancel Ratio Check] ──► [Deterministic Priority Queue]
                               │                                      │
                   High Fill Ratio: FREE                     Sub-second Execution
                   Excessive Spam: Rate Throttled           Zero Toxic MEV Front-running

Accounts maintaining a healthy fill ratio receive prioritized order matching without paying gas surcharges. If an account continuously submits non-filling orders at abnormal frequencies, the protocol applies temporary micro-throttling without impacting honest traders.

3. Native Oracle Architecture & Mark Price Calculation

Perpetual contracts require accurate, manipulation-resistant spot price feeds to calculate unrealized PnL, trigger liquidations, and enforce hourly funding rates. Hyperliquid bypasses external third-party oracle delay (such as Chainlink 1-minute heartbeats) by integrating a native validator-driven oracle consensus engine.

Mark Price Medianizer Formula

The protocol computes the Mark Price ($P_{ ext{mark}}$) for every asset in every sub-second block using a robust median of multiple independent feeds:

P_mark = Median(P_index, P_oracle_1, P_oracle_2, P_median_30s) + Exponential_Moving_Basis
Oracle Component Source Description Update Frequency Weight / Protection
Index Price ($P_{ ext{index}}$) Volume-weighted average price (VWAP) across tier-1 external spot exchanges (Binance, OKX, Coinbase, Bybit, Kraken). Every Block (~200ms) Outliers > 1.5% trimmed automatically.
Validator Oracles Direct cryptographic signed price feeds submitted by active PoS consensus validators. Continuous UDP Stream Stake-weighted median calculation.
Local Impact Mid The median of best bid and ask on the native Hyperliquid L1 order book, bounded by order depth. Microsecond Execution Prevents local order book manipulation from skewing mark price.

4. Comparison with Other DEX Oracle Implementations

Feature Hyperliquid L1 dYdX v4 (Cosmos) GMX (Arbitrum)
Oracle Latency < 300 ms (Native L1) ~1.0 – 2.0 s ~1.0 – 3.0 s (Chainlink Data Streams)
Cancellation Fee 0 Gas (Free) Gas required N/A (AMM position-based)
Flash Loan Resistance Deterministic Block Median Oracle Median Keeper Execution Delay

🔗 Official External References & Primary Sources

To verify facts, technical formulas, and architectural parameters presented in this chapter, consult the following primary sources: