Hyperliquid Glossary: Term Lookup for Chain, Token, and Market Words

A Hyperliquid glossary is a term lookup. Each entry is one short meaning plus a route to the guide written for that mechanism. Official docs currently list four numbered HIP labels, HIP-1 through HIP-4. Those four titles name four different proposals.

The job is to send you to the right next page. If you wanted the chain defined as a product, start with what Hyperliquid is. HIP-3 is a perp listing path. Builder codes are a fee on fills. Mixing those two words is how a lookup becomes the wrong click.

What a Hyperliquid glossary covers

A lookup line is one sentence, then a route. Mechanism detail, click paths, and product definitions live on the owning guides. If a cell starts walking steps, it has stopped being a glossary.

Suppose you type HyperBFT into a search box and land on a Hyperliquid word list. You want to know whether it is a second chain. The line should say it is the consensus name on this layer-1. The next click is HyperBFT consensus. Shared crypto words such as margin, mark, and funding already live in general crypto trading terms. They stay on that trading list.

A pointer word gets one sentence, then a route. A shared trading word stays on the trading glossary. A mechanism word names the guide and leaves the lesson there.

Suppose you typed HIP-3 and a gloss told you it meant builder codes. You would then approve a builder fee thinking you had understood a listing requirement. A one-line official title would have stopped that. The cost of a bad gloss is the wrong next click, not a missing adjective.

Hyperliquid, HYPE, and HYPER

Hyperliquid, HYPE, and HYPER share letters. They keep separate issuers. Sorting them is the minimum so you do not buy the wrong listing. The chain, the native token, and the Hyperlane ticker are three labels.

Market pages list the Hyperliquid token under HYPE. CoinGecko's Hyperliquid page titles the asset as a HYPE/USD live price chart (source: CoinGecko, Hyperliquid). That title is a ticker map. Leave a live price off a glossary line. HYPER is the collision. Hyperlane's intro describes a system that enables message passing and asset transfers across different chains without relying on centralized intermediaries or requiring any permissions (source: Hyperlane docs, intro). That is cross-chain messaging. Hyperliquid's book is a different product.

If the coin-versus-chain vocabulary is still new, how a coin and a chain differ is the generic fork. The two BloFin listings, including list dates, sit in HYPE versus HYPER ticker.

A beginner hub already sorted chain, token, and the other ticker as labels. A glossary lookup keeps the three nouns a searcher types into a board from collapsing. Same letters can still name two assets.

HyperCore and HyperEVM

HyperCore and HyperEVM are two execution environments on one chain. Collapse them and a book order starts to look like a contract call. A glossary cell names the half. Matching, gas, and transfer paths stay on the owning guides.

HyperEVM docs put the inheritance in one line: "The HyperEVM consists of EVM blocks built as part of Hyperliquid's execution, inheriting all security from HyperBFT consensus." HYPE is the native gas token there. Mainnet chain ID is 999. Testnet is 998 (source: Hyperliquid Docs, HyperEVM). That ID is a wallet field for this EVM half. Send HYPE to the HyperEVM half without gas and the contract call stalls. Send it to HyperCore spot when you meant gas, and the wallet on 999 still looks empty.

Book mechanics sit in HyperCore explained. Validators still run one consensus for both halves. The split is execution. A HyperCore fill is a book match. A HyperEVM call is a contract execution. Both land in the same HyperBFT committed list. The wallet field still has to match the half you meant.

A glossary line that treats HyperEVM as a second chain will send a wallet to the wrong ID. A line that treats HyperCore as an EVM app will skip the book. Keep the two words. Keep the one chain.

HyperBFT and the four HIP titles

HyperBFT is the consensus name on this layer-1. HIP is a numbered proposal. Official docs currently list four HIP titles on the live index. Builder codes are a per-order fee on fills, a separate trading word from those four numbers.

The HIP index is a short list of official titles: HIP-1 Native token standard, HIP-2 Hyperliquidity, HIP-3 Builder-deployed perpetuals, HIP-4 Outcome markets (source: Hyperliquid Docs, HIPs). Read those titles before you trust a gloss that swaps HIP-3 for builder codes.

HIP-1 is the native token standard. HIP-2 Hyperliquidity quotes HIP-1 tokens against USDC. Those two numbers sit next to each other on the index and still name different jobs.

