KVORUM
aaveSource: Aave governance v3 · #421

Remove USDS as collateral and increase RF across all Aave Instances

executedDec 22, 2025, 08:31 AM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

Proposal to remove USDS as collateral across all Aave instances by setting LTV to 0%, reduce USDS supply and borrow caps by 80%, increase USDS reserve factor from 10% to 25%, reduce DAI LTV to 0% across multiple chains, and remove USDS from multiple eMode categories. Rationale: USDS revenue has declined sharply (from $244k Q1 to $18k Q4 2024) and is too low to justify risk exposure; issuance model changes introduce unacceptable risks for collateral.

Type
parameter change

Key changes

  • Remove USDS as collateral by setting LTV to 0% on Ethereum Core(high)
  • Increase USDS reserve factor from 10% to 25% on Ethereum Core and Prime instances to boost revenue by ~150%(high)
  • Reduce USDS supply cap from 800M to 160M on Ethereum Core and from 200M to 40M on Prime(high)
  • Reduce USDS borrow cap from 360M to 144M on Ethereum Core and from 180M to 36M on Prime(high)
  • Set DAI LTV to 0% across Optimism, Polygon, Avalanche, Arbitrum, Ethereum Core, and Metis(high)
  • Reduce DAI supply and borrow caps across multiple instances (Ethereum Core, Optimism, Metis)(medium)
  • Remove USDS from 12 eMode categories across Core and Prime instances(medium)

Notable concerns

  • USDS revenue declined 93% from Q1 2024 ($244k) to Q4 2024 ($18k), indicating insufficient profitability to justify collateral exposure
  • Sky ecosystem changes including new credit lines at low or zero cost and new yield strategies increase USDS risk profile beyond acceptable levels for Aave collateral
  • Proposal significantly reduces USDS supply and borrow caps (80% reduction), which may impact users with positions using USDS as collateral
ContractsAaveV3EthereumAaveV3EthereumLidoAaveV3PolygonAaveV3AvalancheAaveV3OptimismAaveV3ArbitrumAaveV3Metis
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

629 words

Simple Summary

This AIP proposes removing USDS as collateral and increasing RF across all Aave instances.

USDS generates negligible revenue while its issuance model introduces asymmetric risks that could impact Aave’s stability.

Motivation

Motivation for these changes is driven by both reducing revenue from USDS borrows, and changing risk profile bringing into doubt the suitability of the asset as collateral.

1. Low Profitability

Data shows a decline in revenue each month, with $543,528 since Q1 2025, and current annualised revenue of $135,260 based on revenue since the beginning of Q4. With quarterly revenue data showing a sharp decline since the beginning of the year, we believe that current revenue is far below the scale required to justify current risk exposure.

InstanceQ1Q2Q3Q4
Cove V3$87,948$127,768$96,556$17,417
Prime V3$156,205$47,999$9,276$359
Total$244,153$175,767$105,832$17,776

To combat this decline in revenue we propose raising RF to 25% which would increase Aave revenue by +150% on the same borrow volume.

2. Potential Risks from Issuance Model

With the new Stars being created within the Sky ecosystem, the risk profile of USDS is changing. Given these changes characterised by credit lines at low or zero cost, and the risk surface area presented by the yield strategies being utilised, we believe that the risk profile has increased to a degree which is outside of what is acceptable for Aave collateral.

Alongside the increase in RF we propose setting LTV to 0% in order to remove Aave’s exposure to USDS as collateral. Combined, we believe these measures bring the risk/reward of USDS back in line with other assets on Aave.

Specification

InstanceAssetCurrent Max LTVRecommended Max LTV
OptimismDAI63%0%
PolygonDAI63%0%
AvalancheDAI.e63%0%
ArbitrumDAI63%0%
Ethereum CoreDAI63%0%
Ethereum CoreUSDS75%0%
Metism.DAI63%0%
AssetChainCurrent Supply CapRecommended Supply CapCurrent Borrow CapRecommended Borrow CapCurrent RFRecommended RF
USDSEthereum Core800,000,000160,000,000360,000,000144,000,00010%25%
USDSEthereum Prime200,000,00040,000,000180,000,00036,000,00010%25%
DAIEthereum Core338,000,000200,000,000271,000,000180,000,000--
DAIOP Mainnet10,000,0002,000,0007,000,0001,800,000--
m.DAIMetis1,000,000200,000900,000180,000--

Moreover USDS will be removed from the following emodes:

Core:

  • USDe_sUSDe__USDC_USDT_USDS (id:2)
  • sUSDe_PT_sUSDE_31JUL2025__USDC_USDT_USDS (id: 8)
  • PT_eUSDE_29MAY2025_eUSDe__USDC_USDT_USDS (id: 9)
  • USDe_PT_USDe_31JUL2025__USDC_USDT_USDS (id: 10)
  • USDe__USDC_USDT_USDS (id: 11)
  • PT_eUSDE_14AUG2025_eUSDe__USDC_USDT_USDS (id: 13)
  • eUSDe__USDC_USDT_USDS (id: 15)
  • sUSDe_PT_sUSDE_31JUL2025_PT_sUSDE_25SEP2025__USDC_USDT_USDe_USDS_USDtb (id: 17)
  • USDe_PT_USDe_31JUL2025_PT_eUSDE_14AUG2025_PT_USDe_25SEP2025__USDC_USDT_USDe_USDS (id: 19)
  • sUSDe_PT_sUSDE_25SEP2025_PT_sUSDE_27NOV2025__USDC_USDT_USDe_USDS_USDtb (id: 24)
  • PT_USDe_25SEP2025_PT_USDe_27NOV2025__USDC_USDT_USDe_USDS_USDtb (id: 27)

