KVORUM
aaveSource: Aave governor v2 · #284

Reserve Factor Updates - Polygon Aave v2

executedAug 4, 2023, 08:51 AM UTCby550x55b1…f262

01Summary

AISummary by Kvorumclaude-haiku-4-5

This proposal updates Reserve Factors (RF) on Aave Polygon v2 to incentivize user migration to v3. It increases RFs for major stablecoins (DAI to 26%, USDC to 28%, USDT to 27%) and other assets, with frozen assets receiving RFs up to 99.99% to generate near-zero deposit yields. This reduces supply-side returns on v2 without affecting borrowing rates or liquidation risk.

Type
parameter change

Key changes

  • DAI Reserve Factor increased to 26%(medium)
  • USDC Reserve Factor increased to 28%(medium)
  • USDT Reserve Factor increased to 27%(medium)
  • wBTC Reserve Factor increased to 60%(medium)
  • wETH Reserve Factor increased to 50%(medium)
  • MATIC Reserve Factor increased to 46%(medium)
  • BAL Reserve Factor increased to 37%(low)
  • CRV, GHST, LINK Reserve Factors increased to 99.99%(high)

Notable concerns

  • Frozen assets (CRV, GHST, LINK) with 99.99% RF will provide near-zero deposit yields, affecting approximately $680k in user positions (less than 0.5% of Aave v2 TVL)
  • Proposal will assess user elasticity and impact before implementing additional RF increases
Contracts0x158a6bc04f0828318821bae797f50b0a1299d45b0x812dDad273544754d0672A009C27550899e658Aa
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

308 words

Simple Summary

This AIP will update Reserve Factors (RF) on Polygon v2 to encourage users to migrate funds to v3.

Motivation

With the goal of transitioning users from Polygon v2 to v3, this publication, if implemented, will increase the RF of asset on the v2 deployment.

Increasing the RF routes a larger portion of the interest paid by users to Aave DAO’s Treasury. User’s funds are not at risk of liquidation and the borrowing rate remains unchanged.

By progressively increasing the reserve factors, the interest rate for supplying these assets on v2 will be increasingly less attractive, thus encouraging suppliers to transition positions to v3.

Of the assets that are currently frozen, with the exception of BAL, the RF is to be increaed to 99.99%. Around $680k of users positions, CRV, DPI, GHST and LINK will receive near zero deposit yield. This represents less than 0.5% of Aave v2’s TVL. The highest deposit yield of these assets at the time of writing is 0.21%. This change will have minimal affect.

The remaining assets are to receive an incremental 5% increase in the RF. After implementing this publication, user elasticity shall be assessed and the impact of the updates before moving forward with additional increases.

Specification

The following parameters are to be updated as follows:

AssetReserve Factor
DAI26.00%
USDC28.00%
USDT27.00%
wBTC60.00%
wETH50.00%
MATIC46.00%
BAL37.00%
CRV99.99%
GHST99.99%
LINK99.99%

Implementation

A list of relevant links like for this proposal:

The proposal Payload was reviewed by Bored Ghost Developing.

Disclaimer

The author, TokenLogic, receives payment indirectly from Aave Grant DAO via Butter as part of the Incentivised Delegate Campaign. TokenLogic is a delegate within Aave community.

Delegate: 0x2cc1ADE245020FC5AAE66Ad443e1F66e01c54Df1

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Consistent

The decoded calldata contains a single top-level action: a call to execute(address) targeting 0x812dDad273544754d0672A009C27550899e658Aa. This address matches exactly the 'Deployed Contracts' link provided in the proposal's Implementation section, confirming the on-chain action invokes the correct payload contract that the proposal authors identified as containing the Reserve Factor update logic. This is standard Aave governance pattern: the mainnet vote triggers execute() on a payload contract, which internally performs the granular parameter changes (in this case, on Polygon v2 reserves) — those internal calls are not separately decoded here, which is typical and expected boilerplate for this type of proposal, not a discrepancy. Because the internal RF-setting calls inside the payload are not present in the decoded data, I cannot verify the exact numeric RF values (26%, 28%, 99.99%, etc.) against calldata directly — this limits confidence to medium rather than high. However, given the target address matches the disclosed and reviewed payload contract, and no additional or conflicting actions appear in the calldata, there is no evidence of target mismatch, hidden transfers, or value discrepancies. I therefore find the description and calldata consistent, with the caveat that full verification of exact RF percentages would require decoding the internal logic of the payload contract itself, which is outside the scope of the provided decoded action list.

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
#0execute(address)chain 0x1
Target
0x158a…d45b
Value
0 wei
Function
execute(address)
Arguments
{
  "0": "0x812dDad273544754d0672A009C27550899e658Aa"
}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

No forum thread is confidently linked to this proposal.