KVORUM
aaveSource: Aave governance v3 · #105

Chaos Labs Ethereum V2 LT Reductions

executedMay 19, 2024, 01:46 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

Proposal to reduce Liquidation Thresholds on two frozen assets in Aave V2 Ethereum as part of V2 deprecation: LINK from 68% to 65% and ZRX from 5% to 0.01%. This will result in approximately $688 in liquidations across 6 accounts.

Type
parameter change

Key changes

  • Reduce LINK Liquidation Threshold from 68% to 65%(medium)
  • Reduce ZRX Liquidation Threshold from 5% to 0.01%(medium)
  • Liquidation of approximately $688 across 6 user accounts as a result of these changes(medium)

Notable concerns

  • Parameter changes will trigger liquidations of user accounts; 6 accounts will become eligible for liquidation upon approval
  • Liquidation Thresholds reductions are part of Aave V2 deprecation strategy
  • Changes are set with a 4-6% margin from closest LT figures to minimize liquidation impact
ContractsAave V2 EthereumLINK token contractZRX 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

199 words

Simple Summary

A proposal to reduce Liquidation Thresholds on Aave V2 Ethereum.

Motivation

In continuation of the deprecation of Aave V2, Chaos Labs advises implementing the subsequent parameter changes to the frozen assets on Aave v2 Ethereum.

As Liquidation Threshold reductions may lead to user accounts being eligible for liquidations upon their approval, we want to clarify the full implications to the community at each step. We will publicly communicate the planned amendments and list of affected accounts leading to the on-chain execution.

Our recommendations below suggest an LT configuration that optimizes reductions without significantly increasing the number of accounts eligible for liquidation. The proposed values are set at a margin of ~4-6% from the closest LT figure, which would trigger more substantial liquidations.

Specification

AssetCurrent LTRecommended LT
LINK68%65%
ZRX5%0_01%
Value liquidatedAccounts liquidated
Total$6886

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal describes two specific Liquidation Threshold reductions (LINK 68%→65%, ZRX 5%→0.01%) on Aave V2 Ethereum. The decoded on-chain action is a single execute() call to an external payload contract address, which resolves to a fallback() function. This is the standard execution pattern used by Aave governance proposals: the governance executor calls execute() on a dedicated payload contract whose bytecode contains the actual parameter-changing logic (e.g., calls to the LendingPoolConfigurator to set new LT values). Because the decoded calldata does not expose the internal logic of the payload contract (no parameters, no nested calls decoded), it is not possible to directly verify from the calldata alone that the LT values match exactly 65% and 0.01% as described. However, the target address matches the type of contract referenced in the proposal's 'Implementation' link, and this pattern is routine and expected for this proposal type. Given the lack of visibility into the actual parameter values being set, confidence in a full match is low, but there is no evidence of any mismatch, hidden transfer, or unrelated action — nothing in the available data contradicts the description. Therefore, I assess this as consistent with low confidence due to the opacity of the single delegatecall-style action, which is typical and not itself a red flag for Aave V2 payload executions.

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
0xdc38…bd23
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.