How to use the HyperEVM
Last updated
Last updated
You can add the HyperEVM to your wallet extension by using Chainlist (https://chainlist.org/chain/999) or following these steps:
In your wallet extension, click “Add Custom Network” and enter the information below:
Chain ID: 999
Network Name: Hyperliquid
RPC URL: https://rpc.hyperliquid.xyz/evm
Block explorer URL (optional):
(other explorers coming soon — many thanks to the community members building these)
Currency Symbol: HYPE
You can send HYPE to the HyperEVM from your Spot balances and vice versa by clicking the “Transfer to EVM” button on the Balances table for HYPE on https://app.hyperliquid.xyz/trade.
You can also send your HYPE to 0x2222222222222222222222222222222222222222 from either your Spot balances or from the EVM to transfer.
Sending from the HyperEVM to your Spot balances costs gas in HYPE.
Various teams are building applications, tooling, etc. on the HyperEVM. There are many community initiatives to track new releases on the HyperEVM, including:
https://www.hypurr.co/ecosystem-projects, https://hyperliquid.wiki/, https://data.asxn.xyz/dashboard/hyperliquid-ecosystem, and the #hyperevm-eco channel in https://discord.gg/hyperliquid
Hyperliquid is one state with HyperCore state (e.g., perps, spot, order books, other trading features) and HyperEVM state. Because everything is secured by the same HyperBFT consensus, there will ultimately be seamless integration between the two. You can build an application on the HyperEVM involving lending, trading, yield generation, etc. That application can directly access the liquidity on the order books, so that defi has CEX-like functionality for the first time. The application token can also list on native Hyperliquid trading permissionlessly, so that trading happens on the same chain as building.
While the Hyperliquid native blockchain is one of the most performant, high throughput blockchains today, the HyperEVM was intentionally launched with lower initial throughput. Because HyperCore and the HyperEVM share the same state, it is technically risky to allow the HyperEVM to consume more bandwidth on initial launch. The HyperEVM throughput will be increased over time in a gradual technical rollout.
Gas spikes on any chain when there is more demand than supply of blockspace. The HyperEVM uses the same gas system as Ethereum and many L2s, where there is a base fee and a priority fee: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1559.md
First confirm with the CEX that they support the HyperEVM. Note that the HyperEVM is one part of the Hyperliquid blockchain. The native components (e.g., perps, spot, and other trading features) and the HyperEVM are separate parts of the same blockchain. Some CEXs support sending and receiving HYPE on the spot native component, but not the HyperEVM. Always remember to do a test transaction when you are trying something for the first time.
Any application from other chains can already be built with the limited launch. The HyperEVM is a fully functional EVM of its own. The current interaction between HyperCore and the HyperEVM is restricted to transferring HYPE as the gas token on the EVM to and from the spot token on HyperCore. Other features live on testnet will gradually roll out to mainnet, including precompiles and other token transfers.
There is one rpc hosted at rpc.hyperliquid.xyz/evm
Other builders are launching their own as well. Users may run a node, but it is not a requirement to serve an RPC, as all data is uploaded real-time to S3. See python SDK for an example: https://github.com/hyperliquid-dex/hyperliquid-python-sdk/blob/master/examples/evm_block_indexer.py
Cancun without blobs
Functionality is largely the same, which makes it easy to build similar tooling and applications. The main differences are:
Dual block system: fast small blocks and slow big blocks
Interactions with the native side of the Hyperliquid state, providing a seamless onboarding for all Hyperliquid users to the HyperEVM
This can be done through LayerZero or other cross-chain protocols that have launched on the HyperEVM.