The Hyperliquid ecosystem is two environments with different jobs: HyperCore book apps versus HyperEVM apps. Native perps, spot, builder-code frontends, and HLP sit on the book. General-purpose contracts pay HYPE as gas on chain ID 999. Those surfaces share one chain, and they keep separate balances and separate frontends.
Suppose you rest a BTC bid, then call a lending contract. The bid is a HyperCore action on the native book, billed as a trading fee, while the lending call burns HYPE on HyperEVM. Same identity, two environments. That split is the ecosystem.
The book can look like a hosted venue while the contracts can look like Ethereum, and both still sit on one HyperBFT list.
What the Hyperliquid ecosystem contains
A Hyperliquid app is whichever environment ran the click you just made. HyperCore is the onchain order-book environment. HyperEVM is the general-purpose contract environment on the same chain. A rest on the native book is a HyperCore action. A Solidity call is a HyperEVM action that needs HYPE as gas on chain ID 999. A chain ID is the integer a wallet uses to tell networks apart.
What Hyperliquid is covers HyperCore and HyperEVM as two execution halves. How Hyperliquid is put together is the wiring. The ecosystem question is which surface you are on.
Official onboarding states the shared-state fact in one line: Hyperliquid is one state with HyperCore state (perps, spot, order books, and other trading features) and HyperEVM state. The same page tells you to confirm with a centralized exchange that it supports HyperEVM, because some venues accept HYPE from HyperCore spot and refuse the EVM half. Wallet add-network copy on that page sets chain ID at 999 (source: Hyperliquid Docs, How to use the HyperEVM). Independent wallet coverage restates the same jobs without turning them into a protocol list: "Move between trading (HyperCore) and apps (HyperEVM) without constantly hopping chains" (source: OneKey, New to Hyperliquid in 2026).
| Job | Environment | What you pay |
|---|---|---|
| Rest a BTC bid | HyperCore book | Trading fee. No HYPE as gas. |
| Call a lending contract | HyperEVM | HYPE gas on chain ID 999. |
| Deposit into HLP | HyperCore vault | 4-day lockup. |
| Trade BloFin HYPEUSDT | BloFin CEX | Exchange custody. |
The cheap test is the bill and the balance, not the logo. If the UI looks like a CEX ladder and the fill skips HYPE as gas, you are on the book. If a wallet extension is talking to chain ID 999, you are on HyperEVM. A generic order-book primer still helps if bids and asks are new. Which Hyperliquid environment that ladder sits in is a later test.
The About page is the project's own pitch for why those jobs sit together. It says the HyperEVM brings the familiar general-purpose smart contract platform pioneered by Ethereum to the Hyperliquid blockchain (source: Hyperliquid Docs, About Hyperliquid). That is a claim about tooling familiarity. It is a claim the project makes about its own design. It is silent on whether Hyperliquid is an Ethereum rollup, and it is silent on a ranked dapp catalog.
Same chain, two jobs, and every later product only makes sense once that split is named.
HyperCore book apps: native markets and builder frontends
HyperCore book apps are products whose matching, margin, and fills live on the native onchain books. Native perps and spot are the default. Builder-code frontends, HIP-3 builder markets, and HLP remain book-side jobs: fills and vault shares on that book, even when the UI looks like a Solidity app.
The HyperCore overview puts both halves in one state sentence first. The Hyperliquid state consists of HyperCore and the general purpose HyperEVM. HyperCore includes margin and matching engine state (source: Hyperliquid Docs, HyperCore overview). Matching internals, cancel sort, and book-first liquidation sit in how HyperCore works. The job test is enough: if the thing that moved is a fill on that book, it is a book app.
Builder-code frontends look like apps because a phone or a terminal sent the order. They still settle as HyperCore fills. Builder codes let a DeFi team receive a fee on fills they send on behalf of a user (source: Hyperliquid Docs, Builder codes). Builder here means a DeFi team that routes flow, the same sense the docs use for application teams. Fee caps, the 100 USDC builder balance, and the ten-approval ceiling belong in how builder codes work. The ecosystem fact is location: that fee sits on a HyperCore fill. It is billed beside the trading fee, in the quote or collateral asset. It is separate from HyperEVM gas.
An approval is per builder address. A second terminal you install this week is covered only if it sends fills as that same builder. A new phone UI can be a different builder address, a HyperEVM frontend, or a look-alike. Read which address is requesting the fee.
HLP is the other book-side product people file under apps. Hyperliquidity Provider (HLP) is a protocol vault that provides liquidity through multiple market making strategies, performs liquidations, supplies USDC in Earn, and accrues a portion of trading fees. The deposit lockup period is 4 days, so you can withdraw 4 days after your most recent deposit (source: Hyperliquid Docs, Protocol vaults). That 4-day lockup is a HyperCore vault rule. An ERC-20 share you transfer on chain ID 999 is a different product. Depositor mechanics sit in HLP and vaults. HIP-3 builder-deployed perps inherit the same book as native markets, behind a deployer stake, which is a listing requirement on that book.
Suppose you want a BTC rest and an HLP deposit in the same sitting. Both are HyperCore. Neither one is the lending call you will make later. If you treat HLP as the DeFi app, you will look for a MetaMask network when the product is a vault on the book. Native HIP-1 spot names can later link to an ERC-20, and until that link exists the spot book is still the spot book.
A CEX-looking ladder on Hyperliquid is still a book app, a terminal that charges a builder fee is still a book app, and HLP is still a book app.
HyperEVM apps: contracts, gas, and chain ID 999
HyperEVM apps are general-purpose contracts on the same chain that pay HYPE as gas. Wallets add them as chain ID 999. JSON-RPC is the HTTP API those wallets speak when they send the calls. Community directories point at apps. A protocol ranking is a different job.
Developer docs are plain about the missing shop window. "Note that there are currently no official frontend components of the EVM." Users can build their own frontends or port over existing EVM applications. All interaction with the EVM happens through the JSON-RPC. Mainnet chain ID is 999 (source: Hyperliquid Docs, HyperEVM for developers). Independent add-network indexes list that same id under HyperEVM, which is how you confirm the wallet is on this ledger instead of Ethereum mainnet 1 (source: ChainList, HyperEVM chain 999). Wallet work for this half looks like any other EVM add-network flow. A HyperCore trade screen is a different flow.
Official holder docs send readers to community trackers and skip a first-party app store. They tell you to explore directories of apps, tools, and more built by community members. The same page still calls HyperEVM alpha, as a claim the project makes about its own rollout. It also gives the composition example a holder actually needs. A project XYZ could deploy an ERC-20 contract on the HyperEVM using standard EVM tooling and deploy a corresponding spot asset XYZ permissionlessly in the HyperCore spot auction. Once linked, users can use that token on HyperEVM applications and trade it on the native spot book (source: Hyperliquid Docs, HyperEVM). That is one token in two environments.
A generic primer on Ethereum dapps still helps if contract apps are new, and how Ethereum smart contracts work is the account-and-map version of the same job. HyperEVM reuses that tooling. Hyperliquid stays its own chain.
Dual-block internals, precompiles, and CoreWriter encoding sit in how the HyperEVM works. The holder fact is narrower. The primary motivation behind the dual-block architecture is to decouple block speed and block size when allocating throughput improvements (source: Hyperliquid Docs, Dual-block architecture). Fast small blocks and slower large blocks stay HyperEVM traffic rules.
You add 999 so a lending UI can see your HyperEVM HYPE. That add leaves your HyperCore BTC bid off MetaMask. Gas still has to sit on the EVM half. A directory that names fifteen protocols is a community map, so keep the environment test.
If the gas tank and the chain ID are in play, you are in the contract half.
How a token can sit on both environments
Composition is a linked token, with two balances, two bills, and two failure modes. A HyperEVM ERC-20 can pair with a HyperCore spot name. A lending contract can read a book price. You still hold two environments. You do not hold one merged app that is both the book and the contract.
Suppose you hold 200 HYPE on HyperCore spot and want 50 as HyperEVM gas plus the rest as a bid on a linked XYZ spot market. The 50 has to move to the EVM half before the contract will see it. The bid still rests on HyperCore. If XYZ is still unlinked, the ERC-20 and the spot name are two unconnected tokens that happen to share letters. The link is the product. Shared letters without a link are still two names. Official docs call two improvements versus a CEX listing: the process is permissionless, and HyperCore and HyperEVM are one unified state, so that hop is a system transfer on one chain. That last clause is the project's own account of unified state. It is silent on whether you can still send the wrong asset to the HYPE system address.
The link lets users hold the contract token in HyperEVM apps and trade the same name on the native spot book. BTC perp collateral and a merged margin bucket stay separate questions. Shared letters, before the link exists, are still two names.
There is a live tension in the docs. The holder HyperEVM page still says higher throughput and write system contracts are not live on mainnet yet. The vaults page describes HyperEVM vaults in the present tense as CoreWriter plus precompiles, and it calls legacy HyperCore vaults a 2023 design that omits HIP-3 and spot (source: Hyperliquid Docs, Vaults). Leave those as two published pages. Encoding, delay, and which write paths are actually live belong in the HyperEVM guide.
A contract that can read the book is still a contract. A fill that stayed off chain ID 999 is still a book fill. Shared state still leaves you with two balances.
Official ecosystem categories
Official 101 copy lists borrowing, lending, compliant stablecoins, and any-asset perps as ecosystem categories. Treat that list as the project's own self-report: a category map, with live dollar figures on that page left to move.
The 101 page is the project's own wider map. It says the ecosystem extends beyond trading, supporting borrowing, lending, minting compliant stablecoins, and launching perpetual contracts on any asset. Independent teams, it says, monetize through builder codes on mobile apps, terminals, and self-custodial wallets (source: Hyperliquid 101). That sentence names categories.
Aligned quote assets are a later cut: issuers share yield with the protocol under a separate spec, which belongs in aligned quote assets. HIP-3's 500,000 HYPE listing requirement is a deployer stake that is expected to decrease. It is a listing bond for the party that deploys the market.
You can read "lending" on the 101 page on Monday, then open a directory tile that uses the same word on Tuesday. Monday was a category. Tuesday is a specific contract or a specific book frontend. The 101 sentence leaves that choice open.
Treat 101 as a category list. Treat a ranking as someone else's scorecard. Treat the 500,000 figure as a deployer stake the spec says should fall over time.
BloFin listings, HYPER, and community directories
Three look-alikes sit next to the ecosystem. A BloFin HYPE listing, a HYPERUSDT (Hyperlane) listing, and a community directory that ranks protocols. Confusing any of them with a HyperCore book app or a HyperEVM contract is how you use the wrong product.
The public SWAP book on August 20, 2026 still lists the JSON instrument ID HYPE-USDT at 75x, listed December 19, 2024 11:30 UTC, and a separate HYPER-USDT at 50x, listed April 22, 2025 13:15 UTC. Reader copy for those perps is HYPEUSDT and HYPERUSDT. Those hyphenated keys are copied from that response (source: BloFin instruments API, SWAP). A fill on either row is BloFin custody, a CEX account line. Hyperliquid remains a competing venue, and BloFin is the CEX route that quotes HYPE here. HYPE price history is the listing-date record. Centralized versus decentralized exchange shapes is the generic fork. The extra cut here is only this: an exchange listing is a CEX product.
HYPERUSDT is Hyperlane on that same venue, a second ticker with similar letters. If the header says Hyperlane, you are outside this ecosystem.
Community directories are the third mix. Official docs name HypurrCo, ASXN, and HL Eco as places to track HyperEVM releases. The docs present those names as community directories. A CEX that lists HYPE may still refuse HyperEVM sends even when it takes HyperCore spot. BloFin's live listing is exchange custody, off either Hyperliquid environment. Securing a crypto account still applies on every one of those surfaces, because the wrong product is a loss path even when the logo looks familiar.
BloFin is a CEX route that quotes HYPE, HYPER is Hyperlane, and a directory is a community map.
How to pick an app by job
Name the job first, then the environment, then the product that can actually fail. Start with what you want done. Two environments will not collapse into one app because a landing page used the same logo.
If you want a BTC rest, a native spot fill, or a builder-code terminal fill, you are on the HyperCore book, and the extra fee if any still sits on the fill, billed beside the trading fee. HLP yield is a HyperCore vault with a 4-day lockup. A Solidity lender or vault UI is HyperEVM, which means chain ID 999 and HYPE gas. If you only want HYPE price without the native environments, you are on BloFin as a CEX listing: HYPEUSDT, with HYPERUSDT left as the Hyperlane row. That list is a description of jobs. Terms that still blur, including HyperBFT, HIP, and assistance fund, sit as pointers in the Hyperliquid glossary. You already have the bill, the chain ID, and the lockup. Who shipped the chain is a different question from which environment an app sits in, and that cut lives in who created Hyperliquid.
One afternoon can run three products across two environments without a ranked app list. Rest 0.1 BTC on HyperCore, skip HLP if you do not want a 4-day lockup, add chain ID 999, and only then call a lender with 50 HYPE of gas. If a site then shows you fifteen protocol tiles, you can open a community tracker. Treat that grid as a map someone else drew. Confirm a venue supports HyperEVM before you send HyperEVM HYPE to an address that only listed HyperCore spot.
Hyperliquid's ecosystem is a book plus a contract environment that share consensus: builder frontends, HLP, and HIP-3 stay on the book, EVM apps live on 999, and BloFin quotes HYPE without becoming either surface. Pick the job, then pick the environment.
Frequently asked questions
If JSON-RPC is the only official EVM path, can I skip adding chain ID 999 because I already trade on the book?
No. Book trading does not use that RPC as the fill path. JSON-RPC is how wallets and community frontends talk to HyperEVM contracts that burn HYPE as gas. A HyperCore rest still sits on the native books, and adding 999 is still the add-network step for the contract half. You can trade BTC all morning without that RPC and still be unable to sign a lending call until the wallet is actually on 999.
Can I treat any HYPE deposit QR as safe for HyperEVM sends?
No. Matching ticker letters leave the rails unproven, because HyperCore spot withdrawals and HyperEVM sends can land on different address families even when both screens say HYPE. Official onboarding tells you to confirm the venue supports the EVM half before you send it, and a small test send is the cheap check. BloFin's HYPEUSDT row is exchange custody of a USDT-margined perpetual, a different destination from a HyperEVM withdrawal.
If a community directory lists a bridge, is that bridge a Hyperliquid app?
No. Official HyperEVM docs point at community directories as places to track apps and tools. A bridge tile on those sites is still a third-party rail. Some tiles will be real contracts on 999, some will be frontends over the book, and some will only borrow the logo. Run the environment test on the product you clicked.
If I deposit into HLP again before the first lockup ends, when can I withdraw?
The official wait is 4 days after your most recent deposit, so a second deposit restarts the wait on the whole balance. The earlier lot's original morning is gone. That is a HyperCore vault rule, separate from an ERC-20 cooldown on chain ID 999. A BloFin HYPEUSDT listing stays a CEX row.
If I hold HYPEUSDT on BloFin, can I move that position into HLP?
No. A BloFin HYPEUSDT fill is a CEX USDT-margined perpetual under BloFin custody, while an HLP deposit is a HyperCore protocol-vault action behind a 4-day lockup. There is no transfer rail from that BloFin row into HLP, so buying the listing here leaves you on BloFin custody. HYPERUSDT (Hyperlane) is a third listing on the same venue and still stays Hyperlane, so sorting the ticker is still the first job before any vault talk.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated August 2026. Primary sources include the Hyperliquid documentation on HyperEVM, HyperCore, builder codes, protocol vaults, and Hyperliquid 101, plus OneKey's 2026 onboarding note and BloFin's public instruments API. Protocol facts independently verified against cited sources current as of August 2026.
This article is educational and general in nature, not financial or investment advice. Cryptocurrencies like HYPE carry real risks, including price volatility, liquidation, venue risk, and the chance of losing funds. Nothing here is a recommendation to buy, sell, hold, or trade on Hyperliquid or on BloFin. Do your own research, and consider speaking with a licensed professional before making financial decisions. BloFin does not provide investment advice.