KVORUM
aaveSource: Aave governor v2 · #390

Onboarding wstETH to Aave V3 on Base Network

canceledDec 6, 2023, 03:55 AM UTCby320x329c…3ed4

01Summary

AISummary by Kvorumclaude-haiku-4-5

This proposal onboards wstETH (wrapped staked ETH) from Lido as a new asset on Aave V3 Base Network, enabling users to use it as collateral and borrow against it, with a 4,000 wstETH supply cap and 400 wstETH borrow cap.

Type
protocol addition

Key changes

  • wstETH onboarded as collateral asset on Aave V3 Base Network with collateral enabled(high)
  • wstETH enabled for borrowing with 400 wstETH borrow cap(high)
  • LTV set to 71% and liquidation threshold set to 76% for risk management(high)
  • Supply cap set to 4,000 wstETH to limit exposure(medium)
  • Stable borrowing disabled for wstETH to reduce risk(medium)
  • Flash loan functionality enabled for wstETH(low)

Notable concerns

  • Debt ceiling set to USD 0, restricting isolated borrowing against wstETH
  • Siloed borrowing disabled, meaning wstETH cannot be used as sole collateral in isolation mode
Contracts0xc1CBa3fCea344f92D9239c08C0568f6F2F0ee4520x2DC219E716793fb4b21548C0f009Ba3Af753ab01
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

285 words

Simple Summary

This AIP proposes the onboarding of wstETH (wrapped staked ETH) from Lido to the Aave V3 Base Network to enrich the diversity of the ecosystem's liquid staking assets.

Motivation

The onboarding of wstETH will provide Aave users with more options for earning staking rewards on their collateral, reinforcing Aave's position as a diverse and inclusive DeFi protocol.

Specification

The table below illustrates the configured risk parameters for wstETH

ParameterValue
Isolation Modefalse
BorrowableENABLED
Collateral Enabledtrue
Supply Cap (wstETH)4,000
Borrow Cap (wstETH)400
Debt CeilingUSD 0
LTV71 %
LT76 %
Liquidation Bonus6 %
Liquidation Protocol Fee10 %
Reserve Factor15 %
Base Variable Borrow Rate0 %
Variable Slope 17 %
Variable Slope 2300 %
Uoptimal45 %
Stable BorrowingDISABLED
Stable Slope113 %
Stable Slope2300 %
Base Stable Rate Offset3 %
Stable Rate Excess Offset5 %
Optimal Stable To Total Debt Ratio20 %
FlashloanableENABLED
Siloed BorrowingDISABLED
Borrowable in IsolationDISABLED
Oracle0x945fD405773973d286De54E44649cc0d9e264F78

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal's only decoded on-chain action is a single call to forwardPayloadForExecution, which is the standard BGD/Aave cross-chain governance pattern: it instructs the L1 governance to forward execution to a specific payload contract already deployed on Base (chain id 8453). This action itself does not contain the granular risk parameters (LTV, LT, caps, oracle address, etc.) described in the prose — those are encoded inside the target payload contract on Base, which is not part of the decoded calldata provided here. Because the mechanism (forwarding to Base for a wstETH-related payload) matches the description's intent (onboarding wstETH to Aave V3 Base), there is no evident mismatch in target chain, target contract type, or action count. However, since the actual numeric risk parameters cannot be independently verified from the single forwarding call, confidence in a full parameter-by-parameter match is low. No omissions, extra claims, or target mismatches are apparent between the description and the visible calldata action.This is typical for BGD-style cross-chain listing proposals, so it is not flagged as a discrepancy, but the inability to verify granular values keeps confidence low rather than high.'}],

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
#0forwardPayloadForExecution((uint256,uint8,address,uint40))chain 0x1
Target
0x9aee…2bc7
Value
0 wei
Function
forwardPayloadForExecution((uint256,uint8,address,uint40))
Arguments
{
  "0": [
    "8453",
    "1",
    "0x2DC219E716793fb4b21548C0f009Ba3Af753ab01",
    "3"
  ]
}
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.