An Aave V4 proposal would send some idle USDC from its Ethereum Core Hub to Circle Gateway to earn yield. Each recall would be limited to 10 million USDC and consecutive recalls would be about 30 minutes apart. The reserve would have to cover demand between recalls using the USDC already on the Hub.
What the buffer would protect
TokenLogic recommends a 9 percent liquid buffer and a 5 percent floor. The higher figure is the target the controller tries to restore. The lower one triggers replenishment. Gateway exposure would face both a 10 million USDC fixed cap and a cap of 25 percent of supplied USDC.
Why utilization can miss an access constraint
The system would still count swept USDC as supplied liquidity when it computes utilization and borrowing rates. That amount would be available for borrowing or withdrawal only after it returns to the Hub. Users could therefore face a temporary gap between reported supply and funds the reserve can deliver.
What might delay a recall
The design normally relies on Circle attestations. The proposal describes an alternative withdrawal that takes around seven days if that service is unavailable. A governance decision and published deployment parameters would show whether these limits have been adopted.
Sources. Aave governance forum proposal by TokenLogic.
Illustrative photograph by Although via Wikimedia Commons. Image license.



