Repay Excess CRV Debt on Ethereum v2
01Summary
Aave will deploy a swap contract to acquire 2,700,000 CRV tokens using aUSDC holdings from the Ethereum Collector Contract to repay approximately 2,677,749 units of excessive debt in the CRV Reserve on Aave v2 Ethereum. Budget approved: 3,105,000 aUSDC with a price ceiling of $1.15 per CRV.
- Type
- protocol addition
- Funding
- $3105000
Key changes
- Deploy swap contract to exchange aUSDC for CRV with budget cap of 3,105,000 aUSDC(high)
- Acquire 2,700,000 CRV units at maximum price of $1.15 per unit via ParaSwap(high)
- Repay 2,677,749 units of excessive CRV debt in the Ethereum v2 CRV Reserve(high)
- Deposit 0.36M USDC from Collector Contract into Aave v2(medium)
- Apply 10 basis point premium to CRV/USD Chainlink Oracle price for swap execution(medium)
Notable concerns
- Price ceiling of $1.15 is 19.79% above spot price at time of proposal
- Swap contract allows any actor to deposit CRV and receive aUSDC, creating counterparty exposure
- Reliance on ParaSwap for execution with estimated transaction costs of $12-$15
Generated by Kvorum
02Description
Simple Summary
This AIP will procure CRV with aUSDC from the Collector Contract for the purpose of repaying the excess debt in the CRV Reserve on the Ethereum v2 liquidity pool.
Abstract
There are approximately 2,677,749 units of CRV of excessive debt in the Ethereum v2 CRV Reserve. At 96.0 cents per unit, a total of 2,570,639.04 USD, in the form of CRV tokens, is required to recapitalise the protocol.
To recapitalise the protocol, this proposal will acquire enough CRV to repay the excess debt, plus a buffer. This proposal will complete the acquisition from the existing aUSDC holdings. A total of 2,700,000 units of CRV will be procured, with an approved budget of 3,105,000 units of aUSDC. A price ceiling of $1.15 per unit of CRV has been set in the contract.
Aave currently holds 5.26M units of aUSDC in the Ethereum Collector Contract and a further 0.36M units of USDC which will be deposited into Aave v2.
Motivation
There is currently around 2,677,749 units of excessive debt in the CRV Reserve on the Ethereum v2 deployment. As the excess debt is nominated in CRV tokens, the excessive debt must be repaid in CRV.
This proposal follows on from the community discussion, linked here, whereby the community decided to use the aUSDC and USDC holding to acquire the CRV required to repay the excessive debt.
Holdings Summary Table
Holding $ Value % of Excessive Debt aUSDC 5,255,944.02 204.46 USDC 359,693.90 13.99 Excessive Debt 2,570,639.04 100 The table shows there is in total 218.45% more aUSDC and USDC relative to the excessive debt value in the Ethereum Collector Contract, ethereum:0x464C71f6c2F760DdA6093dCB91C24c39e5d6e18c.
Specification
Deposit the USDC held in the Ethereum Collector Contract and use the aUSDC holding to acquire 2,700,000 units of CRV via a swap contract. A 10 bps premium to the CRV/USD Chainlink Oracle is to be applied.
CRV/USD Oracle: 0xCd627aA160A6fA45Eb793D19Ef54f5062F20f33f
Estimated Premium: 2,570,639.04 * 0.0010 = $2,570.64 A $15,000 swap via ParaSwap at 14 gwei + depositing into the swap contract is estimated to cost $12 - $15, 10 bps is $15.
A cap of $3,105,000 will be placed on swap contract. This is a defined ceiling which limits the amount of funds allocated for acquiring CRV on market. A price cap of $1.15 has also been set within the contract. The $1.15 ceiling is 19.79% higher than the spot price.
Any actor interacting with the swap contract will have the ability to deposit CRV and receive aUSDC.
Implementation
Deploy a swap contract exchanging aUSDC for CRV with an approved budget of 3,105,000 units of aUSDC.
To repay the excess debt, the repay function will be used. This function requires CRV as an input and the address the bad debt has accumulated within.
pool.repay(crv, total bad debt, variableInterest, Address)
CRV: ethereum:0xD533a949740bb3306d119CC777fa900bA034cd52 Total Excessive Debt: 2,570,639.04 units of CRV Address: 0x57e04786e231af3343562c062e0d058f25dace9e
Test cases can be found here
Payload Implementation can be found [here](
Proposal Payload = 0xaa7ef2f9b31fa26e802ca9b3e33990ada4143fb9
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The decoded calldata consists of a single action: a call to execute() on the contract address 0xaa7ef2f9b31fa26e802ca9b3e33990ada4143fb9. This address matches exactly the 'Proposal Payload' address cited in the description's Implementation section. This is the standard Aave governance pattern where a single payload contract encapsulates all the granular logic (deploying the swap contract, depositing USDC, setting price ceilings, calling pool.repay, etc.) described in the prose. Because the on-chain action is just a generic execute() call, the actual internal logic (swap contract deployment, repay parameters, price ceiling, budget cap) cannot be independently verified from the calldata alone — it is bundled inside the target contract's bytecode, which is not decoded here. Given that the only verifiable data point (target address) matches the description precisely, there is no evidence of a target mismatch, omitted action, or value discrepancy. However, since the calldata itself carries no parameter-level detail, confidence in a full line-by-line comparison against the described repay amount, price cap, and premium is inherently low. No contradictions were found between what is decoded and what is claimed, so the proposal is assessed as consistent, with low confidence due to the opacity of the delegated call structure.
Generated by Kvorum
04Actions
- Target
- 0xaa7e…3fb9
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
- [ARFC] Repay Excess CRV Debt on Ethereum v2 ↗discourse · medium confidence
Arguments for
- Aave should use existing USDC/aUSDC holdings (which vastly exceed the excess debt) to acquire CRV and repay the bad debt, preserving the strategic aCRV position for future yield/veCRV potential.— Llamaxyz
- The community's intention to repay the excess debt has been clear and the DAO should proceed to AIP stage without further delay to avoid the debt widening as CRV price rises.— MarcZeller
- The revised swap contract (raising budget to $3,105,000 with a $1.15 price cap) successfully cleared the remaining excess debt quickly and efficiently once executed.— MarcZeller, Llamaxyz
Arguments against
- The community should reconsider using the aCRV holdings (or a streaming mechanism using aCRV income) to close the bad debt rather than further depleting stablecoin reserves.— bgdlabs
- Raising the USDC spend cap to chase a rising CRV price effectively de-capitalizes the protocol and is concerning from a treasury health perspective.— bgdlabs
- The swap contract model is problematic because caps/limits can easily go out of control in a volatile USDC/CRV market, especially combined with proposal timing delays.— bgdlabs, Llamaxyz
- The DAO's current heavy reliance on approved stablecoin streams is unsustainable and focus should shift to revenue and cost-cutting to avoid being forced to sell strategic assets.— MarcZeller
Unresolved concerns
- Llama's delay between the Snapshot vote and PR submission (roughly a month) allowed CRV price to rise, costing the DAO an estimated extra $1M, and raised questions of accountability and communication.— float, fig
- It was unclear whether a material change to the proposal (raising the budget cap) required a new Snapshot vote or could proceed directly to AIP, creating governance process ambiguity.— Llamaxyz, MarcZeller
- No mitigation existed for the scenario where the swap order goes unfilled and CRV debt grows to exceed the approved budget without CRV itself exceeding the price cap.— Llamaxyz
- Whether to build a more complex streaming/discounting mechanism using aCRV income (potentially requiring Certora audit and added delay) versus a faster swap-based solution was never fully settled.— bgdlabs, Llamaxyz
- Evaluating the swap using non-USDC stablecoin assets with more historical correlation to CRV to reduce price exposure was suggested but not adopted or further discussed.— bgdlabs
Notable participants
- LlamaxyzProposal author who designed the swap contract mechanism, managed revisions to the budget/price cap, and provided a detailed timeline defending the team's execution process.
- MarcZellerACI representative who pushed for rapid execution to stop the debt from widening and later confirmed successful execution of the contract.
- bgdlabsTechnical reviewer who raised concerns about the swap model's volatility risk, de-capitalization, and suggested alternative aCRV-based solutions.
- figCommunity member who questioned the delay between Snapshot approval and execution and its cost to the DAO.
- floatCritical voice holding Llama accountable for the execution delay and its financial impact, calling for review of Llama's treasury management KPIs.
Generated by Kvorum
08Similar proposals
- aaveexecutedAdd CRV to Ethereum v377%
- aaveexecutedaCRV OTC Deal76%
- aaveexecutedTransfer all CRV positions from Ethereum Mainnet Collector to GLC Safe74%
- aaveexecutedAIP 5: Adding CRV to Aave70%
- aaveexecutedReduce CRV LT by 6%68%
- aaveexecutedCRV Aave V2 Ethereum LT Reduction68%
- aaveexecutedDisable CRV Borrowing For Ethereum and Polygon V368%
- aavecanceledChaos Labs Risk Parameter Updates - CRV Aave V2 Ethereum67%
- aaveexecutedCRV Aave V2 Ethereum - LT Reduction67%
- aaveexecutedChaos Labs Risk Parameter Updates - CRV Aave V2 Ethereum66%