Aave Labs has proposed adding USAT to Aave V4’s Core instance on Avalanche. The 19 October post follows the Direct to AIP route and leaves risk parameters and final configuration to service providers before a governance vote.

The proposal identifies an Avalanche token contract, but that address alone establishes neither approval nor a functioning lending market. Aave Labs describes USAT as issued by Anchorage Digital Bank and says it received no compensation from the issuer, Tether or their affiliates for preparing the proposal.

A separate route from lending receipts to GHO

A 15 October TokenLogic proposal would create a permissioned GHO Stability Module on Avalanche. Approved counterparties would supply USAT to an Aave V4 Tokenization Spoke, receive waUSAT receipts and exchange those receipts for GHO through the module.

The proposed module would hold waUSAT rather than the underlying USAT. Recovering USAT would require the receipt-token redemption route and enough available liquidity. GHO obtained from the module would remain transferable.

Permission can constrain the way back

TokenLogic says permission checks would apply to the person initiating a swap in either direction. Revoking approval could therefore prevent a counterparty from exchanging GHO back for waUSAT. Freezing or insufficient liquidity could also obstruct reversal; a seizure control would transfer module assets to a designated treasury and stop exchanges.

The draft proposes 65 million GHO of initial reserve funding, a 25 million GHO draw limit and a 20 million waUSAT exposure cap. These describe different limits: the funding amount is not an individual participant’s guaranteed withdrawal capacity. Liquidity would be shared rather than reserved for each depositor.

Several configuration fields remain unresolved, including the receipt-token address, pricing strategy and possible automatic-freeze strategy. The draft says it would proceed through community feedback, Snapshot and then an implementation proposal if approved.

NetNapz assessment

The useful test is whether the final configuration explains how a counterparty exits during stress. A lending receipt introduces one redemption step, while participant approval and shared liquidity add further conditions. Those dependencies deserve explicit treatment in counterparty agreements and operational procedures.

The proposals may broaden Aave’s stablecoin infrastructure, but their publication supplies no evidence of completed deployment, institutional borrowing volume or additional AAVE-token demand.

Verification limits

NetNapz checked both governance discussions on 22 October 2026. Final approval, execution and live usage were not independently verified. The USAT onboarding and permissioned module are separate proposals; one should not be read as proof the other is implemented.

Related: Aave’s separate USDe Avalanche vote. USDe and USAT are distinct assets with different structures.