Research/Education/Hyperliquid/How HLP and Hyperliquid Vaults Work: What a Depositor Is Exposed To
# Hyperliquid

How HLP and Hyperliquid Vaults Work: What a Depositor Is Exposed To

Sabrina Chua08/25/2026
HLP is Hyperliquid's protocol vault. Depositors share market-making and liquidation pnl, including losses, and can withdraw only 4 days after the most recent deposit.

HLP is Hyperliquid's protocol vault. Depositors share that vault's market-making and liquidation pnl, including losses. Treating the share as a savings rate is the loss step. You sit on the other side of backstop liquidations, and you can withdraw only 4 days after your most recent deposit.

Suppose you treat that share like cash you can tap after a rough weekend, then deposit and add more the next morning as if the new lot sat beside the old one. The official wait is 4 days after the most recent deposit, so the add-on restarts the wait on the whole balance while the vault can still take inventory a book-first close failed to absorb.

Protocol vault, user vault, and HyperEVM tokenized vault share a word. Each product has its own wait.


What an HLP depositor is exposed to

HLP is the protocol vault whose depositors share market-making and liquidation pnl. That share includes losing days. The liquidator vault can take inventory a book-first close left behind when a position sits below two thirds of maintenance, and withdrawal waits 4 days after the most recent deposit.

What Hyperliquid is covers the chain and the token. The depositor job is narrower. HLP is the protocol vault that runs market-making, liquidation takeovers, and Earn USDC supply as strategy work, and a depositor holds a share of that pnl.

A savings account credits a rate and returns principal on a notice period. An HLP share moves with inventory pnl. HLP is not a savings rate. The 4-day wait is a withdrawal lockup measured from the last inbound, and the returned size still follows that vault's profits or losses.

The close path, the wait, the three products that share the word vault, and the look-alikes on a CEX board, in a staking queue, or on HyperEVM are the rest of the map.

How book-first liquidation uses the HLP liquidator vault

When equity falls through maintenance, HyperCore first tries a book-first close. Residue that still sits below two thirds of maintenance can move into HLP's liquidator vault. A depositor is watching that inventory stream. The vault chooses the names.

The liquidations page names the liquidator vault as a component strategy of HLP. Positions that sit below two thirds of maintenance margin can be taken over by that vault (source: Hyperliquid Docs, Liquidations). On average the docs describe that stream as profitable for the liquidator, and they say the pnl from those takeovers goes to the community through HLP. That is inventory risk with a positive expected sign in the source's own wording. It is still a sign, not a floor under a depositor's balance. How the Hyperliquid book works covers rest, cancel, and the book-first close. The residue that vault takes is the depositor fact.

The close path has three steps.

  1. Equity falls through maintenance. HyperCore sends market orders onto the book for the position.
  2. If equity is still below two thirds of maintenance, the liquidator vault can take over.
  3. Depositors share that takeover pnl, including the day the takeover loses money.

Suppose the book cannot absorb a crossed account and the mark keeps going. On a cross backstop the liquidator vault takes the trader's cross positions and cross margin. On an isolated backstop it takes that isolated position and isolated margin, and the trader's cross book stays put. Your share moves with that pnl either way, including the day the takeover is the wrong sign, even though you did not send a bid on that name and only deposited into the protocol vault that runs that strategy. How HyperCore works is the matching environment those takeovers still clear on.

A generic primer on what an order book is covers bids, asks, and walking the spread. Hyperliquid's backstop is a vault strategy on that book. The fee schedule is a separate invoice.

During a backstop the liquidator vault keeps a buffer so takeovers are profitable on average. That buffer is why the docs can describe the stream as profitable for the liquidator without flooring a depositor's share this week.

The 4-day withdrawal wait after your latest deposit

The official lockup is 4 days after your most recent deposit. A later top-up restarts the wait on the balance. The older lot's original morning is gone. That is a HyperCore vault rule. Support cannot rewrite it.

The protocol-vaults page states the product, then the wait. HLP opens strategies that other exchanges keep for privileged parties, the community can provide liquidity and share pnl, and HLP is fully community-owned, which is the project's own claim about who receives that pnl (source: Hyperliquid Docs, Protocol vaults). "This means you can withdraw 4 days after your most recent deposit" (source: Hyperliquid Docs, Protocol vaults). If you deposited on September 14 at 08:00, you could withdraw on September 18 at 08:00. That arithmetic is the docs' own example, not a live APY.

