KVORUM
aaveSource: Aave governor v2 · #168

Add CRV to Ethereum v3

executedMar 7, 2023, 07:05 AM UTCby550x55b1…f262

01Summary

AISummary by Kvorumclaude-haiku-4-5

Proposal to add CRV (Curve DAO token) as a new asset to Aave v3 on Ethereum with borrowing and collateral enabled. This aims to restore CRV lending revenue that declined after v2 reserves were frozen, and allow users to migrate positions from v2 to v3. Risk parameters have been reviewed and endorsed by Gauntlet.

Type
protocol addition

Key changes

  • Add CRV token as a new asset to Aave v3 Ethereum with borrowing and collateral functionality enabled(high)
  • Set supply cap at 62.50M CRV and borrow cap at 7.70M CRV to manage risk(high)
  • Configure LTV at 55%, liquidation threshold at 61%, and liquidation bonus at 8.30%(high)
  • Establish interest rate curve with variable base 3%, slope1 14%, slope2 300%, and optimal utilization at 70%(medium)
  • Enable isolation mode with 20.90M debt ceiling and 20% reserve factor(medium)
  • Disable stable borrowing for CRV asset(low)

Notable concerns

  • CRV v2 reserves have been frozen, causing material revenue decline which this proposal aims to address
  • Future proposal required to determine how CRV earnings will be utilized by Aave treasury
Contracts0xD533a949740bb3306d119CC777fa900bA034cd520x5594475f068f814bdeb2d21b1676431a376322f50x76884cAFeCf1f7d4146DA6C4053B18B76bf6ED14
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

419 words

Summary

This proposal presents Aave the opportunity to onboard CRV to the Ethereum v3 Liquidity Pool.

Abstract

CRV is a strategic asset to Aave and any CRV earned from the pool could be used by Aave to support bootstrapping the adoption of GHO, StakedAToken and in the long term, perhaps help incentivize the Safety Module too.

The risk parameters provided within have been reviewed and endorsed by Gauntlet.

Motivation

Listing CRV on Aave v3 Ethereum compliments the community's recent on-market purchase of CRV to repay the excessive debt created on v2 Ethereum. CRV is a material contributor to Aave’s revenue through the continual borrowing demand for CRV. With serveral v2 CRV reserves being frozen, Month on Month revenue has fallen significantly in recently months.

The Polygon v3 deployment is the only liquidity pool with Borrowing enabled. The chart below shows how deposit rates on this deployment have been affect by the freezing and disabling borrowing on Polygon v2 and Ethereum v2 respectively during late November 2022.

By listing CRV on v3 Ethereum and with a suitable BorrowCap in place, users will have the ability to migrate there positions from v2 to v3.

Any CRV earned by Aave can be used in a number of different ways, with examples shown below:

  • Treasury yield
  • GHO adoption
  • StakedAToken adoption
  • Support Safety Module yield

How the CRV will be used is open for discuss and implementation via a separate proposal.

The risk parameters presented have been reviewed by Gauntlet and a supportive comment can be found on the forum.

The interest rate curve parameters have been sourced from Llama's ARFC CRV Interest Rate Curve Upgrade post and have also been reviewed by Gauntlet.

Specification

Ticker: CRV

Contract Address: 0xD533a949740bb3306d119CC777fa900bA034cd52

Risk ParameterValue
Isolation ModeYES
Enable BorrowYES
Enable CollateralYES
Loan To Value55.00%
Liquidation Threshold61.00%
Liquidation Bonus8.30%
Reserve Factor20.00%
Liquidation Protocol Fee10.00%
Borrow Cap7.70M
Supply Cap62.50M
Debt Ceiling20.90M
Variable Base3.00%
Variable Slope114.00%
Variable Slope2300.00%
Uoptimal70.00%
Stable BorrowingDisabled
Stable Slope18.00%
Stable Slope2300.00%
Base Stable Rate Offset3.00%
Stable Rate Excess Offset5.00%
Optimal Stable To Total Debt Ratio20.00%

Implementation

Test cases can be found here

Payload Implementation can be found here

Proposal Payload deployed address can be found here

Interest Rate Strategy deployed address can be found here

Security Considerations

The proposal Payload was reviewed by Bored Ghost Developing.

Governance Considerations

Aave governance forum discussion, Snapshot vote and Risk Service Provider feedback.

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The decoded calldata consists of a single top-level call: execute() on the payload contract at the exact address the description cites as the deployed Proposal Payload. This matches the standard Aave governance execution pattern, where the granular logic (listing CRV, setting LTV, liquidation threshold, caps, interest rate curve, etc.) is embedded inside the payload contract's own code rather than passed as calldata arguments to the governance executor. Because the decoded action list does not expose the internal parameter-setting calls, I cannot independently verify the specific numeric risk parameters (LTV 55%, LT 61%, caps, interest rate curve, etc.) against on-chain calldata — they are not visible in this decoded representation. The target address does match what the description claims, so there is no evidence of a target mismatch or malicious redirection. Given the lack of granular calldata to cross-check the many specific numbers in the specification table, confidence in a full parameter-by-parameter comparison is low, but nothing in the visible action contradicts the description, and the single action's target aligns with the stated payload address. Therefore I assess this as consistent with low confidence, since the proposal follows the expected pattern for Aave v3 listing proposals and no contradiction is observable at this level of decoding. Discrepancies list is empty because there is no evidence — only absence of visibility — into the granular actions; flagging omission here would be a false alarm given this is the routine/expected calldata shape for this proposal type.

Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

