aaveSource: Aave governance v3 · #163

Harmonize weETH Parameters

executedSep 16, 2024, 05:40 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

This proposal standardizes weETH borrowing parameters across Ethereum, Arbitrum, Base, and Scroll by setting the base variable borrow rate to 1%, increasing the Reserve Factor to 45%, and setting the optimal utilization ratio to 30%. The changes aim to increase DAO revenue, improve weETH liquidity, and create consistency across networks.

Type: parameter change

Key changes

Set base variable borrow rate for weETH to 1%(medium)
Adjust Reserve Factor (RF) to 45% on all networks(high)
Set optimal utilization ratio to 30%(medium)

ContractsAaveV3EthereumAaveV3ArbitrumAaveV3BaseAaveV3Scroll

Generated by Kvorum

model: claude-haiku-4-5

provider: anthropic

profile: anthropic-fast-v1

prompt: v1.0

generated: 2mo ago

Read the description ↗

02Description

271 words

Simple Summary

This proposal aims to harmonize weETH parameters across all networks where it is supported.

Motivation

This proposal aims to harmonize weETH parameters across all networks where it is supported.

The key changes include:

Setting the base variable borrow rate for weETH to 1% Adjusting the Reserve Factor (RF) to 45% on all networks Setting the optimal utilization ratio to 30% The primary motivations for these parameter adjustments are:

Increased Revenue for the DAO: By harmonizing these parameters, particularly the increase in the Reserve Factor, we can generate additional revenue for the Aave DAO.

Improved External Liquidity: The proposed changes, especially the adjustment of the optimal utilization ratio, are expected to enhance the external liquidity of weETH. This improvement in liquidity can lead to more efficient liquidity and better capital utilization within the Aave ecosystem.

Consistency Across Networks: By standardizing these parameters across all networks where weETH is supported, we create a more uniform and predictable environment for users and integrators. This consistency will lead to improved user experience and easier management of the asset across different networks.

These changes represent a balanced approach to optimizing the performance of weETH within the Aave protocol, benefiting both the DAO and its users while maintaining weETH’s attractiveness and utility

Specification

On all networks, change weETH parameters to:

Base variable borrow rate for weETH to 1%
Adjusting the Reserve Factor (RF) to 45%
Setting the optimal utilization ratio to 30%

References

Implementation: AaveV3Ethereum, AaveV3Arbitrum, AaveV3Base, AaveV3Scroll
Tests: AaveV3Ethereum, AaveV3Arbitrum, AaveV3Base, AaveV3Scroll
Snapshot
Discussion

Copyright

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5

Consistent

The proposal description lays out three specific parameter changes for weETH (base variable borrow rate to 1%, Reserve Factor to 45%, optimal utilization ratio to 30%) to be applied uniformly across Ethereum, Arbitrum, Base, and Scroll, with links to per-network payload contracts. The decoded on-chain action set contains only a single row: a generic execute() call on a payload contract on Ethereum (chain 0x1), with no decoded internal parameters. This is standard for Aave governance, where the AIP payload's execute() function performs a delegatecall that applies the actual pool configuration changes; the specific numeric parameters are not visible in this decoded action. Because the calldata is opaque at this level of decoding, I cannot directly verify whether the 1%/45%/30% figures match what execute() actually sets, nor confirm the other three network-specific payloads (Arbitrum, Base, Scroll) are included, since only one action (Ethereum) is decoded. However, nothing in the decoded data contradicts the description, and the single execute() call is consistent with the expected implementation pattern referenced in the proposal's own links. Given the lack of granular parameter visibility, confidence is low, but there is no evidence of a value mismatch, target mismatch, or omitted/extra action — hence the assessment is 'consistent' rather than flagging a discrepancy based on speculation about what the opaque call does.

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: 0x1cd2…3728
Value: 0 wei
Function: fallback()
Arguments: {}
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.

08Similar proposals

AI · embeddings