Suppose the first lot landed on that September 14 08:00 stamp, and a second lot lands on September 15 because the share looked cheap. The most recent deposit is September 15, so the wait on the whole balance restarts. The official sentence covers the whole balance. You are still in that liquidation inventory while you wait, including a day when backstop flow is the wrong sign. Perpetuals versus futures still help if open-ended mark-to-market is unfamiliar. Four days stay four days.

Legacy user vaults use a shorter 1-day lockup on the same family of pages. That is a different product. Early exit from HLP still uses the 4-day wait.

Community-owned is the project's own claim about who sits in the pnl stream. It is silent on strategy quality. Support cannot rewrite a HyperCore lockup, because the wait is the product.

Protocol vault vs user vault vs HyperEVM tokenized vaults

Hyperliquid uses vault for three depositor-facing products. Mixing them into one yield product is how a 4-day protocol lockup gets treated as a 1-day user-vault exit, or as an ERC-20 share on HyperEVM. Sort the product before you sort the return.

Vault type Withdrawal wait HIP-3 and spot Profit share
HLP, protocol vault 4 days after most recent deposit. Not a listing right. None on protocol vaults.
Legacy user vault 1 day. Cannot trade spot or HIP-3. 10 percent to the leader.
HyperEVM tokenized vault Separate from HLP's 4-day lockup. Docs: CoreWriter access including HIP-3. Custom accounting.

HLP is the protocol vault on the current protocol-vaults page. Legacy HyperCore user vaults are the 2023 products whose depositor and leader pages still sit beside it. HyperEVM tokenized vaults are the later general case. Builders can create and tokenize vaults on HyperEVM with fully customizable accounting (source: Hyperliquid Docs, Vaults). That sentence is about builders minting a vault share with CoreWriter access to HyperCore, including spot and HIP-3 in all quote assets on that page's own wording. The docs call that a strict improvement over legacy HyperCore vaults that still omit HIP-3 and spot. It is a capability at that layer. Whether a given minted share implements the path is still a contract-read. HLP remains a HyperCore protocol vault.

Legacy leaders still trade only validator-operated perps. Vaults can trade validator-operated perps, and they cannot trade spot or HIP-3 perps (source: Hyperliquid Docs, For vault leaders (legacy)). If the job is HIP-3 inventory inside a user vault, that product cannot take the fill. A vault share is a different claim from a Yes token and from a builder perpetual. HIP-3 builder-deployed perps still hold the listing lockup. Legacy vaults cannot trade those markets, which is the depositor fence.

A comparison table is a description of waits and rights. Which product fits depends on whether you wanted protocol inventory, a leader's validator-perp book, or a HyperEVM share with custom accounting.

How vault shares, profit share, and leader fees work

A vault deposit is a share of that vault's profits or losses. Protocol vaults take no leader cut on top of that share, so a depositor can lose, and past figures on a vault page are not a guarantee.

The legacy depositor page states the economic claim, then walks a user-vault example that uses 100 USDC as the share unit on that page. That walk is user-vault arithmetic. Protocol-vaults leaves HLP's depositor unit unnamed. "By depositing, you earn a share of the profits, or losses, of the vault" (source: Hyperliquid Docs, For vault depositors (legacy)). The same page also says past figures are not a guarantee of future returns.

Suppose 100 USDC goes into a vault that already holds 900. That lot is 10 percent of 1,000. If the vault later totals 2,000 with no other flows, the same share is 200 before a 10 USDC leader cut, with possible slippage while open positions close. The 100 USDC unit belongs to that user-vault walk. Protocol-vaults names HLP supplying USDC in Earn as a strategy job, and it leaves the depositor-asset field blank.

