Recently, a significant buy order of approximately $50 million in AAVE on the Aave platform encountered severe slippage losses due to insufficient liquidity while being exchanged through the CoW Protocol. The user submitted the order via Aave's exchange interface, which routes through the CoW Protocol. The confirmation interface warned of serious slippage risks, yet the transaction was still executed on-chain.
As the order hit thin liquidity on the route, it caused a massive price impact, resulting in a substantial loss of value due to slippage. During the settlement process, block builders and MEV (Maximal Extractable Value) participants captured a considerable portion of the slippage profits.
This incident has raised concerns regarding the following issues:
- Solver Design and MEV Capture: Does the design of CoW Protocol's Solver adequately consider liquidity depth and potential MEV extraction when handling large transactions?
- Aave DAO Fee Revenue Controversy: According to estimates from CoinCatch Academy, routing fees could reach up to $200,000 weekly, which, if unaddressed, would have a significant annual impact. This figure highlights the contentious focus of Aave DAO's fee revenue distribution.
Direct Impact and Follow-up Measures:
- Fee Refunds: Fees associated with the problematic transaction are being processed for refunds, with publicly disclosed amounts around $600,000. However, the actual slippage losses incurred on-chain are irretrievable.
- Enhanced Slippage Protection: The Aave team is focusing on strengthening slippage protection mechanisms, including setting hard caps for large orders and default non-negotiable slippage limits. Additionally, they are reviewing other safety measures, such as Solver-side thresholds based on liquidity pool depth and routing feasibility.
- MEV Exposure and Revenue Routing Review: Community discussions also involve MEV risk exposure and the transparency of revenue routing. Some representatives are calling for independent audits of brand assets and front-end operations, as well as enhanced DAO oversight.
Safety Measures and Governance Improvements:
- MEV and Slippage Protection Proposals: This incident underscores the necessity of building multi-layered defense mechanisms to address extreme execution risks. Current proposals under discussion include enforced maximum slippage limits, liquidity pool depth checks, and restricting Solver routing to pools with extremely low liquidity.
- UI Warnings and Solver Safeguards: These improvements will complement existing MEV protection measures, aiming to prevent execution paths that could lead to excessive MEV extraction. By combining user interface warning prompts with Solver-side safeguard mechanisms, price impacts can be effectively constrained even when users attempt to accept high slippage.
- Revenue Routing Transparency and Product/Protocol Definitions: Aave Labs has proposed that the front-end interface and Swap Adapter are classified as “products,” while what the DAO manages is termed a “protocol,” to clarify the attribution of product revenues. Clearly defining on-chain routing will help delineate which fees belong to the DAO and which belong to the providers.
- Representative Demands: DAO representatives are seeking transparent, verifiable revenue paths and disclosures that can distinguish between commercial arrangements and governance-controlled economics. Clear categorization will help mitigate disputes and provide a basis for future funding negotiations.