KVORUM
aaveSource: Aave governance v3 · #323

Onboard wrsETH to ZKsync V3 Instance

executedJun 10, 2025, 05:54 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

Proposal to onboard wrsETH (wrapped restaking ETH) to Aave V3 on ZKsync as collateral with a 700 supply cap, and to increase rsETH E-Mode parameters on the Prime instance (LTV from 92.5% to 93%, LT from 94.5% to 95%).

Type
protocol addition

Key changes

  • Onboard wrsETH to Aave V3 ZKsync as collateral with supply cap of 700 wrsETH, not borrowable, LTV 0.05%, LT 0.1%(high)
  • Enable wrsETH/wstETH E-Mode on ZKsync with 92.5% LTV and 94.5% LT for wrsETH(high)
  • Update rsETH E-Mode parameters on Prime instance: increase LTV from 92.5% to 93% and LT from 94.5% to 95%(medium)
  • Set emission admin for wrsETH and aToken to 0x95Cbff6e45C499d45dd8627f3ce179057B5Fbfcc(medium)
  • Enable flashloaning for wrsETH(low)

Notable concerns

  • wrsETH has very low LTV (0.05%) and LT (0.1%) indicating minimal collateral value in default isolation mode
  • Prime instance rsETH E-Mode update is bundled due to Risk Steward not yet deployed on Ethereum, which is a workaround rather than standard procedure
  • Borrow cap set to 1 despite borrowing being disabled, creating potential confusion
ContractsAave V3 ZKsync InstanceAave V3 Prime InstancewrsETH token contractrsETH token contract
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

562 words

Simple Summary

This is a proposal to onboard wrsETH to the Aave V3 ZKsync Instance allowing Aave users to supply wrsETH as collateral. This proposal will be under Direct to AIP, as there are already on other Aave Instances.

Additionally, this AIP will update the rsETH LST E-Mode of the Prime instance.

Motivation

In order to benefit from the ongoing ZKsync Ignite incentives program, we propose onboarding assets which have proven popular on other Aave instances and are either whitelisted for Ignite incentives, or are good candidates for future whitelisting.

wrsETH is currently the only whitelisted liquid restaking token on ZKsync and has proven popular on the Aave Prime instance, therefore we believe should be onboarded to the Aave Instance on ZKsync too.

Specification

The table below illustrates the configured risk parameters for wrsETH

ParameterValue
Isolation Modefalse
BorrowableDISABLED
Collateral Enabledtrue
Supply Cap (wrsETH)700
Borrow Cap (wrsETH)1
Debt CeilingUSD 0
LTV0.05 %
LT0.1 %
Liquidation Bonus7.5 %
Liquidation Protocol Fee10 %
Reserve Factor10 %
Base Variable Borrow Rate0 %
Variable Slope 110 %
Variable Slope 2300 %
Uoptimal45 %
FlashloanableENABLED
Siloed BorrowingDISABLED
Borrowable in IsolationDISABLED
Oracle0x8d25c9de6DBAd9a9eadfB2CA4706034F6721d555

Pricefeed details

ParameterValue
OracleCapped rsETH / ETH / USD
BASE/USD OracleChainlink ETH/USD
Ratio ProviderrsETH
Oracle Latest Answer(2025-05-27) USD 2726.41712463
min snapshot14 days
max yearly growth9.83%

wrsETH/wstETH E-Mode

ParameterValueValue
AssetwrsETHwstETH
CollateralYesNo
BorrowableNoYes
LTV92.50%-
LT94.50%-
Liquidation Penalty1.00%-

Additionally 0x95Cbff6e45C499d45dd8627f3ce179057B5Fbfcc has been set as the emission admin for wrsETH and the corresponding aToken.

Prime rsETH LST E-Mode Update

ParameterValueValue
AssetrsETHwstETH
CollateralYesNo
BorrowableNoYes
LTV92.50% 93%-
LT94.50% 95%-
Liquidation Penalty1.00%-

This E-Mode update come from this AIP. It wasn’t included in the AIP itself because it could be executed via the Risk Steward. However, since the new version of the Risk Steward has not yet been deployed on the Ethereum Prime instance, we’re currently unable to update the E-mode through it. As a result, we are proposing to bundle this change into the current rsETH ZkSync onboarding AIP.

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal description is highly detailed, specifying exact risk parameters for onboarding wrsETH on Aave V3 ZKsync, a new E-Mode, an emission admin assignment, and a Prime instance rsETH E-Mode update. However, the decoded calldata contains only a single generic execute() (fallback()) call to a contract on Ethereum mainnet, with no arguments decoded. This is the typical pattern for Aave Governance V3 proposals, where the actual granular logic (asset listing parameters, e-mode configuration, cross-chain relay to the ZKsync executor) is encoded inside the target Payload contract's bytecode rather than exposed as decoded top-level calldata. Because the decoded action carries no parameters, it is not possible to independently verify that the numeric values (LTV, LT, caps, oracle addresses, emission admin address, Prime e-mode changes) in the description match what the payload contract will actually execute. No contradiction was found, but this is due to lack of visibility into the payload's internals rather than confirmed alignment. Given this, confidence in the comparison is low, and no discrepancy is asserted since none can be substantiated from the available calldata — flagging one here would be speculative rather than evidence-based.

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
0xcbad…6587
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters33
VP participating563.3K
Outcome (current)For
Current support100%

06Voters

33 total
Filter:
VoterChoice% of totalRationale
570x57ab…2922For297.9K52.88%—1y ago
2E0x2e21…f21aFor104.3K18.52%—1y ago
EZezr3al.eth0x8659…7d0eFor57.6K10.23%—1y ago
B90xb933…8dd1For39.6K7.02%—1y ago
EC0xecc2…6ac9For21.8K3.87%—1y ago
3D0x3ddc…05b0For20.1K3.56%—1y ago
8B0x8b37…2a22For10.9K1.93%—1y ago
2C0x2cc1…4df1For5.5K0.98%—1y ago
080x0865…24ceFor2K0.36%—1y ago
440x4444…34b3For1.7K0.31%—1y ago
620x6276…b4e8For603.90.11%—1y ago
B30xb356…c826For4800.09%—1y ago
A50xa54f…0f31For2700.05%—1y ago
3C0x3c25…5363For200.50.04%—1y ago
F10xf13c…6dd3For141.60.03%—1y ago
9A0x9a62…3e0eFor57.80.01%—1y ago
7D0x7dcc…9fcaFor22.50.00%—1y ago
7E0x7ee5…a6c1For200.00%—1y ago
640x649f…35b8For10.40.00%—1y ago
BB0xbb86…3527For4.80.00%—1y ago
2F0x2f2f…f78aFor20.00%—1y ago
C50xc554…7759For10.00%—1y ago
050x0579…4048For10.00%—1y ago
2E0x2e00…67faFor10.00%—1y ago
7D0x7d40…ef1dFor0.60.00%—1y ago
010x019e…2ee3For0.30.00%—1y ago
6E0x6e54…aea3For0.30.00%—1y ago
010x0100…7cc9For0.20.00%—1y ago
EF0xefdb…3c77For0.20.00%—1y ago
160x168f…7400For0.10.00%—1y ago
930x93fd…f5bcFor00.00%—1y ago
D80xd8de…ae41For00.00%—1y ago
CB0xcb15…a1a0For00.00%—1y ago
Showing 33

07Forum

No forum thread is confidently linked to this proposal.