HyperEVM’s gas fees have spiked to absurd levels in the past few days—should we move to L2 now?
That’s a good idea, but it’s almost impossible to make it happen. Not because of technical reasons, but because building an L2 goes against HyperEVM’s core philosophy.
At its essence, HyperEVM is not a standalone L1 chain. It’s simply a generalized smart-contract execution layer for Hyperliquid’s L1. HyperCore, on the other hand, is another execution layer focused on high-performance trading. These two execution environments are tightly coupled: they share the same validator set, the same consensus, and a unified state.
Hyperliquid’s official GitBook explains the motivation behind building HyperEVM: developers can write smart contracts on HyperEVM, and then directly tap into the liquidity of HyperCore’s native on-chain order book. In more professional terms, it enables native composability between HyperEVM and HyperCore—no bridges, no oracles, no liquidity fragmentation, and no latency.
If Hyperliquid were to build an L2, it would inevitably sacrifice native composability, leading to liquidity fragmentation and latency issues—and HyperEVM would lose the meaning of its existence.
#Hyperliquid $HYPE
That’s a good idea, but it’s almost impossible to make it happen. Not because of technical reasons, but because building an L2 goes against HyperEVM’s core philosophy.
At its essence, HyperEVM is not a standalone L1 chain. It’s simply a generalized smart-contract execution layer for Hyperliquid’s L1. HyperCore, on the other hand, is another execution layer focused on high-performance trading. These two execution environments are tightly coupled: they share the same validator set, the same consensus, and a unified state.
Hyperliquid’s official GitBook explains the motivation behind building HyperEVM: developers can write smart contracts on HyperEVM, and then directly tap into the liquidity of HyperCore’s native on-chain order book. In more professional terms, it enables native composability between HyperEVM and HyperCore—no bridges, no oracles, no liquidity fragmentation, and no latency.
If Hyperliquid were to build an L2, it would inevitably sacrifice native composability, leading to liquidity fragmentation and latency issues—and HyperEVM would lose the meaning of its existence.
#Hyperliquid $HYPE