HIP-3 is a perp listing path. The Hyperliquid protocol supports permissionless builder-deployed perps (HIP-3). The staking requirement for mainnet is 500,000 HYPE and is expected to decrease as the infrastructure matures (source: HIP-3: Builder-deployed perpetuals). That figure is a listing requirement for the deployer. The listing walk lives in HIP-3 builder-deployed perps. Slashing detail lives on that HIP-3 guide.

Builder codes are a different fee word. "Builder codes are processed entirely onchain as part of the fee logic" (source: Hyperliquid Docs, Builder codes). They attach a builder fee to a fill. HIP-3 remains the listing path. Builder codes remain the fee on fills.

HIP-4 is a bounded primitive. The docs describe it as useful for applications such as prediction markets and bounded options-like instruments (source: HIP-4: Outcome markets). The product walk lives in HIP-4 outcome markets. Deployer actions for HIP-4 are still marked Testnet-only on the docs index line for hip-4-deployer-actions.md): Testnet-only (source: Hyperliquid Docs, llms.txt). A live BTC binary is still a listed market. It is a different fact from a mainnet deploy button.

Trust the title on the index. That is the word the protocol assigned.

HLP, Hyperliquidity, the assistance fund, and staking

HLP, HIP-2 Hyperliquidity, the assistance fund, and staking share family letters. They keep separate jobs. A vault line is a vault line. A Hyperliquidity strategy is a spot quoting strategy. Mixing them is how a deposit hits the wrong wait.

HIP-2 is explicit about its design. Hyperliquidity is inspired by Uniswap, while interoperating with a native onchain order book to support sophisticated order book liquidity from end users. It is currently only available on spot pairs against USDC (source: HIP-2: Hyperliquidity). HLP is the protocol vault that quotes perps, takes liquidation inventory, and shares pnl. Depositor mechanics, including the 4-day wait after the most recent deposit, sit in HLP and vaults. A HIP-2 seed stays a HIP-2 seed.

Fees name the burn sink. The assistance fund uses the system address 0xfefefefefefefefefefefefefefefefefefefefe. It converts trading fees to HYPE as part of L1 execution and burns that HYPE (source: Hyperliquid Docs, Fees). That is a pointer. Full burn structure belongs on a tokenomics page.

Staking is a different wait. Transfers from the staking account back to spot have a 7-day unstaking queue, and there is currently no automatic slashing implemented (source: Hyperliquid Docs, Staking). The queue walk lives in HYPE staking. A glossary line can name the wait. It leaves the click path on that guide.

You do not need to memorize four waits. You need to know they are four different waits.

BloFin HYPE and HYPER listings

A BloFin listing is a venue balance. SWAP, spot, and the HYPER row are exchange words. They leave a CEX fill on this exchange. Sorting them keeps a glossary from treating the exchange board as the chain.

HYPEUSDT is a USDT-margined perp at 75x. HYPE/USDT is the spot pair. HYPERUSDT is Hyperlane at 50x. If the chart header says Hyperlane, you are on the HYPER listing. If it says Hyperliquid, you are on the HYPE listing.

The public SWAP book lists HYPE-USDT SWAP live at 75x, listed December 19, 2024 11:30 UTC, and HYPER-USDT SWAP as a different row at 50x. The unified instruments path asked for SPOT still returns SWAP rows, so the spot book is a different endpoint (source: BloFin SWAP instruments API). Reader copy for those perpetuals is HYPEUSDT and HYPERUSDT.

Dedicated spot instruments list HYPE-USDT SPOT as live, listed May 30, 2025 13:30 UTC, and HYPER-USDT SPOT as a separate row listed April 23, 2025 14:00 UTC (source: BloFin spot instruments API). Reader copy for those spot pairs is HYPE/USDT and HYPER/USDT. A glossary cell leaves those listings as the API wrote them. Native book how-to is a different URL.

Closing a SWAP returns quote, usually USDT. It leaves HyperCore HYPE out of a wallet. It leaves HyperEVM gas unpaid. If you treated a filled HYPEUSDT SWAP as a coin you could stake, the glossary already failed you before any staking screen loaded. Apps and environments are a different URL again, and that cut lives in the Hyperliquid ecosystem.

