How Spot, Perps, DeFi, and Applications Fit Into One Hyperliquid Stack
Hyperliquid combines native financial markets in HyperCore with a programmable HyperEVM application layer, allowing capital and information to move between trading and DeFi surfaces.
Hyperliquid is easier to understand as a stack than as a list of products. HyperCore provides native spot and perpetual markets, risk, and liquidity. HyperEVM adds smart-contract applications such as lending, AMMs, vaults, and structured products. APIs serve offchain trading and analytics, while precompiles, CoreWriter, and transfer mechanisms connect applications back to native market state.
Layer 1: consensus
HyperBFT orders state transitions and secures the chain. Both HyperCore and HyperEVM rely on that consensus layer.
Layer 2: native markets
HyperCore contains the native exchange state. Spot assets, perpetual markets, order books, margin, funding, liquidations, staking, vaults, and protocol asset metadata live here.
This is the layer a trader touches when placing a native order.
Layer 3: programmable finance
HyperEVM lets protocols build contracts around the native financial layer. A money market can lend assets, a liquid staking protocol can create a composable representation of staked HYPE, and a vault can package a strategy.
The application can read supported HyperCore state and, where allowed, trigger native actions through protocol interfaces.
Layer 4: applications and data
Frontends, wallets, trading terminals, market makers, bots, analytics tools, and institutional systems generally sit outside the chain and communicate through APIs, WebSockets, RPC endpoints, and signing infrastructure.
This layer can be highly competitive even when multiple products use the same native liquidity underneath.
Why the stack matters
The architecture creates composability in two directions. HyperCore offers deep native financial primitives that applications can build around. HyperEVM lets applications create new credit, staking, routing, and structured-product layers that can send activity back toward HyperCore.
The risks also stack. A user may simultaneously face protocol risk, a HyperEVM contract's smart-contract risk, oracle risk, liquidity risk, and wallet or API-key risk. Understanding which layer performs each action is the first step toward separating those risks.