0x2975fea82975…2975feab
Hyperliquid's First USDC Reserve-Yield Payment Lands at $14.6 Million
Hyperliquid's AQAv2 program delivered 14.58 million USDC in its first reserve-yield payment, funds that await transfer to the Assistance Fund for HYPE buybacks.

Outputs
Hyperliquid received its first AQAv2 reserve-yield payment of 14,580,777.21 USDC, confirmed by the protocol's on-chain explorer.
Coinbase acts as treasury deployer sharing reserve revenue; Circle is technical deployer handling minting, redemption and cross-chain infrastructure.
Payments accrue over 30-day intervals and reach the Assistance Fund eight days after each interval, where HYPE is bought and permanently burned.
Hyperliquid's USDC reserve-yield program has received its first payment of 14,580,777.21 USDC, opening a new funding stream for HYPE buybacks that operates independently of trading volume. On-chain records show the funds had not yet reached their final destination as of early Oct. 3 ET.
A transaction recorded by Hyperliquid's own explorer shows the 14.58 million USDC sent to the protocol's system interest address. Hypurrscan's account record for that address showed the balance still sitting there, alongside only an earlier 2 USDC transfer to the Assistance Fund. The payment therefore funded the collection stage rather than completed any HYPE purchases.
Ecosystem data provider HL Eco identified the transfer as the first month's payment under Hyperliquid's AQAv2 framework. "Funds are waiting to be transferred to the Assistance Fund to buy and effectively burn $HYPE," HL Eco wrote.
The mechanics matter for HYPE holders because they add reserve income to a buyback mechanism previously funded solely by trading fees. Under the AQAv2 rules, stablecoin deployers share approximately 90% of cost-adjusted reserve yield generated on their Hyperliquid supply with the protocol. The new funding stream scales with eligible stablecoin balances and the applicable yield rate, not trading turnover — a structural shift that decouples part of the buyback budget from exchange activity.
The arrangement divides responsibility between two named USDC operators. Hyperliquid identifies Coinbase as the treasury deployer sharing reserve revenue, while Circle serves as the technical deployer responsible for minting, redemption and cross-chain infrastructure. The USDC backing HyperCore balances is held on HyperEVM in a 9:1 split between the treasury address and the technical deployer's linked contract. The treasury address passes 100% of the AQA rate — a cost-adjusted on-chain reference rate — to the protocol. Revenue accrues over 30-day intervals and is scheduled to reach the Assistance Fund eight days after each interval closes.
Annualizing the first 30-day payment produces roughly $177.4 million, or about $486,000 per day, according to The Defiant's calculation. That projection assumes subsequent intervals generate identical proceeds; any change in eligible balances or the reference rate would move the outcome. At CoinGecko's HYPE price of $87.84 at 5:07 a.m. ET on Oct. 3, the annualized amount would purchase approximately 2 million HYPE — roughly 0.9% of the reported 222.45 million circulating tokens — before fees or market impact. That figure illustrates potential purchasing power at a constant price, not an executed burn.
The destination is the existing Assistance Fund rather than a newly created treasury. Hyperliquid's fee documentation states that the fund automatically converts trading fees into HYPE as part of blockchain execution, and that HYPE held in the fund is burned, permanently removing it from both circulating and total supply.
Operationally, the immediate next step is administrative: the 14.58 million USDC must move from the system interest address to the Assistance Fund before any buybacks occur. Under the protocol's schedule, subsequent AQAv2 payments should follow the same 30-day accrual cycle with an eight-day settlement lag, giving HYPE holders a recurring, balance-dependent supply-reduction mechanism alongside the fee-funded burn already embedded in Hyperliquid's execution layer.
via app.hyperliquid.xyz (Original)