Stake to deploy on Hyperliquid is the HIP-3 listing lock. A qualifying deployer posts the current official mainnet stake of 500,000 HYPE to run one independent perp dex. Those coins are listing collateral for that dex. The spec says that 500,000 figure is expected to decrease.
Suppose you compare posting idle HyperCore HYPE into HIP-3 deployer stake versus ordinary delegated staking. Path A credits instantly, waits 7 days to come back, and has no automatic slashing at the stake layer today. Path B is a listing bond: 500,000 official, a 183-day floor after a dex is deployed, and a validator vote that burns coins rather than paying traders.
The same HYPE can do consensus work or listing collateral. Those jobs use different waiting periods and different slash rules.
What stake to deploy means
Stake to deploy is the HIP-3 listing requirement on HyperCore. A deployer who meets today's official mainnet stake can list one independently margined perp dex, set that dex's markets, oracles, and contract specifications, and operate them onchain. The coins posted for that right are listing collateral. They sit against the quality of that listing.
HIP-3 builder-deployed perps covers the product a deployer lists. Stake to deploy is the holder-facing half of the same mechanism: what posting the coins binds, how long they have to stay, and how that job differs from ordinary delegated staking. The project's own HIP-3 article puts the listing right in one sentence: "Any deployer that stakes 500k HYPE can deploy a perp DEX, define the markets, oracles, and contract specifications, and operate them onchain" (source: Hyperliquid, HIP-3).
That sentence is a listing right. It is a permission to run one builder dex on HyperCore's book. A trader who loses money on that book still lives or dies on mark, margin, and the oracle the deployer set. The posted HYPE raises the cost of listing a weak market. It does not write that trader a check.
Path A and Path B reuse the English word stake. Path A is a HyperCore staking-account job: spot HYPE moves in at once, coming back waits on a 7-day queue, and automatic slashing is not implemented at that layer today. Path B is the listing bond. Meeting Path A's size does not convert those coins into Path B. Sitting in a Diamond fee-tier band, which also starts above 500,000 HYPE, is a third coincidence. A holder can sit in that discount band without deploying a perp dex.
The 500,000 HYPE listing requirement
The 500,000 HYPE mainnet figure is the protocol's current official listing requirement for one HIP-3 perp dex. The same spec says that requirement is expected to decrease as the infrastructure matures. Treat the pair as a living official line. Extra above the latest requirement can be unstaked.
The spec's adjacent clauses sit around that figure as one packet. Deployers must maintain 500,000 staked HYPE to keep markets at a stated quality standard and to protect users. Any amount staked above the most recent requirement can be unstaked. A future upgrade may support multiple dex deployments sharing the same deployer and staking requirement. Once all assets are settled, a deployer's required stake is free to be unstaked. Slashing is technical and does not distinguish between malicious and incompetent behavior. HIP-3 should not require slashing in its final state (source: HIP-3: Builder-deployed perpetuals).
Read those as one set of rules. The requirement can fall as infrastructure matures. Excess above the latest requirement can leave. One lock currently funds one independently margined dex. Halt plus settle is what later frees the required stake, still subject to the 183-day floor.
Model the lock as 500,000 HYPE today. Re-read the spec before you treat that integer as a permanent input. Converting 500,000 HYPE into a dollar headline answers a price question this mechanism does not cover. The listing requirement is denominated in HYPE.
A HyperCore spot balance of 500,000 HYPE is spendable inventory. Listing collateral is posted deployer stake. Sitting in spot, even at 500,000, does not qualify a deployer identity and does not start the maintain calendar, because a dex has not been deployed. Spot can later be delegated as Path A or posted as Path B. Until one of those postings exists, the integer in spot is just size.
The 183-day floor and one dex per lock
Once a dex is deployed, the required stake has to be maintained for a minimum of 183 days. That window counts from deploy, not from the first fill and not from a later halt. One qualifying deployer currently runs one perp dex under that lock. A smaller posting cannot buy a fraction of a listing.
Walk through capacity with round numbers. You hold 500,000 HYPE on HyperCore, which meets today's official requirement, so Path B is even possible as a listing bond. 50,000 is a different product in the sense that it is closed: it does not purchase 10 percent of a listing. There is no protocol coupon that lets five wallets glue 100,000 each into one deployer identity. The one-dex rule is current policy. A future upgrade may share a staking requirement across multiple dexes, and that clause is already in the spec. It is not the rule that is live today.
Halt can settle positions to mark. Once every asset on that dex is settled, the required stake is free to leave. The minimum maintain window still started at deploy. A 30-day-after-halt floor is a different calendar than the sentence on the spec. You do not need the halt action's JSON. You need the dates: deploy starts 183 days, the 7-day unstaking queue is a later hop, and both can sit on the same coins.
Independent margining is the other capacity fact. The lock buys one dex with its own order books and its own deployer settings. A blow-up on that builder book is a separate margin account from validator-operated BTC. That independence is why the lock exists as listing collateral. HYPE held on a centralized venue still sits outside that dex's margin.
Day 183 is a maintain minimum counted from deploy. After the later halt-and-settle condition, the required stake is allowed to leave, which is a permission you still have to exercise. HyperCore does not send a scheduled push of those coins back to a spot account on a calendar day. Starting that exit is a later action.
How HIP-3 slashing and the unstaking queue work
HIP-3 slashing is a deployer penalty by stake-weighted validator vote. The coins that come out are burned. They are not paid to people who lost money on that builder book. The stake stays slashable through the 7-day unstaking queue. That combination is why the lock is listing collateral.
The vote does not sort malice from incompetence from a stolen key. The spec cares about the effect on protocol correctness, uptime, and performance. Slashable is a deployer penalty. It is not a trader rebate. An independent write-up of the same design is blunt about the destination of those coins: "slashed HYPE is burned; it does not go to validators" (source: FalconX, The Transformational Potential of Hyperliquid's HIP-3). If you are the trader on that book, your residual is still mark, margin, and the oracle the deployer set. If your coins are the lock, you are the one who can lose the slash.
The 7-day unstaking queue is the trap in the other direction. Starting a withdrawal does not take the coins off the slash list for a week. Both Path A and Path B last a week on the way out, and they are different queues. The deployer queue stays HIP-3 slashable. The delegated queue is the hop from a staking account back to spot.
Trader-facing residual, including why an LST that funded a deployer has to diligence that operator, sits in HIP-3 deployer slashing risk. That is where the trader residual for that book belongs.
Jail on Path A stops rewards for that validator's delegators and leaves their principal in place. HIP-3 slash is a separate stake-weighted vote on deployer collateral. Those two penalties do not share a switch. A jailed consensus operator is, by itself, a Path A fact. It is not a burn of listing collateral sitting in a different posting.
How deployer stake differs from delegated staking
Ordinary delegated staking of HYPE is a HyperCore staking-account job. Spot HYPE transfers in instantly. Coming back waits on a 7-day queue. Automatic slashing is not implemented at that layer today. Path A is that product. Path B is a listing bond that happens to reuse the word stake.
How HYPE staking works covers those timelines in depth, including the 1-day delegation lockup and the five-pending-withdrawal cap. The contrast this lock needs is narrower. Docs even warn that the vocabulary collides: delegate and stake are used interchangeably, because Hyperliquid only supports delegated proof of stake (source: Hyperliquid Docs, staking). HIP-3 then uses staked HYPE for a listing requirement. Same English word. Two jobs.
Path A can start at 1,000 HYPE. Path B currently wants 500,000. Path A can undelegate into the staking account after a 1-day lockup, then wait 7 days to spend as spot. Path B cannot treat halt as a same-week exit, because 183 days from deploy still sits in front of that queue, and the queue itself stays slashable. Path A has no automatic stake-layer slash today. Jail can stop rewards without burning principal. Path B is built around a vote that can burn.
The five-pending cap is a Path A staking-account limit on how many staking-to-spot exits can sit at once. Coins posted as a HIP-3 lock do not fill one of those five Path A slots, and filling those slots does not post a listing bond. If you are waiting on Path A withdrawals, that queue is still the staking product. The listing lock has its own later unstaking hop after the maintain floor.
A validator's 10,000 HYPE self-delegation is the operator self-bond that lets a validator become active, locked for a year. It does not chip 10,000 off the listing requirement, and delegators never had to post it in order to stake. A wallet that already posted that operator minimum still owes the full HIP-3 listing requirement if it wants Path B. Consensus eligibility is not a down payment on a builder dex.
The generic primer still helps if stake only meant a savings product: what staking is is that category. How Ethereum validators work is the other chain's version of an operator bond. It is useful as a reminder that a validator self-bond and a listing lock are large for different jobs.
A staking-account line is Path A work. Listing collateral is a different HyperCore posting. To reuse delegated coins as a listing bond you first have to leave the staking account, which is Path A's week-long exit, and only then could you post them as deployer stake if you still want Path B. There is no in-place conversion that turns delegated HYPE into a listing lock while it is still earning consensus rewards.
HIP-4 vs BloFin listings vs this lock
HIP-4 outcome markets are a different primitive. Permissionless HIP-4 deployer actions are still labeled Testnet-only on the docs index. A BloFin HYPEUSDT position is a CEX instrument rather than HyperCore deployer collateral. Neither posting is the HIP-3 500,000 lock.
HIP-4 outcome markets are fully collateralized and bounded. They do not inherit this 500,000 figure. The docs index still marks HIP-4 deployer actions as Testnet-only (source: Hyperliquid Docs, llms.txt). A live daily BTC binary is evidence that an outcome market can trade. It is not proof that you can permissionlessly list a new outcome on mainnet, and it is not proof that HIP-4 secretly uses HIP-3's 500,000.
If that API later opens, the HIP-4 deployer page already says the two requirements add and do not share a double-count: stake that counts toward HIP-3 deployment does not double-count toward outcome deployment (source: Hyperliquid Docs, HIP-4 deployer actions). That page does not state 500,000. Collapsing both products onto one figure puts the wrong requirement on the wrong product.
BloFin's public SWAP catalog lists HYPE-USDT as the JSON instrument ID for the live USDT-margined perpetual at 75x, listed December 19, 2024 11:30 UTC (source: BloFin instruments API, SWAP). In reader copy that pair is HYPEUSDT. It is a USDT-margined perpetual rather than a HyperCore staking account. The spot row is live too, listed May 30, 2025 13:30 UTC (source: BloFin spot instruments API). That pair is HYPE/USDT. HYPERUSDT on the same book is Hyperlane, a different listing. None of those instruments is Path B.
What Hyperliquid is covers the chain, the token, and the other ticker. Stake to deploy is narrower: one HIP-3 listing bond on HyperCore. A BloFin fill can be HYPE you later withdraw, and it is still custodial until it leaves.
HyperEVM gas is how HYPE pays for general-purpose execution. The HIP-3 listing requirement is a HyperCore deployer posting. Having HYPE somewhere in the Hyperliquid environments is not the lock. A gas balance and Path A delegated coins are other jobs. This lock only exists once those coins are posted as deployer stake.
Opportunity cost while HYPE sits as deployer stake
While 500,000 HYPE sits as HIP-3 deployer stake, you forgo spendable spot, a fast exit, and the option to treat those coins as ordinary delegated stake alone. You also take a vote-and-burn residual that delegated staking does not attach at the stake layer today. That opportunity cost is the listing requirement rather than a published yield.
The spec does not publish a deployer-stake APY, and no live rate is attached to that listing lock. Emissions math on the staking docs is a formula for delegated HYPE, tied to total stake and the emissions reserve, and even that formula is not a live rate to bake. Path B is collateral for listing rights. If a third party later wraps that lock into an LST, the slash still follows the coins, which is why diligence sits on the operator rather than on a yield headline.
You also forgo treating 500,000 as only a fee-tier cutoff. Diamond happens to start above 500,000 HYPE, and that table cuts trading fees without listing a dex. Mixing those two 500,000 figures is how a discount band gets talked about as if it were a listing bond, or the reverse.
Hyperliquid is also a competing venue. If you wanted HYPE price exposure at BloFin you wanted a SWAP or SPOT instrument. If you wanted consensus work and a 7-day way back you wanted how to stake HYPE. If you wanted to understand a builder book you already trade you wanted the HIP-3 product page, then this lock, then the slashing residual. Allocation framing for staking in a bag still lives in staking in a crypto portfolio, which is the generic decision, not a HIP-3 deploy.
You do not need the auction reserve formula or every slash guideline. The forfeit is liquidity, calendar, and burn risk, with no live APY attached to the listing requirement.
Listing lock, delegated staking, and a BloFin pair compared
Stake to deploy is a HIP-3 listing bond of 500,000 HYPE today, expected to decrease, held at least 183 days after dex deploy, slashable by vote, and burned rather than paid to traders. Delegated staking, HIP-4, and a BloFin instrument are other jobs for the same four letters.
| Deployer lock | Delegated staking | BloFin HYPEUSDT | |
|---|---|---|---|
| Job | List one HIP-3 dex. | Consensus and emissions. | CEX price exposure. |
| Size today | 500k official, can fall. | Any amount. | Position size. |
| Exit | 183-day floor, then queue. | Instant in, 7-day to spot. | Close or withdraw. |
| Slash | Validator vote, burned. | No automatic stake-layer slash. | Ordinary perp PnL. |
CoinGecko still describes the chain as a layer-1 blockchain best known for perpetual futures and spot trading (source: CoinGecko, Hyperliquid). That native book is a competing venue. A BloFin HYPE instrument is CEX exposure. The listing bond lives on HyperCore with that dex's oracle and that dex's lock.
If the question was which posting you are actually holding, the table is the filter: listing bond, consensus work, or CEX instrument. Mixing those three is how a 500,000 fee-tier cutoff gets treated as a listing credential, or how a SWAP fill gets treated as HyperCore collateral.
You do not need to memorize fee-share percentages, Dutch-auction hyperparameters, or every future upgrade clause. Weigh whether you were asking about a listing bond, a consensus delegation, or a CEX instrument, then read the spec's decrease sentence before you treat 500,000 as frozen. Nothing here is a recommendation to post a deployer lock, delegate, or trade HYPE.
Frequently asked questions
If my 500k is already delegated, do I have to wait out the 7-day staking-to-spot queue before those coins can sit as HIP-3 listing collateral?
Yes. A staking-account line is Path A work. Listing collateral is a different HyperCore posting, not a rename of the same row. To reuse those coins as a listing bond you first have to leave the staking account, which is Path A's week-long exit, and only then could you post them as deployer stake if you still want Path B. There is no in-place conversion that turns delegated HYPE into a listing lock while it is still earning consensus rewards. The hop is the Path A exit queue, not a HIP-3 rename.
Does HIP-3 listing collateral occupy one of Path A's five pending-withdrawal slots?
No. The five-pending cap is a Path A staking-account limit on how many staking-to-spot exits can sit at once. Listing collateral is a different posting. Coins posted as a HIP-3 lock do not fill one of those five Path A slots, and filling those slots does not post a listing bond. If you are waiting on Path A withdrawals, that queue is still the staking product. The listing lock has its own later unstaking hop after the maintain floor, which is a different counter than those five slots.
If my HYPE is only sitting as HyperEVM gas, does that balance count toward the HIP-3 500k?
No. HyperEVM gas is how HYPE pays for general-purpose execution. The HIP-3 listing requirement is a HyperCore deployer posting. Having HYPE somewhere in the Hyperliquid environments is not the lock. A gas balance and Path A delegated coins are other jobs. This lock only exists once those coins are posted as deployer stake, which is not a gas-tank reading.
On day 183 after deploy, does HyperCore automatically return the required stake to my spot account?
No. Day 183 is not a disbursement date. The floor is a maintain minimum counted from deploy. After the later halt-and-settle condition, the required stake is allowed to leave, which is a permission you still have to exercise. HyperCore does not send a scheduled push of those coins back to a spot account on a calendar day. Starting that exit is a later action, not an automatic credit.
If a validator I delegated to on Path A is jailed, does that jail also burn my HIP-3 listing lock?
No. Jail on Path A stops rewards for that validator's delegators and does not burn their principal. HIP-3 slash is a separate stake-weighted vote on deployer collateral. Those two penalties do not share a switch. A jailed consensus operator is not, by itself, a burn of listing collateral sitting in a different posting. Keep the Path A jail fact on the staking page, and keep the listing-lock burn on this lock.
If I already have 500k HYPE in a HyperCore spot balance, is that already HIP-3 deployer stake?
No. Spot HYPE on HyperCore is spendable inventory. Listing collateral is posted deployer stake. Sitting in spot, even at 500,000, does not qualify a deployer identity and does not start the maintain calendar, because a dex has not been deployed. Spot can later be delegated as Path A or posted as Path B. Until one of those postings exists, the integer in spot is just size.
Does a validator's 10k HYPE self-delegation count toward the HIP-3 500k?
No. 10,000 is the operator self-bond that lets a validator become active, locked for a year. It does not chip 10,000 off the listing requirement, and delegators never had to post it in order to stake. Two large integers, two jobs. A wallet that already posted that operator minimum still owes the full HIP-3 listing requirement if it wants Path B, because consensus eligibility is not a down payment on a builder dex.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated August 2026. Primary sources include the Hyperliquid HIP-3 spec, HyperCore staking docs, the docs index, HIP-4 deployer actions, Hyperliquid's HIP-3 article, FalconX's HIP-3 note, and BloFin's public instrument APIs. Protocol and listing 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, deployer and oracle risk on builder markets, slashing of deployer stake, unstaking delay, venue risk, and the chance of losing funds. Nothing here is a recommendation to buy, sell, hold, deploy, stake, or trade HYPE. Do your own research, and consider speaking with a licensed professional before making financial decisions. BloFin does not provide investment advice.