Hyperliquid is expected to receive its first AQAv2 reserve revenue distribution tomorrow, according to a post on X by HL HUB (Community). The distribution involves about $14.5 million in passive income generated from USDC reserves, with the funds set to flow into the Assistance Fund for HYPE buybacks. Under AQAv2’s revenue-sharing model, stablecoin deployers on Hyperliquid are required to allocate 90% of reserve income to the protocol. Those proceeds are then used entirely to buy back and burn HYPE tokens. The reserve revenue is accrued and settled on a 30-day cycle, and transfers are made automatically to the Assistance Fund on the eighth day after each cycle ends. Formal revenue accrual began on Aug. 26, putting the first payout on Oct. 3.
Hyperliquid is expected to receive its first AQAv2 reserve revenue distribution tomorrow, according to a post on X by HL HUB (Community).
About $14.5 million in passive income generated from USDC reserves will be transferred to the Assistance Fund and used to buy back HYPE.
AQAv2 revenue-sharing structure
Under AQAv2’s revenue-sharing mechanism, stablecoin deployers on Hyperliquid are required to allocate 90% of stablecoin reserve income to the Hyperliquid protocol. Those proceeds are then used in full to buy back and burn HYPE tokens.
Reserve revenue from the stablecoin side is accrued and settled on a 30-day cycle. The proceeds are automatically transferred to the Assistance Fund on the eighth day after the cycle ends. Formal revenue accrual began on Aug. 26, which puts the first payout on Oct. 3.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
