HyperCore is Hyperliquid’s native market engine. HyperEVM is its EVM smart-contract environment. Shared consensus does not make their balances, fees, assets or bot integrations interchangeable.
| Question | HyperCore | HyperEVM |
|---|---|---|
| What executes here? | Native order-book markets: spot and perpetuals | EVM smart contracts, including DEX swaps |
| What balance do I use? | The relevant native trading balance or margin account | The wallet balance on chain 999 |
| What are the costs? | Trading fees; funding for perpetuals; route-specific transfer costs | HYPE gas, venue fees and any bot/platform charge |
| What support must a bot prove? | The named native market integration | HyperEVM token trading and the relevant venue |
| What does a token symbol prove? | Nothing about EVM token contract compatibility | Nothing about the corresponding native asset or deposit route |
What belongs to HyperCore?
Native spot and perpetual order books are handled within HyperCore. Spot and perpetuals are themselves different products: one exchanges assets, while the other creates a margined position. An interface may integrate only one subset. A generic “Hyperliquid integration” should therefore be checked against the actual market and action supported.
What belongs to HyperEVM?
HyperEVM runs EVM contracts and exposes a JSON-RPC interface. Mainnet uses chain ID 999 and HYPE for gas. DEX contracts and launchpad integrations need HyperEVM-specific evidence. HyperEVM contracts can interact with HyperCore through documented mechanisms, but an ordinary token swap should not be described as a native perpetual order.
How we label products
HyperEVM support means the product has explicit evidence for this environment. Hyperliquid platform support identifies a native integration that needs its own feature review. Both means evidence exists for both surfaces; it does not establish identical controls or fees.
Axiom exposes HyperEVM spot trading and documents native perpetuals. MEVX lists the two surfaces separately; its native integration details remain less specific. Our side-by-side tables are restricted to HyperEVM so these differences do not silently distort a ranking.
Common mistakes
- Importing a Solana routing claim into a HyperEVM comparison.
- Applying a spot-bot fee to a native perpetual trade.
- Assuming an exchange supports HyperEVM deposits because it supports HYPE on HyperCore.
- Treating a DEX listing as proof of private execution or MEV protection.
Source: HyperEVM execution reference.
Frequently asked questions
Is HyperEVM a separate Ethereum L2?
The official documentation describes it as part of Hyperliquid execution, inheriting HyperBFT consensus security.
Can I compare a perps-only tool with an EVM swap bot?
You can compare their purposes, but not score them as substitutes for the same execution environment.