A CEX listing is price exposure at BloFin. Native HyperCore still needs its own session. Official onboarding lets you trade with a normal defi wallet or by logging in with your email address (source: Hyperliquid Docs, How to start trading). Email uses a 6-digit code. A wallet path still has Enable Trading after Connect. Neither path is a BloFin password. A signature on that native path spends no HyperEVM gas.

When to leave the glossary

The glossary is the right tool when you already want a definition, and you only need the official title plus the next URL. It is fast on collisions. It is weak on procedures. A word list is the wrong tool when you need a mechanism, a click path, or a product definition. Then you want the hub, the ecosystem frame, or a how-to, not another cell. The list still helps you pick which of those URLs to open.

If you still cannot tell Hyperliquid from HYPE, open the hub. If you know the names and want apps versus books, open the ecosystem frame. If you only wanted funding and TWAP, you wanted the trading glossary all along. Safety, scams, and should I buy each own their own guides. None of those questions is answered by a one-line HLP cell.

A term lookup also fails when you need history, genesis, or a named lab. Those are other articles. The list can tell you the word names a mechanism. It cannot replace the mechanism. Use it to pick the next URL, then leave it.

You do not need to hold every HIP number. You need the official title, the collision next to it, and the guide that covers the rest. A dump of every Hyperliquid URL is the other failure mode. Open one next guide. If you needed a click path, another cell will not become one. If you only needed a ticker sorted, you are already done.

Frequently asked questions

If I add chain ID 998, what did I add?

Testnet HyperEVM. Mainnet HyperEVM uses chain ID 999. Testnet uses 998. Both use HYPE with 18 decimals on that EVM. A wallet that saved 998 will look empty on mainnet apps that expect 999. Check the ID before you send HYPE as gas. If the field says 999, you are on mainnet HyperEVM. If it says 998, you are on the test network the docs name next to that ID.

What is the official title of HIP-3, and how do builder codes relate?

HIP-3: Builder-deployed perpetuals. That is the title on the HIP index. Builder codes are a separate trading page about a per-order fee on fills. A fill can carry a builder code without being a HIP-3 listing, and a HIP-3 market can exist without that extra fee. The builder-codes page is still real. It is a fee on fills. If you needed listing-requirement detail, open the HIP-3 guide.

If I undelegate today, when can I move HYPE back to spot?

The 7-day unstaking queue. Spot to staking is instant. Staking back to spot waits seven days. Each address may have at most five pending withdrawals in that queue. A glossary line can name the wait. Support cannot shorten it. If you needed the click path, that is the staking guide. Undelegating is also a different action from a HIP-3 deployer unstake.

Can HIP-2 quoting and an HLP deposit sit on the same address?

Yes. They stay separate balances. HIP-2 quoting is a spot-side strategy on HIP-1 pairs against USDC. HLP is a perp-side vault with its own 4-day wait after the most recent deposit. Holding both on one address leaves them unmerged. A HIP-2 seed stays a HIP-2 seed, and an HLP deposit stays an HLP share. If a UI shows one USDC number, ask which balance it belongs to before you treat it as the other.

If CoinGecko lists HYPE, why does a BloFin board still show HYPER?

Because HYPER is Hyperlane, a different listing. CoinGecko's Hyperliquid page maps that project to HYPE in the title. BloFin also lists HYPERUSDT, which is a different token. Seeing both rows is expected. Sort by instrument ID: HYPEUSDT versus HYPERUSDT on perps, HYPE/USDT versus HYPER/USDT on spot. If you wanted native HyperCore HYPE, a CEX row is still a CEX balance even after you pick the HYPE ticker.

Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Primary sources include the Hyperliquid Docs HIP index, builder-codes page, HIP-2, fees, HIP-3, HIP-4, llms.txt, HyperEVM, staking, Hyperlane intro, CoinGecko's HYPE ticker page, and BloFin's SWAP instruments API. Protocol facts independently verified against cited documentation 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, venue and custody risk, and the chance of losing funds. Nothing here is a recommendation to buy, sell, hold, or trade HYPE, HYPER, or Hyperliquid on BloFin or elsewhere. Do your own research, and consider speaking with a licensed professional before making financial decisions. BloFin does not provide investment advice.