1 total
#0fallback()chain 0x1
Target
0x5594…22f5
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total
Filter:
VoterChoice% of totalRationale
320x329c…3ed4For222.5K0.00%—4y ago
070x0703…961bFor107.3K0.00%—4y ago
130x13bd…8548For80.6K0.00%—4y ago
B80xb83b…cf5cFor80.2K0.00%—4y ago
B90xb933…8dd1For41.7K0.00%—4y ago
EA0xea17…6676For10.6K0.00%—4y ago
5F0x5fa0…cfa8For499.90.00%—4y ago
580x58ac…a73dFor388.20.00%—4y ago
210x2155…59aaFor8.30.00%—4y ago
A00xa0ef…2d56For8.30.00%—4y ago
BE0xbeb9…f1d7For1.90.00%—4y ago
280x288b…b106For1.50.00%—4y ago
860x8655…6267For10.00%—4y ago
230x2368…e99dFor10.00%—4y ago
7E0x7eaf…3555For0.90.00%—4y ago
BF0xbf4c…5a7cFor0.80.00%—4y ago
880x8824…5443For0.50.00%—4y ago
100x10ae…a227For0.50.00%—4y ago
750x7513…9d55For0.50.00%—4y ago
770x772e…fd0dFor0.40.00%—4y ago
7A0x7a01…2c4bFor0.30.00%—4y ago
290x2946…5469For0.30.00%—4y ago
9B0x9b2a…9bf6For0.20.00%—4y ago
FF0xffc2…d86fFor0.20.00%—4y ago
F20xf2f4…fc57For0.20.00%—4y ago
CF0xcfdd…cbc5For0.20.00%—4y ago
380x3886…c84bFor0.20.00%—4y ago
F80xf87c…a0e6For0.20.00%—4y ago
8C0x8ccf…c275For0.10.00%—4y ago
890x8952…7450Against0.10.00%—4y ago
980x98ab…ba24For0.10.00%—4y ago
770x77bb…ff85For0.10.00%—4y ago
E00xe032…c743For0.10.00%—4y ago
540x54c6…33b2For0.10.00%—4y ago
9A0x9a37…ea65For0.10.00%—4y ago
DB0xdb1a…38e2For00.00%—4y ago
050x059e…2744For00.00%—4y ago
260x26ba…6758For00.00%—4y ago
E40xe48a…597cFor00.00%—4y ago
Showing 39

07Forum

AIForum synthesis by Kvorumclaude-sonnet-5
sentiment · favorablethread · constructive

Arguments for

  • CRV is a strategic asset for Aave that could be used to bootstrap veCRV, aid GHO adoption, and potentially incentivize the Safety Module.— Llamaxyz
  • Listing CRV on v3 complements the community's recent repayment of excess CRV debt on v2 and restores revenue lost from disabling CRV borrowing on v2.— Llamaxyz
  • There is strong ongoing borrowing demand for CRV due to veTokenomics and the Convex/Curve ecosystem, so enabling borrowing on v3 with a suitable cap would generate revenue and let users migrate from v2.— Llamaxyz
  • The community should not worry about past Aave V3 risk parameter issues and should support this listing.— Rudy
  • The Aave Companies Initiative (ACI) is supportive of the proposal, pending final risk parameter recommendations from the risk teams.— MarcZeller

Arguments against

None surfaced.

Unresolved concerns

  • MarcZeller criticized the use of overly precise, non-round numbers (e.g., liquidation bonus of 10.83%, debt ceiling of 20,929k) in the proposed risk parameters, requesting rounder figures for cleaner, less error-prone code, without a clear resolution in the thread.— MarcZeller
  • Several parameters (stable borrowing slopes, offsets, and optimal stable-to-total debt ratio) were left marked as 'to be confirmed by Gauntlet' in the original specification, and it's unclear if these were ever explicitly finalized in the thread.— Llamaxyz

Notable participants

  • LlamaxyzProposal author who drafted the ARFC, responded to feedback, and shepherded the proposal through Snapshot and toward AIP.
  • PauljleiGauntlet representative who provided updated risk parameter recommendations (borrow/supply caps and liquidation bonus).
  • MarcZellerACI representative who expressed general support while critiquing the precision of numerical parameters and awaiting risk team input.
  • RudyCommunity member who voiced clear support for the proposal.
  • dydymoonListed co-author of the proposal alongside Llamaxyz.
Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Open the thread ↗