Protocol vaults are the no-cut case, which the legacy HyperCore vaults page states in the same breath as the leader cut. Vault owners receive 10 percent of the total profits. Protocol vaults do not have any fees or profit share (source: Hyperliquid Docs, HyperCore vaults (legacy)). Leaders still post a 100 USDC minimum, pay a 10,000 USDC creation fee distributed like trading fees, and must keep at least 5 percent. Those remain leader rules on the 2023 product. Independent explainers that refuse a fixed yield match that silence. The official page does not promise positive returns or a fixed yield (source: VaultVision, How the HLP vault works).

Live APY and TVL on app.hyperliquid.xyz/vaults stay on that UI. A static explainer cannot freeze them. Generic DeFi yield for crypto investors still names the usual yield traps. Which Hyperliquid vault type you hold is the extra filter.

Fee routing into HLP, the assistance fund, and deployers is a different cut than depositor pnl. The burn half sits in how the assistance fund burns HYPE. Venue risk, token risk, and deployer risk still sit in whether Hyperliquid is safe. A share of HLP is inventory exposure. It is a separate question from a venue safety grade.

You are in the strategy's pnl, including the ugly days, with no protocol profit share on HLP and no live rate invented for the share.

HIP-3 and HIP-4 access by vault type

Legacy HyperCore user vaults cannot take HIP-3 or spot fills. HyperEVM tokenized vaults are documented with CoreWriter access that includes HIP-3. HIP-4 is still a bounded book claim. Mixing those three is how a Yes token gets filed under HLP.

The comparison table lists those rights. The listing lockup and the vault lockup stay separate. A HIP-3 builder perpetual still has a deployer oracle and a listing lockup on staked HYPE. The staking requirement for mainnet will be 500,000 HYPE, and that requirement is expected to decrease over time as the infrastructure matures (source: Hyperliquid Docs, HIP-3). That 500,000 figure is a listing parameter. Staking it to deploy a market leaves a depositor share uninsured, and holding HLP leaves listing rights with the deployer. HIP-4's fully collateralized Yes still settles on the book. Settlement is conversion of Yes and No, and the product split stays in HIP-3 versus HIP-4.

Suppose the job is HIP-3 inventory without listing a dex. The docs name CoreWriter access at the HyperEVM vault standard, which is a capability at that layer. The contract still has to be read. HLP remains the protocol vault's own strategies, including liquidations and Earn USDC supply. That work stays separate from a HIP-3 listing right. HIP-4 keeps its own settlement path, and a Yes fill leaves a protocol-vault wait untouched.

The operational filter is the product on the fill, not the word vault in the interface.

HLP compared with BloFin pairs, staking, and HyperEVM shares

An HLP deposit is a HyperCore protocol-vault share with the 4-day most-recent lockup. A BloFin account, HYPE in the staking queue, an ERC-4626 share on HyperEVM, and a HYPERUSDT fill are four other products that can share four letters and still sit on different rails.

The public SWAP book on August 20, 2026 lists HYPEUSDT at 75x, listed December 19, 2024 11:30 UTC, and a separate HYPERUSDT swap at 50x, listed April 22, 2025 13:15 UTC. In that JSON the instrument ids are HYPE-USDT and HYPER-USDT (source: BloFin instruments API, SWAP). A fill on either row is BloFin custody. Hyperliquid remains a competing venue, and BloFin is the CEX route that quotes HYPE here. HYPERUSDT is Hyperlane on the same board, so a password on this exchange leaves you off HLP.

Staking is a different wait on a different asset. How HYPE staking works covers the 7-day staking-to-spot transfer queue. That queue is a staking wait. HLP is a protocol-vault share, a separate product from a HYPE staking account.

ERC-4626 is the Ethereum tokenized-vault standard HyperEVM vaults may follow. The specification presents it as a standard API for tokenized vaults that lowers integration effort for yield-bearing vaults (source: ERC-4626: Tokenized Vaults). That standard is why a HyperEVM share can look like a redeemable ERC-20. It is a different interface from HLP's HyperCore lockup.

Ethereum smart contracts still cover generic contract literacy. Crypto security still covers the usual custody hygiene. Neither page turns a CEX login into a vault share.

If the product is the protocol vault with the 4-day most-recent lockup, it is HLP. A fourth slogan will not make a CEX fill, a staking queue, or a HyperEVM share into that vault.

How to evaluate a vault deposit before you send funds

