What is HyperEVM, and how is it different from HyperCore?
Hyperliquid gets described as "an exchange" and "a blockchain" in the same breath, and both descriptions are correct — which is exactly what confuses people. It is one chain running two execution surfaces, and which surface an asset lives on decides how you trade it, what you actually hold, and what can go wrong.
BT365 is integrated against both sides — perps, spot and HIP-4 outcome markets on HyperCore, and token swaps plus a token launchpad on HyperEVM — so this is the distinction as it looks from having built against each, not from a diagram.
One chain, two surfaces
HyperCore is the exchange. Perpetual futures, spot pairs and HIP-4 outcome markets all trade on central limit order books that the chain itself operates. Your position lives in an exchange account. When you buy, nothing is minted to a wallet — the venue's ledger changes. Settlement, margining and liquidation are all things the venue does to your account.
HyperEVM is a general-purpose EVM on the same chain. Chain ID 999, standard Ethereum tooling, permissionless contract deployment. Assets here are ERC-20 tokens sitting in your own wallet, and trading means calling a smart contract that swaps against a liquidity pool — the same model as Ethereum mainnet or Base, secured by Hyperliquid's consensus rather than its own validator set.
The practical consequence: "trading on Hyperliquid" is ambiguous until you say which side. A HYPE/USDC order on HyperCore's spot book and a HYPE swap through a HyperEVM DEX pool are different mechanisms with different custody, different pricing and different failure modes, even though both are "buying HYPE on Hyperliquid."
Where the two sides actually differ
What you hold. On HyperCore, a balance in an exchange account, settled by the venue. On HyperEVM, tokens in a wallet you control. This is the same custody split as centralized exchange versus DEX — except here both options run on one chain, and moving between them doesn't mean bridging to a different network.
How price is made. HyperCore prices come from an order book: bids, asks, and whoever crosses the spread. HyperEVM prices come from pool reserves — the constant-product or concentrated-liquidity math of whatever DEX holds the liquidity. Order books give tight pricing on liquid pairs; pools give guaranteed executability on anything with a pool, including tokens that listed five minutes ago and will never see an order book.
What can list. HyperCore listings are venue decisions. HyperEVM listings are permissionless — anyone who deploys a token and seeds a pool has a tradable market. That is why new tokens appear on the EVM side first, and why token launchpads on Hyperliquid are HyperEVM contracts, not exchange listings.
HYPE and WHYPE
HYPE is the asset that exists on both sides, and it picks up a third form in the process.
On HyperEVM, HYPE is the native gas asset — it pays for transactions the way ETH does on Ethereum. Native assets are not ERC-20 tokens, and DEX pool contracts need an ERC-20 on both sides of a pair. So HyperEVM has WHYPE, canonical wrapped HYPE, at a memorable address: 0x5555555555555555555555555555555555555555. Pools quote against WHYPE; wrapping converts one-to-one in both directions.
Whether you ever touch WHYPE yourself depends on the contract you trade through. BT365's HyperEVM swaps route through our own helper contract, which accepts and returns native HYPE and does the wrapping and unwrapping internally — routing and pricing run against WHYPE while the user only ever sees HYPE. A raw DEX interaction without such a wrapper leaves the wrap step to you, which is where "I bought HYPE but my wallet shows a token I don't recognize" comes from. The token is WHYPE, and it is worth exactly one HYPE.
Why the split matters when something goes wrong
The two surfaces fail differently, and knowing which side you're on tells you which failures apply.
On HyperCore, the venue can act on your market: an outcome market can be delisted before it resolves, and positions share an account with everything else you trade there — the unified margin trade-off. On HyperEVM, the venue cannot touch your tokens, but contract-level risks replace venue-level ones: a pool's liquidity can be withdrawn by whoever owns the LP position (unless it is locked), a quote can go stale between signing and execution, and a swap with no minimum-output protection can be sandwiched. Every swap BT365 executes on HyperEVM is bound to a signed quote with an explicit minimum output and a deadline, because on a permissionless surface the contract call is the only place those protections can live.
Neither side is the safe one. They are different machines, and the useful question is never "is Hyperliquid safe?" but "which surface is this asset on, and what does that surface let happen?"
BT365 trades both sides of Hyperliquid — perps, spot and outcome markets on HyperCore, swaps and token launches on HyperEVM — from one self-custodial account. Explore the platform or read the documentation.