KVORUM
aaveSource: Aave governor v2 · #70

Risk Parameter Updates 2022-04-22

executedApr 29, 2022, 10:09 PM UTCby680x683a…6c02

01Summary

AISummary by Kvorumclaude-haiku-4-5

Batch update of risk parameters (LTV, Liquidation Threshold, Liquidation Bonus) for 4 Aave V2 assets (SNX, stETH, UNI, USDC) to align with the community-chosen Moderate risk level and optimize capital efficiency while maintaining protocol safety.

Type
parameter change

Key changes

  • Adjust LTV, Liquidation Threshold, and Liquidation Bonus for SNX (0xC011a73ee8576Fb46F5E1c5751cA3B9Fe0af2a6F): LTV 49%, Threshold 65%, Bonus 10.75%(medium)
  • Adjust LTV, Liquidation Threshold, and Liquidation Bonus for stETH (0xae7ab96520DE3A18E5e111B5EaAb095312D7fE84): LTV 73%, Threshold 75%, Bonus 10.75%(medium)
  • Adjust LTV, Liquidation Threshold, and Liquidation Bonus for UNI (0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984): LTV 60%, Threshold 75%, Bonus 10.9%(medium)
  • Adjust LTV, Liquidation Threshold, and Liquidation Bonus for USDC (0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48): LTV 85.5%, Threshold 88%, Bonus 10.45%(medium)

Notable concerns

  • Parameter adjustments based on Gauntlet's agent-based simulations that depend on daily-changing market inputs; community should review Gauntlet Risk Dashboard for supporting analysis
  • Proposal represents continuation of regular parameter recommendations and risk trade-offs between specific 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

321 words

Simple Summary

A proposal to adjust five (5) total risk parameters, including LTV, Liquidation Threshold, and Liquidation Bonus across four (4) 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. We 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 Kvorummedium confidenceclaude-sonnet-5
Consistent

The proposal describes a batch update of Aave V2 risk parameters (LTV, Liquidation Threshold, Liquidation Bonus) for four assets, executed via configureReserveAsCollateral on the LendingPoolConfigurator contract at 0x311Bb771e4F8952E6Da169b425E7e92d6Ac45756. The decoded calldata shows exactly four calls to configureReserveAsCollateral on that same target address, each setting the three parameters (LTV, LT, LB) for a distinct asset — matching the structural claim of '4 assets' and the named function/target. The description does not specify which numeric values change (it defers to an external forum link for the full parameter list), so I cannot verify the exact figures or confirm the precise count of 'five total parameters changed' (since each call technically touches 3 slots per asset, whether all are actual changes from prior state is unknowable without querying prior on-chain state). This uncertainty is a limitation of available data rather than an inconsistency, so it is not flagged as a discrepancy per the conservative reporting guidance. Target address, function name, and asset count in the description all align with the calldata. No unexplained transfers, role grants, or off-target actions are present. Given the lack of specific numeric claims to verify in the prose, confidence is medium rather than high, but no material or severe issues are evident.

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

04Actions

4 total
#0configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0xC011a73ee8576Fb46F5E1c5751cA3B9Fe0af2a6F",
  "1": "4900",
  "2": "6500",
  "3": "10750"
}
Calldata
#1configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0xae7ab96520DE3A18E5e111B5EaAb095312D7fE84",
  "1": "7300",
  "2": "7500",
  "3": "10750"
}
Calldata
#2configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984",
  "1": "6000",
  "2": "7500",
  "3": "10900"
}
Calldata
#3configureReserveAsCollateral(address,uint256,uint256,uint256)chain 0x1
Target
0x311b…5756
Value
0 wei
Function
configureReserveAsCollateral(address,uint256,uint256,uint256)
Arguments
{
  "0": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
  "1": "8550",
  "2": "8800",
  "3": "10450"
}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total
Filter:
VoterChoice% of totalRationale
C10xc17c…64e1For103.3K0.00%—5y ago
AF0xafda…3a6eFor93.4K0.00%—5y ago
C40xc4a9…2935For92.5K0.00%—5y ago
DD0xdd45…4cc5For55.5K0.00%—5y ago
070x0703…961bFor10K0.00%—5y ago
800x80a0…2b08For161.30.00%—5y ago
A50xa519…c81bFor159.70.00%—5y ago
990x9915…5529For760.00%—5y ago
550x55e1…764cFor52.30.00%—5y ago
5B0x5b3b…7c98For51.30.00%—5y ago
5D0x5de6…ee01For47.90.00%—5y ago
FE0xfec1…abbbFor28.10.00%—5y ago
800x800e…4cc9For22.70.00%—5y ago
E50xe551…0bf7For5.20.00%—5y ago
C70xc7a3…1303For0.20.00%—5y ago
4D0x4d47…3ad9For0.10.00%—5y ago
5B0x5b90…0fa3For0.10.00%—5y ago
3C0x3cd4…1c7cFor0.10.00%—5y ago
A40xa430…810cFor0.10.00%—5y ago
420x4241…722bFor0.10.00%—5y ago
580x58c7…b43bFor0.10.00%—5y ago
360x3617…2d0bFor00.00%—5y ago
0A0x0ab7…6625For00.00%—5y ago
Showing 23

07Forum

No forum thread is confidently linked to this proposal.