Weigh the job first, then the product, then the wait. A vault page that shows APY is describing a UI statistic the docs point at. The figure is a screen reading. The loss step is still treating the share as cash you can reclaim on the morning prices reverse.

A sort dashboard and a dedicated vault page are doing different jobs even when they share a ticker. Sort tiles order vaults so a visitor can scan, and the rate they show is that sort key. Your Performance on a dedicated vault page is that vault's history for the address looking at it. It is a history view. A later inbound still joins the same lockup. Screenshot the product (the lockup sentence, profit-share rules, and whether that vault can even touch HIP-3) instead of screenshotting the tile as if the tile were the lockup.

Pasting a dashboard tile as a coupon, treating Earn supply as a second exit, or asking support to shorten a HyperCore lockup are the same savings mistake in three costumes. A later inbound still restarts the wait on the balance already held. Earn USDC supply stays a strategy the protocol vault can run. Support cannot rewrite a HyperCore lockup, because the wait is the product.

Check five things before you send funds.

  1. Name the vault type: protocol, legacy user, or HyperEVM tokenized.
  2. Read the withdrawal wait from the docs for that type.
  3. Read the profit-share rule, including the protocol vault's no-cut case.
  4. Check whether that vault can touch HIP-3 or spot.
  5. Leave the APY tile on the sort UI.

Pick the job, then pick the product, and leave the APY tile on the sort UI.


Frequently asked questions

If HLP supplies USDC in Earn, can I withdraw that Earn balance on Earn's timeline?

HLP supplying USDC in Earn is a strategy on the protocol-vaults page. The strategy sits inside the same protocol vault, so the 4-day wait after your most recent deposit still governs the share. A CEX USDT row still leaves the depositor-asset field blank. If a later Earn screen shows a balance, read that screen as Earn. That balance is a strategy view. It stays bound to HLP's wait.

If I withdraw HYPEUSDT from BloFin onto Hyperliquid, does that inbound open an HLP share?

A BloFin withdrawal is an exchange outbound. HLP is a HyperCore protocol-vault deposit behind its own lockup, so landing size on Hyperliquid is still only size on Hyperliquid. The USDT-margined HYPEUSDT SWAP fill stays BloFin custody until you withdraw it. Enable Trading is a different signature. HYPERUSDT on the same board is Hyperlane. None of those steps buy the share.

During a backstop, does the liquidated trader keep the maintenance-margin buffer?

During a backstop the liquidations page says the maintenance margin is not returned to the user, because the liquidator vault needs a buffer so takeovers are profitable on average. That is why the docs can describe the stream as profitable for the liquidator without flooring a depositor's share this week. A book-first close that actually meets maintenance still leaves remaining collateral with the trader. Skipping HLP leaves that close path in place.

If a user-vault leader closes the vault, are those depositors paid from HLP?

Leader docs say depositors receive their share of that vault when it is closed, after positions are closed. That share is the user vault's equity. Protocol vaults have no leader profit share, so HLP payout follows protocol-vault accounting. A BloFin withdrawal queue is a CEX outbound, on a separate rail from either vault's close path.

If I redeem a tokenized HyperEVM vault share, does that redemption draw from HLP's liquidator inventory?

ERC-4626 is the Ethereum tokenized-vault interface a HyperEVM share can follow, which is why that share can look transferable on chain. Redeeming it settles against that vault's accounting. HLP's liquidator inventory stays on HyperCore. The protocol vault remains the HyperCore product, and redeeming the share leaves HyperCore's 4-day most-recent lockup in place. A CEX login still sits on neither product.


Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated August 2026. Primary sources include the Hyperliquid documentation on protocol vaults, HyperEVM vaults, liquidations, HIP-3, and legacy vault depositors and leaders, plus ERC-4626, VaultVision's HLP explainer, and BloFin's public instruments API. 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 and vault deposits carry real risks, including inventory loss, liquidation-takeover risk, lockup risk, slippage on withdrawal, smart-contract risk on HyperEVM vaults, custody risk on an exchange fill, and the chance of losing funds. Nothing here is a recommendation to deposit into HLP or any vault, and nothing here is a yield. Do your own research, and consider speaking with a licensed professional before making financial decisions. BloFin does not provide investment advice.