Hyperliquid Architecture · Ecosystem & Tokens · 8/8
Architecture Knowledge Check
Test your understanding of Hyperliquid's architecture. You need 70% to pass.
1. What consensus mechanism does Hyperliquid use?
Hyperliquid uses HyperBFT, a custom consensus algorithm inspired by HotStuff and optimized for low end-to-end latency with one-block finality.
2. Where does the order book and matching engine run?
The order books and matching engine are part of HyperCore, the native L1 execution state, and run inside consensus on every validator — not on HyperEVM and not on an off-chain server. HyperEVM contracts can interact with the books through precompiles and CoreWriter.
3. What is the relationship between the native L1 and HyperEVM?
HyperEVM is not a separate chain: it is secured by the same HyperBFT consensus and validator set as HyperCore, but provides a separate EVM-compatible execution environment.
4. How are funding rates calculated on Hyperliquid?
Funding is based on the premium of the perp's impact prices over the spot oracle price, plus a small fixed interest component, and is paid every hour. Positive funding means longs pay shorts, which pushes the perp toward spot.
5. What happens when a position falls below the maintenance margin?
When account value falls below maintenance margin, the liquidation engine sends market orders to the order book to close the position. If that fails and equity drops below 2/3 of maintenance margin, the liquidator vault (part of HLP) takes over the position as a backstop.