Aave V4 Proposal Would Sweep Idle USDC Into Circle Gateway via LiquidityBufferController
Key Takeaways
- •The ARFC proposal would deploy a LiquidityBufferController on the USDC reserve of Aave V4's Ethereum Core Hub to sweep surplus idle liquidity into Circle Gateway, a Circle-operated product that accepts USDC deposits and returns yield.
- •Proposed safeguards include a 9% liquid buffer target, a 5% floor that triggers automatic recalls from Circle Gateway, and total exposure capped at 10,000,000 USDC or 25% of supply, whichever is lower.
- •A historical simulation spanning August through November 2026 recorded 21 sweeps and 20 recalls with zero reverted transactions, while a crossing test produced a 0.46% floor-breach failure rate, below the proposal's 0.5% acceptability threshold.
- •The proposal cites an estimated $6 billion in idle stablecoin deposits across Aave V4, representing approximately 30% of its roughly $20 billion deposit base.
- •The measure has not been approved and must pass a Snapshot vote and an on-chain AIP before any sweeps go live, with the authors having announced no timeline for either step.

TokenLogic, in collaboration with Aave Labs, posted a governance proposal on November 20, 2026 to deploy a LiquidityBufferController on the USDC reserve of the Aave V4 Ethereum Core Hub, enabling automated sweeps of idle USDC into Circle Gateway. The proposal, published on Aave's governance forum, sits at the ARFC (Aave Request for Comment) stage and has not been approved. It would need to pass a Snapshot vote and an on-chain AIP before any sweeps go live, and the authors have announced no timeline for either step.
Key Details
- The proposal would activate LiquidityBufferController sweeps on the V4 Ethereum Core Hub USDC reserve, routing idle capital into Circle Gateway.
- Exposure would be capped at 10,000,000 USDC, with a liquid buffer target of 9% and a floor of 5% designed to protect borrower withdrawals.
- The measure remains a proposal, not a confirmed implementation: the ARFC stage requires community feedback, a Snapshot vote and a final AIP before any on-chain execution.
Stated Objective: Putting Idle USDC to Work
The ARFC proposes activating a LiquidityBufferController that would detect when idle USDC exceeds a defined buffer target and automatically sweep the surplus into Circle Gateway. According to the Aave V4 reinvestment module design, the broader V4 architecture was built with this kind of buffer management in mind. The proposal cites an estimated $6 billion in idle stablecoin deposits across Aave V4 out of roughly $20 billion in total — approximately 30% of the deposit base — a substantial pool of capital that currently generates no return for the protocol. As context on this theme, Defiliban's US session roundup previously reported Aave V4 deposits above $1.75 billion.
How LiquidityBufferController Sweeps Would Work
The controller operates against two thresholds. The liquid buffer target is set at 900 basis points — 9% of supply — meaning the reserve would always retain at least that fraction on-chain to meet borrower demand. The buffer floor sits at 500 basis points, or 5%; if on-chain liquidity drops to that level, the controller triggers a recall from Circle Gateway to replenish the buffer.
A keeper bot handles both sweep and recall execution autonomously, without requiring manual intervention each cycle. Circle Gateway's sequential withdrawal constraint is a key operational consideration here: recall frequency is limited by that sequencing, which is why the keeper bot is designed to recall proactively once liquidity approaches the floor, rather than waiting for an actual shortfall.
Controller and Keeper Risks
The proposed automation introduces controller and keeper-execution dependencies in addition to Circle counterparty risk. Its operation depends on correct authorization of sweep and recall calls, reliable keeper execution and the behavior of any controller upgrades. The proposal description does not detail these controls, nor the outcome if a recall fails or is delayed. It also does not state whether oracle, bridge or liquidation pathways are involved in the sweep-and-recall process. Based on the disclosed parameters, these operational details are a key unresolved consideration for governance review.
The proposal sets an absolute exposure cap of 10,000,000 USDC and an exposureCapBps of 2,500 (25% of supply), with the lower of the two applying at any given time. This hard ceiling limits Aave's total counterparty exposure to Circle Gateway regardless of how large the reserve grows. The proposal notes that Circle Gateway redemptions are designed to be near-instant and 1:1 for USDC, though this characteristic is stated in the proposal itself and has not been independently verified.
Circle Gateway's Role in the Yield Loop
According to the proposal, Circle Gateway is a Circle-operated product that accepts USDC deposits and returns yield. The proposal does not state a yield rate, observation period or calculation basis. It also emphasizes that counterparty risk is limited to existing Circle issuer exposure — Circle being the issuer of USDC itself — introducing no new credit risk beyond what any USDC holder already carries.
Risk Parameters and Historical Stress Testing
The proposal includes a historical simulation covering August through November 2026 that recorded 21 sweeps and 20 recalls, with zero reverted transactions across the test window. A crossing test, which measures how often on-chain liquidity would breach the 5% buffer floor, produced a failure rate of 0.46% — below the 0.5% threshold the proposal targets as acceptable.
The 99.5th percentile worst-case 30-minute net outflow from the reserve is modeled at 6.1% of supply, per the governance post. A 6.1% net outflow from a 9% on-chain buffer would leave 2.9%, crossing the stated 5% floor and triggering a Circle Gateway recall under the described parameters. The proposal does not document a different liquidity basis that would avoid this trigger.
How Governance Review and Implementation Could Proceed
The proposal is at the ARFC stage, the first formal step in Aave's governance process. Community members can comment and suggest amendments directly on the governance forum before the proposal advances. If sentiment is positive, the authors would submit a Snapshot vote for off-chain signaling, followed by an on-chain AIP that, if passed, executes the deployment automatically through Aave's governance executor contracts.
Aave's governance has been processing a range of V4-era parameter and integration proposals in this window. The DAO recently reviewed proposals targeting Coinbase tokenized equities on Base, illustrating the breadth of integration work moving through the ARFC pipeline simultaneously. The LiquidityBufferController ARFC competes for governance attention in that same queue.
Implementation Considerations and What to Watch
If the AIP passes, deployment would configure the LiquidityBufferController contract against the V4 Ethereum Core Hub USDC reserve with the parameters described above: a 9% buffer target, a 5% buffer floor and a 10 million USDC absolute cap. The keeper bot would then operate continuously, sweeping and recalling without additional governance action unless parameters need adjustment. Changes in Circle Gateway yield could affect expected returns and could prompt a follow-up governance action to revise the exposure cap or buffer thresholds.
Governance participants and USDC depositors on the V4 Core Hub should watch for the Snapshot vote announcement, the final AIP parameter set — which may differ from the ARFC draft — and any community comments that challenge the Circle Gateway counterparty risk framing. The 0.46% crossing-test failure rate is below threshold today, but if V4 Core Hub supply and utilization patterns shift materially, those parameters may warrant reassessment before the AIP is finalized.