{"id":14660,"date":"2026-10-19T16:10:48","date_gmt":"2026-10-19T16:10:48","guid":{"rendered":"https:\/\/cryptonews.uk.com\/?p=14660"},"modified":"2026-10-19T16:10:48","modified_gmt":"2026-10-19T16:10:48","slug":"aave-usat-gateway-would-require-approval-to-swap-back","status":"publish","type":"post","link":"https:\/\/cryptonews.uk.com\/?p=14660","title":{"rendered":"Aave USAT gateway would require approval to swap back"},"content":{"rendered":"

<\/p>\n

\n

Aave\u2019s proposed USAT gateway would require approval for every return swap, allowing access to be revoked after an institution had exchanged its deposit receipts for GHO.<\/p>\n

TokenLogic\u2019s Oct. 15 governance proposal would introduce a permissioned GHO Stability Module, or GSM, on Avalanche. It would let approved counterparties exchange waUSAT, a receipt for the dollar stablecoin USAT supplied to Aave V4, for GHO. Approval would apply in both directions, so revocation could prevent a participant from returning GHO to recover waUSAT.<\/p>\n

That creates three separate conditions on the route back to dollars: access to the return swap, the ability to withdraw underlying USAT from lending, and eligibility to redeem USAT with its issuer, Anchorage Digital Bank.<\/p>\n

As of Oct. 18, the public proposal still describes a Snapshot vote followed, if approved, by an implementation proposal as its next steps. Important addresses and contracts remain unspecified.<\/p>\n

The proposed entry route involves two transactions. An approved counterparty would supply USAT to Aave V4\u2019s Tokenization Spoke and receive waUSAT. It would then exchange those receipt tokens for GHO through the GSM, which would hold the waUSAT while the USAT remained supplied to Aave.<\/p>\n

The return swap would therefore recover a receipt token. It would not directly deliver USAT or dollars.<\/p>\n

The permission check would apply to the swap originator every time. TokenLogic explicitly says that revoking approval would prevent further swaps, including exchanges intended to recover previously deposited assets.<\/p>\n

An approved originator could name another recipient or have a relayer submit a valid signed swap. Neither would need separate participant approval, but those options would preserve the approval requirement on the originator.<\/p>\n

GHO received through the module would remain freely transferable. Aave\u2019s GHO documentation distinguishes ordinary transfers from GSM conversions, so a participant whose module access was revoked could still transfer GHO.<\/p>\n

\"Proposed\"Proposed<\/p>\n

The proposal would also retain emergency controls. Freezing would halt exchanges; seizure would transfer module-held assets to the designated treasury and prevent further exchanges. Those powers are distinct from revoking an individual participant\u2019s approval. TokenLogic says restrictions on reversing a swap would need to be reflected in counterparty agreements.<\/p>\n

\n

Related Reading<\/span><\/p>\n

Native Bitcoin collateral on Aave triggers WBTC pool deficit<\/h3>\n<\/p>\n

<\/span> <\/div>\n

Shared inventory would determine what can come back<\/h2>\n

The initial whitelist would include a commercial counterparty and an Aave DAO Safe controlled by the Aave Finance Committee. Both would use the same liquidity and pricing. The module would not keep individual principal balances or require a participant\u2019s swaps to match its earlier deposits.<\/p>\n

Recovering waUSAT would leave a second step: obtaining the USAT represented by those shares. TokenLogic says that would depend on the selected integration and available liquidity. V4 withdrawals require a sufficient withdrawable amount and an unpaused reserve. The final USAT receipt-token integration remains unspecified.<\/p>\n