All articles
HyperCore vs HyperEVM5 min readReviewed 2026-09-04

HyperCore vs HyperEVM: What Is the Difference?

HyperCore vs HyperEVM explained: where perps and spot live, where smart contracts run, and how assets move between the two.

Direct answer

HyperCore is Hyperliquid's native trading layer, where perps, spot markets, and the order book live. HyperEVM is an EVM-compatible environment on the same chain where smart contracts and DeFi apps run. Assets move between them through a documented transfer path using a system address, so a balance on one side is not automatically available on the other.

Updated 2026-10-043 sourcesAffiliate action disclosed in the site header

In short

  1. 1HyperCore holds the native order book for perps and spot.
  2. 2HyperEVM runs smart contracts and lending, DEX, and vault apps.
  3. 3Funds must be transferred between the two; they are separate balances.
Risk notice
Crypto perpetuals and leveraged trading are high risk. You can lose money through liquidation, funding, slippage, oracle issues, protocol failures, and market volatility.

What is HyperCore?

HyperCore is the native layer behind the trading product: the order book, margin, funding, liquidations, and native vaults. Most of the fee and funding mechanics discussed on this site refer to HyperCore.

What is HyperEVM?

HyperEVM lets developers deploy Solidity contracts on the Hyperliquid chain. Lending markets, DEXs, and other apps run here, separate from the native order book. Current vault architecture on HyperEVM differs from legacy HyperCore vaults.

How do assets move between them?

Transfers use a documented path involving a system address. The balance of that address reflects transfer mechanics and is not one holder, so avoid reading it as a whale position. Check the official transfer instructions before sending anything.

Why does the split matter?

Margin on HyperCore does not automatically count on HyperEVM, and a contract risk on HyperEVM does not touch HyperCore positions. Know which layer holds your funds before you act.

Example: where is my balance?

Say you hold USDC for trading in your HyperCore account and want to lend on a HyperEVM app. The app cannot use your trading margin directly; you must transfer funds across, and the balance becomes unavailable for margin until you move it back.

If you forget which side holds the funds, a margin call or an app transaction may fail. Estimate your needs on each side before transferring.

Common mistakes

Confirm which layer holds your funds before any action.

  • Assuming balances are shared automatically.
  • Reading the system address balance as a single large holder.
  • Sending funds without checking the official transfer steps.

Practical next steps

Before moving funds between layers, read the official transfer instructions, send a small test amount, and confirm it arrives on the right side. Keep a note of which balances sit where so you never assume trading margin is available to an app, or the reverse. If you use HyperEVM apps, read each protocol's own documentation and risks, because they are separate from HyperCore's trading engine. The ecosystem page on this site lists sources for several HyperEVM protocols with their documentation links. If something looks wrong after a transfer, check both balances before repeating it, because a second transfer will not fix a first one that is simply still pending. Keep a short note of each protocol you use.

Sources

3 references · Expand
  • Hyperliquid Docs: HyperEVMAccessed 2026-08-20
    Supports: The EVM-compatible smart-contract environment on the Hyperliquid chain and its relationship to HyperCore.
  • Supports: The HYPE system address, its role in transfers between HyperCore and HyperEVM, and the limits of interpreting its balance as one holder.
  • Hyperliquid Docs: VaultsAccessed 2026-08-26
    Supports: Current HyperEVM vault architecture and the distinction from legacy HyperCore vaults.

Keep reading

Related Hyperliquid questions