The HyperEVM is live. This is a major step toward the vision of housing all finance by bringing general-purpose programmability to Hyperliquid’s performant financial system. The initial mainnet release of the HyperEVM includes:
1. HyperEVM blocks built as part of L1 execution, inheriting all security from HyperBFT consensus.
2. Spot transfers between native spot HYPE and HyperEVM HYPE. As a reminder, HYPE is the native gas token on the HyperEVM.
3. A canonical WHYPE system contract deployed at 0x555...5 for defi applications. The source code can be found at hyperliquid.gitbook.io/hyperliquid-do…
Effective immediately, the bug bounty program will pay mainnet bounty amounts for reports within the scope of the points above. See hyperliquid.gitbook.io/hyperliquid-do… for details.
For API and wallet users: the mainnet HyperEVM has chain ID 999. A JSON-RPC server for the mainnet HyperEVM is hosted at rpc.hyperliquid.xyz/evm. Node operators and other builders are encouraged to host their own RPC servers.
Tooling and analytics around mainnet HyperEVM may not be polished on day one. However, there are many talented builders working to solve these developer pain points. To help with these efforts, raw HyperEVM block data is streamed realtime to S3 so that running a node is not required to index the HyperEVM. More technical details can be found here: hyperliquid.gitbook.io/hyperliquid-do…
General ERC20 native transfers and precompiles will be enabled on a future network upgrade. Any ongoing feedback for these features on testnet is greatly appreciated. While these features are implemented on testnet, the mainnet releases are staggered for minimal disruption to existing users on the L1. The HyperEVM is composable with the L1 state while not affecting the low latency trading experience of existing users.
Thank you to all the builders and users who have shared feedback on testnet so far. It will be exciting to see new applications leveraging and building upon the existing onchain financial system of Hyperliquid.
1. HyperEVM blocks built as part of L1 execution, inheriting all security from HyperBFT consensus.
2. Spot transfers between native spot HYPE and HyperEVM HYPE. As a reminder, HYPE is the native gas token on the HyperEVM.
3. A canonical WHYPE system contract deployed at 0x555...5 for defi applications. The source code can be found at hyperliquid.gitbook.io/hyperliquid-do…
Effective immediately, the bug bounty program will pay mainnet bounty amounts for reports within the scope of the points above. See hyperliquid.gitbook.io/hyperliquid-do… for details.
For API and wallet users: the mainnet HyperEVM has chain ID 999. A JSON-RPC server for the mainnet HyperEVM is hosted at rpc.hyperliquid.xyz/evm. Node operators and other builders are encouraged to host their own RPC servers.
Tooling and analytics around mainnet HyperEVM may not be polished on day one. However, there are many talented builders working to solve these developer pain points. To help with these efforts, raw HyperEVM block data is streamed realtime to S3 so that running a node is not required to index the HyperEVM. More technical details can be found here: hyperliquid.gitbook.io/hyperliquid-do…
General ERC20 native transfers and precompiles will be enabled on a future network upgrade. Any ongoing feedback for these features on testnet is greatly appreciated. While these features are implemented on testnet, the mainnet releases are staggered for minimal disruption to existing users on the L1. The HyperEVM is composable with the L1 state while not affecting the low latency trading experience of existing users.
Thank you to all the builders and users who have shared feedback on testnet so far. It will be exciting to see new applications leveraging and building upon the existing onchain financial system of Hyperliquid.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
