KVORUM
aaveSource: Aave governor v2 · #74

Risk Parameter Updates 2022-05-05

canceledMay 14, 2022, 12:56 AM UTCby680x683a…6c02

01Summary

AISummary by Kvorumclaude-haiku-4-5

Batch update of risk parameters (LTV, Liquidation Threshold, Liquidation Bonus) across 5 Aave V2 assets (BAL, DAI, stETH, xSUSHI, YFI) to align with the community-chosen Moderate risk level and optimize the protocol's balance between insolvencies, liquidations, and borrow usage.

Type
parameter change

Key changes

  • BAL: LTV adjusted to 62%, Liquidation Threshold to 70%, Liquidation Bonus to 10.7%(medium)
  • DAI: LTV adjusted to 77%, Liquidation Threshold to 85%, Liquidation Bonus to 10.5%(medium)
  • stETH: LTV adjusted to 76%, Liquidation Threshold to 77%, Liquidation Bonus to 10.75%(medium)
  • xSUSHI: LTV adjusted to 47%, Liquidation Threshold to 65%, Liquidation Bonus to 10.8%(medium)
  • YFI: LTV adjusted to 46%, Liquidation Threshold to 68%, Liquidation Bonus to 10.75%(medium)

Notable concerns

  • These are risk parameter adjustments that will affect collateralization requirements and liquidation dynamics across multiple assets
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

323 words

Simple Summary

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

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.

Gauntlet's parameter recommendations are driven by an optimization function that balances 3 core metrics: insolvencies, liquidations, and borrow usage. Parameter recommendations seek to optimize for this objective function. Our agent-based simulations use a wide array of varied input data that changes on a daily basis (including but not limited to asset volatility, asset correlation, asset collateral usage, DEX / CEX liquidity, trading volume, expected market impact of trades, and liquidator behavior). Gauntlet's simulations tease out complex relationships between these inputs that cannot be simply expressed as heuristics. The individual collateral pages on the Gauntlet Risk Dashboard cover other key statistics and outputs from our simulations that can help with understanding interesting inputs and results related to our simulations.

Specification

Our recent market downturn report showed that many collaterals are resilient to insolvencies, as our simulation models have predicted. Gauntlet's simulation engine will continue to adjust risk parameters to drive increases in capital efficiency while maintaining protocol risk at safe levels.

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 Kvorumclaude-sonnet-5
Consistent

The description states this proposal batches risk-parameter (LTV, Liquidation Threshold, Liquidation Bonus) updates for five Aave V2 assets via `configureReserveAsCollateral` on the LendingPoolConfigurator contract at 0x311Bb771e4F8952E6Da169b425E7e92d6Ac45756. The decoded calldata shows exactly five calls to `configureReserveAsCollateral` on that same contract address, each setting LTV, Liquidation Threshold, and Liquidation Bonus values for a distinct asset — a one-to-one match with the described action type, function, target contract, and asset count. The specific numeric parameter values are not enumerated in the description (it defers to a linked forum post for the full parameter table), so there is no basis to flag value mismatches; this is a reasonable summarization typical of Aave Gauntlet risk-parameter proposals. The claim of 'nine (9) total risk parameters' changed versus the 15 possible (3 params × 5 assets) could suggest some values are actually unchanged from current state, but without access to the pre-proposal on-chain values we cannot verify whether this underrepresents or accurately reflects the actual deltas — this is a case where confidence is insufficient to raise a discrepancy, so it is not flagged. No omitted actions, no extra claims, and no target or value mismatches were found in what can be verified. Overall the description and calldata align well and this proposal appears consistent with standard Gauntlet Aave V2 risk-parameter update proposals.

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

04Actions

5 total
#0configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0xba100000625a3754423978a60c9317c58a424e3D",
  "1": "6200",
  "2": "7000",
  "3": "10700"
}
Calldata
#1configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0x6B175474E89094C44Da98b954EedeAC495271d0F",
  "1": "7700",
  "2": "8500",
  "3": "10500"
}
Calldata
#2configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0xae7ab96520DE3A18E5e111B5EaAb095312D7fE84",
  "1": "7600",
  "2": "7700",
  "3": "10750"
}
Calldata
#3configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0x8798249c2E607446EfB7Ad49eC89dD1865Ff4272",
  "1": "4700",
  "2": "6500",
  "3": "10800"
}
Calldata
#4configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0x0bc529c00C6401aEF6D220BE8C6Ea1667F6Ad93e",
  "1": "4600",
  "2": "6800",
  "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.