Aave Labs proposed on 28 October granting approved-flash-borrower status to new CoW swap adapter factories. The objective is to remove the flash-loan premium from eligible routes used for collateral swaps, debt swaps, repayment with collateral and leverage.

A targeted permission change across V3 markets

The draft names two factory versions, AaveV3AdapterV3Factory and AaveV3AdapterV4Factory. Its market table covers Ethereum Core and Prime, Base, Arbitrum, Gnosis, Avalanche, BNB Chain, Polygon, Linea and Plasma. The proposed payload would register each listed factory through ACLManager.addFlashBorrower.

Although the forum title refers to V3/V4, the specification identifies Aave V3 deployments. Factory version names should not be read as proof of a separate V4 protocol rollout.

Aave Labs argues that removing this internal cost would improve routing competitiveness and keep more activity within Aave. That is the proposer’s expected benefit, not a measured improvement in execution prices or protocol revenue.

The waiver has a defined technical boundary

Aave’s access-control documentation describes approved flash borrowers as a role with a fee benefit. It is distinct from administrative roles that can change risk settings or list assets.

The official flash-loan guide says approved borrowers can receive a premium waiver through flashLoan(). It explicitly excludes flashLoanSimple() from that waiver. Repayment or the permitted creation of a debt position must still satisfy the transaction’s conditions; otherwise execution reverts.

Vote and execution remain ahead

The forum post says an AIP vote would follow community support, with execution conditional on passage. NetNapz verified no completed vote or executed permission change at publication.

NetNapz assessment

The distinction for users is between one component of a route’s cost and its final outcome. Removing an internal premium would not, by itself, establish a cheaper completed trade: gas, market liquidity and the price achieved during execution still matter. Comparing like-for-like transaction results would be more informative than assuming the proposal’s stated objective has already been delivered.

For governance reviewers, the next useful evidence is a final payload whose addresses and markets match the proposal, followed by an observable execution. This is separate from the pending V3.8 security proposal. Neither announcement establishes an AAVE token-price effect.

Verification limits

NetNapz checked the dated proposal and official permission and flash-loan documentation. No live transaction simulation, deployed-contract role inspection or independent code audit was performed. The existing credited conceptual photograph was reused; a fresh public image retrieval failed.