How the assistance fund works
The assistance fund is a Hyperliquid system address, and HyperCore is Hyperliquid's onchain trading environment. Protocol trading fees that reach this address convert to HYPE inside layer-1 execution, then that HYPE is burned, which here means the conversion runs automatically in Hyperliquid's own chain processing when those fees are applied.
A December 2025 write-up of the burn discussion describes the control surface in one line. "There is no withdrawal function, no admin key, and no recovery mechanism built into the protocol." (source: BSCN, Hyperliquid HYPE burn vote) That is reporting on the project's address design, not a promise BSCN can enforce. The official fees page names the same 0xfefe address and the convert-and-burn job.
Suppose you paid 100 USDC in protocol fees on a native HyperCore fill and tried to open a claim against 0xfefe. The fees page gives you no withdrawal button on that address, and a CEX help form after a native fill is a different product, with an adjuster and a payout path.
An unofficial architecture wiki files the same fund under protocol vaults and calls it a safety net for the Hyperliquid ecosystem. That page also publishes a 93 percent fee allocation and describes TWAP buy sizes, which are time-weighted average price orders spread across an interval (source: Hyperliquid community wiki, vault). That wiki sits off Hyperliquid Docs, and the official fees page omits the 93 percent figure and those TWAP sizes. Official control is the system address, and official purpose is convert-and-burn as execution.
A tokenomics lab models purchased HYPE as a balance the fund holds. Holding those coins, it writes, preserves optionality for protocol-owned treasury operations, including emergency liquidity and insurance payouts in extreme events (source: Giants Labs, HYPE tokenomics). That optionality is the lab's reading of a balance it treats as held. The official fees page states a different job: HYPE in the assistance fund is burned, which removes those tokens from circulating and total supply.
If you wanted a vault share with inventory profit and loss, you wanted HLP, which is a different destination, and if you wanted a CEX ledger line, you wanted a venue balance. The fund is the address in the middle, built to convert and burn.
Where protocol fees go
Protocol trading fees on Hyperliquid are directed to HLP, the assistance fund, and deployers as three named destinations. HLP is Hyperliquidity Provider, a protocol vault, and deployers are parties who list spot assets or HIP-3 perps, which are builder-deployed perpetual markets.
| Destination | Official job | How you interact |
|---|---|---|
| HLP | Vault: market making, liquidations, Earn USDC, a fee slice | Deposit for a vault share and inventory pnl. Withdrawals wait 4 days after your most recent deposit. |
| Assistance fund | Convert fees to HYPE as L1 execution, then burn | No withdrawal, airdrop, or insurance check on 0xfefe |
| Deployers | May keep up to 50% of fees on listed assets | A ceiling those deployers may set on their own markets |
HLP is the inventory destination. Hyperliquidity Provider 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 (source: Hyperliquid Docs, Protocol vaults). That sentence is HLP's job list, so backstop pnl that lands in HLP stays inside that vault's share, off the assistance-fund address. The 4-day lockup is a vault rule after your most recent deposit, and waiting four days leaves 0xfefe closed.
The deployer slice is a keep-up-to cap on listed assets. Spot and HIP-3 perp deployers may choose to keep up to 50% of trading fees generated by their deployed assets (source: Hyperliquid Docs, Fees). Up to 50 percent is a ceiling those deployers may set on their own markets, and that ceiling leaves the rest of the community split with HLP and the fund, with no 97 percent figure on the fees page. A crypto.news feature writes that the assistance fund uses 97% of protocol trading fees to buy HYPE tokens directly from the open market (source: crypto.news, Why HYPE is different). Leave that percentage off a mechanism explainer. It is trade-press, and the live dollar totals beside it move, so a static page should not bake them.
What the HYPE token is names the burn as a sink. The remaining split is three named destinations, one system address, and no invented remainder math to match a headline.
How conversion and burn work
Fees that reach the assistance fund are converted to HYPE as part of layer-1 execution and then burned, which removes those coins from circulating supply and from total supply.
The convert step is automated inside execution, with no wait on a discretionary operator or on a claim you file. The fees page states that conversion happens in a fully automated manner as part of L1 execution, and that HYPE in the assistance fund is burned, permanently from circulating and total. That pair is the project's own account of the destination, with no outsider audit of every fee dollar this week and no live burn dashboard.
Suppose you watch a burn headline and still hold 200 HYPE in the same wallet. A smaller total somewhere else leaves that wallet unchanged, so you can feel richer from the headline and still hold the same 200 HYPE.
Giants Labs still models the purchased balance as held, which is useful as a warning about third-party float math and a poor substitute for the fees page. If a model needs coins sitting in a treasury so they can later become insurance, it is modeling a different destination than the fees-page burn that removes tokens permanently from circulating and total supply. Those two accounts should not be reconciled by inventing a share, so the official verb stays burned.
A burn from total supply is a stronger supply cut than a circulating-only reduction, and it is still no deflation guarantee. Fees can fall, and deployer keeps can rise toward their cap on some markets. Aligned-quote yield is a separate inbound, covered next. None of that licenses a forecast that HYPE must grind up because the fund exists. HYPE tokenomics is where genesis buckets and the emissions reserve are structured. An assistance-fund explainer should not publish a current burn total that would be stale tomorrow.
Ethereum's fee-burn comparative sits on Ethereum ultrasound money if you want the ETH version of base fees leaving the stock. Hyperliquid's assistance-fund path is a HyperCore fee convert into HYPE, a different mechanism from EIP-1559, Ethereum's base-fee burn, and mixing the two is how a gas-burn story gets pasted onto 0xfefe.
Other HYPE burns on Hyperliquid
Hyperliquid burns HYPE in more than one place. Treating every burned coin as an assistance-fund event is how value goes to the wrong address, or how HIP-3 deployer slashing gets read as a rebate after a bad fill in a builder-deployed market.
HyperEVM gas is one neighbor, and HyperEVM is the general-purpose EVM half of the same chain. Base fees are burned in the usual EIP-1559 way, and priority fees are burned too because HyperEVM sits on HyperBFT, Hyperliquid's consensus. The burned priority fees are sent to the zero address's EVM balance (source: Hyperliquid Docs, HyperEVM for developers). That zero address is a different string from 0xfefefefefefefefefefefefefefefefefefefefe, so a HyperEVM send that you think is helping the buyback is gas accounting: it leaves the assistance fund untouched and opens no insurance file.
HIP-3 deployer slashing is the other neighbor. When validators slash a listing lockup, those coins stay a stake-layer penalty. "Relatedly, the slashed stake by the deployer is burned instead of being distributed to affected users." (source: Hyperliquid Docs, HIP-3) A trader who lost money in a builder market gets no compensation from that slash, which is a different path from the fee convert at the assistance-fund address.
Write the destination first. Assistance-fund HYPE is burned after a fee convert at 0xfefe, HyperEVM priority fees are burned onto the EVM zero address, and HIP-3 slashed deployer stake is burned with those coins staying off user wallets in that market. Three verbs, three destinations. A CEX treasury that buys its own token on a schedule is a fourth kind of buyback, and it is a different design from this protocol's system address.
How centralized and decentralized exchanges differ still helps if you are sorting a venue treasury versus an onchain destination, but it will not identify which Hyperliquid burn you are looking at. Name the address, or name the slash, before you name the headline.
How aligned-quote yield reaches the fund
Aligned-quote reserve yield can also be sent to the assistance fund on a 30-day interval. Aligned quote assets are quote assets the protocol treats as aligned, and that yield is a second inbound into the same destination, sitting beside converting trading fees as layer-1 execution on HyperCore, still with no coupon you can cash.
AQAv2 share is yield on Hyperliquid supply, a separate inbound from a trading-fee coupon, with no knob that cuts your taker rate. The official spec starts that interval at activation. The 30 day intervals begin on the date of activation (source: Hyperliquid Docs, Aligned quote assets). Later settlement examples on that page, including a February 7 UTC pay, are interval arithmetic for that yield stream: they leave the fee convert running, publish no 97 percent, and open no CEX claim. Reserve yield is automatically sent to the assistance fund 8 days after each interval completes. The burn question only needs the destination: same assistance fund, different inbound. The 8-day lag after each interval is a protocol payment into the fund, walked in more detail on the aligned quote assets explainer.
Suppose you read an interest payment dated February 7 and treat it as the day the buyback starts. The activation interval is older than that date. February 7 in the spec is when one 30-day UTC-date interval settles into the fund, eight days after the interval completes. Trading fees can still convert as L1 execution on every native fill, including on days besides February 7. Two inbounds can share an address without sharing a schedule, and neither inbound opens a withdrawal button.
USDH sunset headlines, 500k AQA stakes, and 9:1 treasury splits are quote-asset mechanics, so the burn question is narrower: yield that the spec sends to the fund is still no airdrop, and it is still no CEX insurance.
How BloFin HYPE fills relate to this path
A HYPEUSDT fill on BloFin is a USDT-margined centralized-exchange perpetual. That fill leaves Hyperliquid's assistance fund untouched, and the fund pays you nothing when native protocol fees convert to HYPE on HyperCore.
The public SWAP book on August 21, 2026 still returns a live HYPE-USDT instrument ID, max 75x, listed December 19, 2024 11:30 UTC, settle currency USDT, plus a separate HYPER-USDT row at 50x listed April 22, 2025 13:15 UTC (source: BloFin, SWAP instruments). Those hyphenated strings are the API keys, and reader names are HYPEUSDT and HYPERUSDT. A BloFin maker rebate, if you earn one, is this venue's schedule, off 0xfefe.
Spot on the same venue is a different product surface. The public SPOT book on the same date still returns HYPE-USDT with minSize 0.001, listed May 30, 2025 13:30 UTC, and HYPER-USDT with minSize 0.1, listed April 23, 2025 14:00 UTC (source: BloFin, SPOT instruments). Reader names on spot are HYPE/USDT and HYPER/USDT. HYPE/USDT here stays in BloFin custody until you withdraw it. HYPER on either board is Hyperlane, a name collision, not a second assistance fund.
Hyperliquid remains a competing venue with its own book. If you wanted the native fee path, you needed a HyperCore fill, not a USDT-margined SWAP that stays off that address. Crypto security basics still apply to whichever venue you pick. They will not move a CEX fill into the burn destination.
How to read the assistance fund
Name the destination before the headline. A system address that converts and burns is a different product from an airdrop, from CEX insurance, and from HLP inventory. Decide which of those you actually wanted before you treat a buyback percentage as a product you own.
Protocol fees have three named destinations, and the assistance fund is the convert-and-burn address. HLP takes a fee slice and inventory risk, and deployers may keep up to 50 percent on their listed assets. HyperEVM gas burns and HIP-3 slash burns are neighbors. A BloFin HYPEUSDT market is a fourth instrument that stays off the native path. You can use that map without a live burn total, and a total published today would be the wrong artifact for a static explainer. Search will keep publishing a percentage. The fees page will keep naming an address. Write which of those two you are looking at before you treat the fund as a product.
If the next question is supply buckets, read HYPE tokenomics. If the next question is whether delegated stake is a burn rebate, HYPE staking is a 7-day queue and an emissions reserve.
Generic what staking is will not sort that queue. Genesis dates and the DEX-to-L1 path sit in Hyperliquid history and genesis.
ETH supply mechanics that are a comparative, not this address, remain on ETH tokenomics.
Write the destination on a note before you search the ticker. Search will sell a safety net, and the fees page will sell an address.
Frequently asked questions
If I send HYPE from spot to 0xfefe, does that count as the protocol convert-and-burn?
No. Protocol trading fees convert to HYPE as layer-1 execution, then burn. That step is automated inside execution. Sending coins from your spot balance to the system address is a transfer you made, and the fees page names trading fees as the inbound. It is also a different path from HyperEVM priority-fee burns, which land on the EVM zero address. A self-send is a loss risk.
Do protocol fees from a HyperCore sub-account skip the assistance fund because vault volume is treated separately?
No. Sub-account volume counts toward the master account, and all sub-accounts share the same fee tier. That rule ranks you on the schedule. Vault volume is treated separately from the master account, which is a different ledger. Neither rule stops protocol fees that reach the assistance fund from converting as layer-1 execution and burning. Opening a sub-account adds no second claims form, and a vault deposit leaves the fund's convert in place.
Does the 8-day aligned-quote settlement lag mean I can withdraw from the fund on day 9?
No. After each 30-day interval completes, reserve yield is sent into the assistance fund eight days later. That is a payment into the fund. Day 9 leaves 0xfefe closed and mints no airdrop. The 4-day lockup after an HLP deposit is a vault-share rule on a different destination. If the yield stream skipped a cycle, the system address would still have no claims form.
If I send HYPE to the HyperEVM zero address, does that count as an assistance-fund burn?
No. HyperEVM priority-fee burns land on the EVM zero address as gas accounting. The assistance fund sits at 0xfefe. Sending coins to zero adds none of them to the assistance fund and creates no insurance claim. If the goal was the fee convert, a HyperCore protocol fee is the inbound the fees page names. A self-send to zero is a loss.
If I hold enough HYPE to reach a staking fee discount, have I already received my share of the burn?
No. A staking tier cuts the HyperCore trading fee you pay once the stake threshold applies. That discount comes from the published staking table, not from coins already removed from total supply. Delegated staking rewards come from the emissions reserve, and transfers from the staking account back to spot wait in a 7-day queue. A lower taker rate after a stake threshold leaves burned HYPE out of the same wallet.
If HYPE is burned from total supply, does that rewrite the one-billion max cap in tokenomics?
No. A burn that removes coins from circulating and total supply shrinks the live stock. That shrink, by itself, leaves the genesis max-supply figure of 1,000,000,000 HYPE in place as the official cap. How genesis buckets, remaining unminted coins, and the emissions reserve are structured belongs on the tokenomics page. Treat a smaller total as a smaller total. Read a changed ceiling only if that page says the cap moved.
If I withdraw HYPE from BloFin onto HyperCore, do my earlier HYPEUSDT SWAP fills retroactively feed the assistance fund?
No. A USDT-margined SWAP fill already settled on BloFin and left 0xfefe untouched. Withdrawing later and trading native starts a new HyperCore fee path. Old CEX fills stay off the protocol-fee path, and the withdraw creates no delayed assistance-fund credit. HYPERUSDT on the same board is still Hyperlane. Native fills after the withdraw can feed the convert. Past BloFin fills cannot.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Primary sources include Hyperliquid Docs (fees, protocol vaults, HyperEVM, HIP-3, aligned quote assets), BSCN's burn-vote write-up, and BloFin's public SWAP instrument API. Independent pages that publish 97 percent or call the fund insurance are cited as published readings, not as protocol constants. All 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 failure, smart-contract and validator risk, and the chance of losing funds. Nothing here is a recommendation to buy, sell, hold, stake, or claim any assistance-fund payout. Do your own research, and consider speaking with a licensed professional before making financial decisions. BloFin does not provide investment advice.