KVORUM
aaveSource: Aave governor v2 · #54

Risk Parameter Updates 2021-12-29

defeatedJan 9, 2022, 06:06 AM UTCby680x683a…6c02

01Summary

AISummary by Kvorumclaude-haiku-4-5

Batch update of risk parameters (LTV, Liquidation Threshold, and Liquidation Bonus) across 7 Aave V2 assets to align with the community-chosen Moderate risk level. Changes reduce liquidation bonuses on less-utilized assets while maintaining overall protocol risk tolerance.

Type
parameter change

Key changes

  • Adjusted LTV, Liquidation Threshold, and Liquidation Bonus for BAL (0xba100000625a3754423978a60c9317c58a414e3D): LTV 65%, Liquidation Threshold 70%, Liquidation Bonus 10.75%(medium)
  • Adjusted LTV, Liquidation Threshold, and Liquidation Bonus for CRV (0xD533a949740bb3306d119CC777fa900bA034cd52): LTV 55%, Liquidation Threshold 60%, Liquidation Bonus 10.85%(medium)
  • Adjusted LTV, Liquidation Threshold, and Liquidation Bonus for DPI (0x1494CA1F11D487c2bBe4543E90080AeBa4BA3C2b): LTV 70%, Liquidation Threshold 75%, Liquidation Bonus 10.75%(medium)
  • Adjusted LTV, Liquidation Threshold, and Liquidation Bonus for ENJ (0xF629cBd94d3791C9250152BD8dfBDF380E2a3B9c): LTV 70%, Liquidation Threshold 70%, Liquidation Bonus 10.75%(medium)
  • Adjusted LTV, Liquidation Threshold, and Liquidation Bonus for MANA (0x0F5D2fB29fb7d3CFeE444a200298f468908cC942): LTV 70%, Liquidation Threshold 75%, Liquidation Bonus 10.75%(medium)
  • Adjusted LTV, Liquidation Threshold, and Liquidation Bonus for MKR (0x9f8F72aA9304c8B593d555F12eF6589cC3A579A2): LTV 65%, Liquidation Threshold 70%, Liquidation Bonus 10.75%(medium)
  • Adjusted LTV, Liquidation Threshold, and Liquidation Bonus for UNI (0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984): LTV 60%, Liquidation Threshold 70%, Liquidation Bonus 10.75%(medium)
Contracts0x311bb771e4f8952e6da169b425e7e92d6ac45756
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

213 words

Simple Summary

A proposal to adjust nine (9) total risk parameters across seven (7) Aave V2 assets including LTV, Liquidation Threshold, and Liquidation Bonus.

Abstract

This proposal is a batch update of risk parameters to align with the the Moderate risk level chosen by the Aave community. These parameter updates are a continuation of Gauntlet's regular parameter recommendations.

Motivation

This set of parameter updates seeks to maintain the overall risk tolerance of the protocol while making risk trade-offs between specific assets.

Specification

This past week did not see outsized changes in market conditions nor within the Aave protocol. There were slight volatility drops and increases in trading volume and liquidity for most assets. Our platform recommends the following set of parameter changes that will decrease liquidation bonuses on several less-utilized assets.

Risk Dashboard

The community should use Gauntlet's Risk Dashboard to better understand the updated parameter suggestions and general market risk in Aave V2.

Implementation

The proposal sets the liquidation bonus, LTV and liquidation threshold ratios by calling configureReserveAsCollateral on the LendingPoolConfigurator contract at 0x311Bb771e4F8952E6Da169b425E7e92d6Ac45756, using the address and parameters specific to each token.

The full list of parameter updates can be found in the forum.

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Consistent

The proposal describes a routine Gauntlet risk-parameter update executed via configureReserveAsCollateral calls on the LendingPoolConfigurator contract, and the calldata shows exactly seven such calls, one per asset, setting LTV, Liquidation Threshold, and Liquidation Bonus values — consistent with the described implementation mechanism and target contract address (case differences only, same address). The description is high-level and defers exact per-asset numbers to an external forum post, so granular values (e.g., 65% LTV for BAL) cannot be individually cross-checked against stated intent beyond the general direction (decreasing liquidation bonuses on less-utilized assets), which is plausible given the LB values shown (all in the 107.5%-108.5% range, i.e., relatively low bonuses). The one notable inconsistency is the claim of 'nine total risk parameters' versus 21 parameter fields actually being set across 7 assets x 3 parameters; this could be explained by many values remaining unchanged from current on-chain state, which we cannot verify, so it is flagged as a low-severity, low-confidence discrepancy rather than a material one. No target mismatches, fund transfers, or unexpected extra actions were found. Overall the description and calldata are consistent with only a minor, unverifiable count discrepancy.

Discrepancies

  • lowvalue mismatch

    The description states that nine (9) total risk parameters are being changed, but the calldata configures three parameters (LTV, LT, LB) for each of the seven assets — up to 21 parameter values in total. Without knowledge of the assets' prior parameter values, it cannot be confirmed whether only 9 of these actually change (the rest may be no-ops matching current settings), so this may simply reflect that most values are unchanged, but it is not independently verifiable from the calldata alone.

    “A proposal to adjust nine (9) total risk parameters across seven (7) Aave V2 assets including LTV, Liquidation Threshold, and Liquidation Bonus.”

Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

7 total
#0configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0xba100000625a3754423978a60c9317c58a424e3D",
  "1": "6500",
  "2": "7000",
  "3": "10750"
}
Calldata
#1configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0xD533a949740bb3306d119CC777fa900bA034cd52",
  "1": "5500",
  "2": "6000",
  "3": "10850"
}
Calldata
#2configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0x1494CA1F11D487c2bBe4543E90080AeBa4BA3C2b",
  "1": "7000",
  "2": "7500",
  "3": "10750"
}
Calldata
#3configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0xF629cBd94d3791C9250152BD8dfBDF380E2a3B9c",
  "1": "7000",
  "2": "7000",
  "3": "10750"
}
Calldata
#4configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0x0F5D2fB29fb7d3CFeE444a200298f468908cC942",
  "1": "7000",
  "2": "7500",
  "3": "10750"
}
Calldata
#5configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0x9f8F72aA9304c8B593d555F12eF6589cC3A579A2",
  "1": "6500",
  "2": "7000",
  "3": "10750"
}
Calldata
#6configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984",
  "1": "6000",
  "2": "7000",
  "3": "10750"
}
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.