HyperEVM Consensus, Fee Burning, and Network Access
Summary
The document describes HyperEVM as an EVM environment whose blocks are included in Hyperliquid execution and inherit security from HyperBFT consensus. HYPE is used for gas, and the document explains that it can be transferred from HyperCore to HyperEVM through a designated address. EVM interaction is through JSON-RPC; there are no official frontend components, and the documented RPC does not support websocket JSON-RPC.
The network uses the Cancun hardfork without blobs and supports EIP-1559. Both base fees and priority fees are burned, with priority fees sent to the zero address balance. The document lists separate mainnet and testnet chain identifiers and endpoints, notes that HYPE has 18 decimals on both, and cautions against wallets that have previously sent pre-EIP-155 transactions. It also describes error code 10055 for boundary issues such as nonce or funds errors. This is technical network documentation rather than a trading method; it provides no market analysis, performance evidence, or investment guidance.
Key ideas
- HyperEVM blocks inherit security from HyperBFT consensus and use HYPE for gas.
- EVM access is provided through JSON-RPC, and the documented RPC endpoint lacks websocket support.
- The network uses Cancun without blobs and enables EIP-1559 fee handling.
- Both base fees and priority fees are burned on HyperEVM.
- Mainnet and testnet have distinct chain identifiers and RPC endpoints, and HYPE uses 18 decimals on both.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.