Key points

  • The first AQAv2 reserve-yield payment placed 14,580,777.21 USDC in Hyperliquid’s system interest address on October 3.
  • AQAv2 sends the vast majority of cost-adjusted reserve yield from USDC on Hyperliquid to the protocol on a recurring cycle.
  • The payment had not yet reached the Assistance Fund when independently checked, so it should not be described as completed HYPE purchases.

Hyperliquid recorded its first payment under the Aligned Quote Asset v2 framework on October 3, placing 14,580,777.21 USDC in the protocol’s system interest address. The transfer establishes a new source of protocol revenue linked to the reserves behind USDC held on Hyperliquid, rather than directly to trading fees. It does not, by itself, show that the full amount has already been used to buy HYPE.

What the first payment represents

Hyperliquid’s official announcement said reserve yield began accruing on August 26 and that the first payment was made on October 3. Independent reporting based on the network’s transaction record identified the amount as 14,580,777.21 USDC. At the time of that check, the funds were still in the interest-collection address and had not yet moved to the Assistance Fund, the protocol account that conducts HYPE purchases. The distinction matters because an allocated payment is not the same as a completed token buyback.

Related reporting: Hyperliquid adds manual borrowing against HYPE and BTC

How AQAv2 routes reserve income

AQAv2 allows a stablecoin that is not exclusive to Hyperliquid to qualify as an aligned quote asset. Under the specification, a treasury deployer designates an address that shares the onchain reference-rate revenue with the protocol, while a technical deployer manages minting, redemption and cross-chain infrastructure. Coinbase serves as the treasury deployer for USDC and Circle as the technical deployer. Each staked 500,000 HYPE to activate the arrangement.

A reserve-based revenue stream

The protocol says deployers share approximately 90% of cost-adjusted reserve yield on their Hyperliquid supply. Revenue accrues in 30-day intervals and is scheduled to move automatically to the Assistance Fund eight days after an interval closes. That makes the flow dependent on the amount of eligible USDC, the applicable reference rate and implementation costs. It is therefore different from trading-fee revenue, which rises and falls mainly with market activity on the venue.

Why the payment is notable

The inaugural transfer turns AQAv2 from a design described in May into an operating revenue mechanism. It also links a large dollar-backed asset to Hyperliquid’s token-supply process without requiring a new proprietary stablecoin. For users, the arrangement is intended to combine USDC liquidity with protocol alignment. For the protocol, it adds a potential recurring inflow that can continue even when trading volumes soften, although future payments may vary substantially with balances and interest rates.

The remaining caveats

Neither the first payment nor its annualized equivalent should be treated as guaranteed future revenue. USDC balances can change, the reference rate can move and the framework’s costs affect the amount shared. The protocol specification also includes slashable staking requirements intended to enforce sufficient treasury balances, but those safeguards do not remove smart-contract, operational or market risks. Any HYPE repurchases would also occur in the market over time rather than at a fixed token price.

What to watch next

The next verifiable step is the movement of the 14.58 million USDC from the system interest address to the Assistance Fund, followed by onchain evidence of purchases. Subsequent 30-day cycles will show whether the first amount is representative or was shaped by the launch period. Until then, the confirmed development is narrower: Hyperliquid has received its first AQAv2 reserve-yield payment, creating a second revenue channel for its buyback system, but the resulting token purchases were not yet complete when the transaction was reviewed.

Sources

AI-generated editorial image; not a photograph of the reported event. Prepared with AI assistance and source verification.