Welcome to the next crypto level
← Nexorena

Marchés

Aave puts an Avalanche USAT-to-GHO exchange module to a vote

The November 15–18 signaling vote concerns a module limited to approved counterparties. The proposal calls for an initial reserve of 65 million GHO and a separate draw limit.

Nexorena Editorial Team

Aave puts an Avalanche USAT-to-GHO exchange module to a vote

A signaling vote comes before deployment

The Snapshot schedule sets November 15–18, 2026, for an Aave DAO signaling vote on a GHO stability module restricted to certain counterparties. TokenLogic proposes an initial use on Avalanche involving USAT, a dollar stablecoin issued by Anchorage Digital Bank. Participants will weigh in on the design and parameters. If the vote passes, TokenLogic plans to submit an implementation proposal to governance.

The design separates depositing the stablecoin from exchanging it for GHO. An approved counterparty would deposit USAT into the Aave V4 tokenization spoke and receive waCoreUSAT, tokens representing that deposit. It could then give those tokens to the module in exchange for GHO. In the other direction, the module would return waCoreUSAT in exchange for GHO. Withdrawal of the underlying USAT would depend on the chosen integration and available liquidity.

Three limits serve different purposes

TokenLogic proposes minting 65 million GHO on Ethereum and transferring the allocation to Avalanche to fund the reserve. Under its initial settings, the module could draw only 25 million GHO from that reserve. A third figure, 20 million waCoreUSAT, would cap the module’s exposure in deposit tokens. The reserve size, draw limit, and exposure cap apply to different operations.

Swaps would use a shared pool. The proposal provides for neither an individual principal balance nor liquidity set aside for each counterparty. A participant’s initial deposit would therefore provide no guarantee that tokens would be available for a reverse swap. Both swap directions would initially carry zero fees. The proposal says charging a positive fee would require another governance decision.

Separate permissions for each direction

The initial allowlist would include only an Aave DAO multisignature wallet managed by its finance committee, with permission in both directions. The GHO Risk Council could approve the commercial counterparty later. An address could be granted access in one direction or both, or have it revoked. GHO obtained through the module would remain freely transferable. The proposal would also let a depositor name another recipient or use a relayer to submit a signed order. The access check would apply to the address initiating the swap. Neither the recipient nor the relayer would need to be on the allowlist.

Permission to swap and available liquidity remain two conditions for exiting through the module. TokenLogic says revocation or a freeze could prevent a counterparty from reversing a swap. The proposal calls for those risks to be reflected in agreements between participants. The vote concerns this specific configuration on Avalanche. Existing permissionless stability modules would continue to operate under their own rules.

Article sources

Written with love byOlivia ParkerMeet this editorial pen name ↗

Explorer Nexorena