Hyperliquid co-founder and CEO Jeff Yan has described the network as a base-layer protocol for onchain financial markets, setting out a model in which market creators, rather than the protocol itself, carry much of the responsibility for defining contracts and their pricing rules.
In an Oct. 15 podcast interview, Yan said Hyperliquid’s architecture is designed to provide a trading experience comparable in speed and usability to centralized venues while retaining onchain settlement and self-custody. His comments place the project’s market-listing system, oracle constraints and regulatory boundaries at the center of how the platform operates.
The approach gives approved market deployers substantial latitude to create products, including contracts linked to assets that may trade only during limited hours on conventional venues. At the same time, it requires users to understand who created a market and how that market’s oracle and funding mechanics work before trading it.
Market creation requires HYPE stake and auction slot
A party seeking to deploy a market on Hyperliquid must stake 500,000 HYPE tokens, Yan said. Once that threshold is met, the deployer can establish the oracle framework for the contract, including how prices are sourced and updated.
The protocol allocates deployment opportunities through an onchain Dutch auction that runs every 31 hours. The auction begins at a set price that falls linearly until a bidder accepts it. The opening price for the following auction is then calculated as twice the clearing price of the previous sale.
That mechanism ties access to market creation to demand for deployment slots and to the HYPE token. It also avoids a conventional listing committee that reviews products according to discretionary standards such as expected liquidity, market-maker participation or the perceived quality of an underlying asset.
Yan said Hyperliquid does not embed subjective liquidity checks or similar assessments into the protocol. The network instead applies mechanical restrictions at the oracle level, where reported prices feed into trading and liquidation calculations.
Oracle rule limits single-update price moves
Under the framework Yan described, the relative difference between two consecutive oracle updates cannot exceed 1%. If an oracle attempts to publish a larger change, the protocol clips the update at 1%, leaving the remaining movement to be reflected through later updates.
The rule can slow the impact of abrupt price moves on a contract, particularly where the underlying reference asset is thinly traded or unavailable for periods of time. It also means a market’s displayed oracle price may take multiple updates to reflect a large external move.
That structure could matter most for non-crypto contracts, where traders may expect a product linked to a stock, commodity or other traditional asset to follow a familiar reference price. A 1% update limit does not determine where a market ultimately trades, but it sets the pace at which oracle-based pricing can adjust.
Yan framed the constraint as a protocol-level safeguard that removes routine human judgment from daily market operations. The trade-off is that users must assess the design of each contract themselves, including the party that deploys it and the price process chosen for it.
Funding can connect 24/7 contracts to closed markets
Yan also outlined how perpetual contracts on Hyperliquid could handle assets whose underlying spot markets do not operate around the clock. He argued that funding payments, rather than oracle pricing alone, provide the longer-term force that can bring perpetual prices back toward a reference market.
Funding is the periodic payment exchanged between long and short positions in a perpetual futures contract. When the perpetual market trades above its reference price, funding generally creates a cost for long positions and a payment for short positions; the incentives reverse when the contract trades below the reference level.
In Yan’s example, a contract could track a spot-linked price during traditional market hours and trade more freely while that underlying market is closed. When the reference market reopens, funding payments could encourage convergence over time between the perpetual contract and its spot-linked benchmark.
That design gives markets a way to express price views outside standard trading hours, but it also introduces risk for positions held through a market reopening. A large gap in the underlying reference price can alter funding conditions quickly, while the oracle’s update restrictions can shape how rapidly the protocol’s reported price catches up.
Yan pointed to activity during the Iran war period, when users traded WTI and Brent crude contracts around the clock while conventional trading venues were closed. He said such behavior depended on the choices made by individual market deployers, rather than on a protocol requirement that every listed product remain active continuously.
Validator model targets lower infrastructure demands
Hyperliquid is operated by more than 30 validators, according to Yan, with the top 27 validators by stake running the network. He described the system as maintaining a single global state, meaning participants operate from the same shared record of balances, orders and market activity.
The stated validator hardware requirement includes 128GB of memory. Yan said the target is to avoid requiring specialized data-center infrastructure while maintaining performance suitable for active trading.
The balance between performance and validator accessibility remains a central design question for trading-focused blockchains. Higher hardware requirements can support faster processing and larger order books, but they may narrow the pool of operators capable of running nodes. Hyperliquid’s validator count remains far below that of large general-purpose blockchain networks, placing greater weight on how stake is distributed among the validators securing the system.
Yan, who previously worked at quantitative trading firm Hudson River Trading, said Hyperliquid began in 2023 without venture capital funding. He characterized its development goal as combining centralized-style trading features with onchain custody and reduced dependence on an intermediary holding customer assets.
US derivatives restrictions remain in place
Yan said US-based users who use virtual private networks to access derivatives trading on Hyperliquid would violate the platform’s terms of service. The statement addresses a recurring tension for globally accessible blockchain applications: smart contracts may be reachable online, while interfaces and service providers can impose geographic restrictions.
He argued that regulatory oversight should focus on the party that deploys and controls a particular market rather than the underlying protocol. Yan compared the protocol layer to TCP/IP, the internet’s foundational transport technology, suggesting that neutral infrastructure should be treated differently from the applications built on top of it.
The comparison does not remove the practical consequences for users or market creators. Hyperliquid’s model assigns deployers responsibility for constructing markets and oracle systems, while traders bear the task of evaluating those designs and complying with the platform’s access rules.
Before trading Hyperliquid markets, learn core concepts in crypto derivatives and oracle design to assess contract risks properly.
Disclaimer: The content on this page is provided for general informational purposes only and does not represent the views or financial advice of Toobit. We make no guarantees regarding the accuracy or completeness of this information and shall not be held liable for any errors, omissions, or outcomes resulting from its use. Investing in digital assets involves risk; users should independently evaluate their financial situation and the risks involved. For further details, please consult our Terms of Service and Risk Disclosure.