Prime:

  • ezETH__USDS_USDC_GHO (id: 2)
  • rsETH__USDS_USDC_GHO (id: 6)

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal description is a detailed, standard Aave risk-parameter AIP: it proposes setting USDS (and correlated DAI-variant) LTVs to 0% across seven instances, raising RF on USDS to 25% on Ethereum Core/Prime, reducing supply/borrow caps, and removing USDS from several e-mode categories. However, the decoded on-chain calldata only reveals two generic execute() (fallback) calls to two contract addresses on Ethereum mainnet — these are almost certainly calls to the AaveV3Ethereum and AaveV3EthereumLido payload contracts referenced in the proposal's implementation links, which in turn contain the granular logic (including bridged calls to Optimism, Polygon, Avalanche, Arbitrum, and Metis governance receivers). This is the standard architecture for Aave cross-chain governance proposals, where the top-level DAO vote only directly invokes one or two payload executors on mainnet, and the rest of the multi-chain configuration is delegated internally. Since no parameter values (LTV %, RF %, caps, e-mode removals) are decoded in the calldata provided, I cannot directly verify each numeric claim against on-chain data — but this opacity is typical and expected for this proposal type, not indicative of a mismatch or malicious redirection. There is no evidence of target mismatch, extra actions, or omitted major actions beyond what is normal boilerplate for this governance pattern. Given the very limited decoded action-level detail, my confidence in this comparison is low, but I found no basis to flag a genuine discrepancy — the visible actions (two execute calls to known payload-style contracts) are consistent with what the description implies (multi-instance risk parameter updates).

Discrepancies

  • lowomitted in description

    The decoded calldata only shows two opaque execute() calls to payload contracts on Ethereum mainnet, with no visible parameters for the LTV, RF, cap, or e-mode changes described in the proposal. This is consistent with Aave's standard governance pattern where a top-level AIP calls payload contracts that internally execute the detailed cross-chain configuration changes (including bridging messages to other networks like Optimism, Polygon, Avalanche, Arbitrum, and Metis). Because the actual parameter changes are not decoded here, a reviewer cannot independently verify that the LTV=0%, RF=25%, or cap reductions match the prose from calldata alone.

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

04Actions

2 total
#0fallback()chain 0x1
Target
0x281e…550a
Value
0 wei
Function
fallback()
Arguments
{}
Calldata
#1fallback()chain 0x1
Target
0x7d94…54c5
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
EA0xea0c…6b5aFor333K0.00%—11mo ago
570x57ab…2922For227.8K0.00%—11mo ago
EZezr3al.eth0x8659…7d0eFor141.2K0.00%—11mo ago
8B0x8b37…2a22For74.3K0.00%—11mo ago
2C0x2cc1…4df1For58.5K0.00%—11mo ago
B90xb933…8dd1For42.3K0.00%—11mo ago
EC0xecc2…6ac9For25K0.00%—11mo ago
3D0x3ddc…05b0For20.1K0.00%—11mo ago
8A0x8af7…fa05Against12.9K0.00%—11mo ago
480x48e5…6430For1.6K0.00%—11mo ago
A50xa54f…0f31Against1.3K0.00%—11mo ago
AA0xaaab…2335Against752.80.00%—11mo ago
930x93cd…becaFor26.50.00%—11mo ago
720x7204…6f00For15.50.00%—11mo ago
2E0x2ef9…02c6For11.30.00%—11mo ago
010x010d…4ee4For1.30.00%—11mo ago
010x0151…c3b9Against1.20.00%—11mo ago
8B0x8bb9…ccc2Against1.10.00%—11mo ago
050x0579…4048For10.00%—11mo ago
C50xc554…7759For10.00%—11mo ago
010x019e…2ee3For0.30.00%—11mo ago
050x05f7…946cFor0.20.00%—11mo ago
D00xd0de…b16fFor0.20.00%—11mo ago
160x168f…7400For0.10.00%—11mo ago
C80xc8f1…17c2For0.10.00%—11mo ago
6A0x6a87…21cbFor0.10.00%—11mo ago
1C0x1c69…7911For0.10.00%—11mo ago
AF0xaf21…ed16For00.00%—11mo ago
A90xa97c…ccc8For00.00%—11mo ago
2F0x2f2f…f78aFor00.00%—11mo ago
7F0x7f21…31e0For00.00%—11mo ago
E80xe8ee…0877For00.00%—11mo ago
AC0xacc9…0b28For00.00%—11mo ago
930x93e0…f6eeFor00.00%—11mo ago
140x1475…6e15For00.00%—11mo ago
E60xe6b8…452dFor00.00%—11mo ago
D70xd712…1366For00.00%—11mo ago
4D0x4d12…7d7cFor00.00%—11mo ago
BE0xbef8…9999For00.00%—11mo ago
A00xa0d0…604aFor00.00%—11mo ago
EE0xee2a…58a7For00.00%—11mo ago
D20xd248…32aeFor00.00%—11mo ago
A60xa6ac…2bf3For00.00%—11mo ago
7A0x7a04…17a8For00.00%—11mo ago
150x1523…080fFor00.00%—11mo ago
380x38dc…472dFor00.00%—11mo ago
210x21ff…c5a8For00.00%—11mo ago
ED0xed4c…9508For00.00%—11mo ago
470x475e…e10cFor00.00%—11mo ago
D20xd220…0e79For00.00%—11mo ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.