KVORUM
aaveSource: Aave governor v2 · #81

Risk Parameter Updates for Aave Arc (Fireblocks) 2022-05-26

defeatedJun 11, 2022, 05:31 AM UTCby680x683a…6c02

01Summary

AISummary by Kvorumclaude-haiku-4-5

This AIP adjusts risk parameters (LTV and Liquidation Threshold) for one asset on Aave Arc (Fireblocks) to align with the community-chosen Moderate risk level. Gauntlet's simulations indicate increasing USDC collateral efficiency does not meaningfully increase insolvency risk, as most borrowing is collateralized by the same asset being borrowed.

Type
parameter change

Key changes

  • Increase LTV (Loan-to-Value) for USDC collateral on Aave Arc to improve capital efficiency(medium)
  • Adjust Liquidation Threshold for USDC collateral on Aave Arc(medium)

Notable concerns

  • Risk parameter changes are based on agent-based simulations that depend on daily-changing market data; effectiveness depends on model accuracy
  • Current Value at Risk on Aave Arc is $0, but this could change as lending market usage grows
Contracts0x311Bb771e4F8952E6Da169b425E7e92d6Ac457560x4e1c7865e7BE78A7748724Fa0409e88dc14E67aA
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

396 words

Simple Summary

This AIP proposes adjusting two (2) total risk parameters, including LTV and Liquidation Threshold, across one (1) Aave Arc (Fireblocks) asset.

Abstract

This proposal is a batch update of risk parameters to align with the Moderate risk level chosen by the Aave community.

These parameter updates represent Gauntlet's first set of parameter updates for the Aave Arc market.

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.

Aave Arc (Fireblocks) Parameter Changes Specification

Our simulation platform indicates that increasing the capital efficiency of USDC collateral does not meaningfully increase the risk of insolvencies. Note that, on our dashboard, the Value at Risk (VaR) metric for Aave Arc is currently $0. This low risk of insolvencies is reflective of the fact that the majority of borrowing on the platform is collateralized by the same asset as the assets being borrowed. As lending market usage grows, our platform will continue to ingest up-to-date data, re-run risk simulations, and make future parameter change recommendations.

Risk Dashboard

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

Implementation

The proposal sets the 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.

By approving this proposal, you agree that any services provided by Gauntlet shall be governed by the terms of service available at gauntlet.network/tos.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Minor discrepancy

The proposal describes a routine Gauntlet risk-parameter update: adjusting LTV and Liquidation Threshold for one Aave Arc asset (USDC) via configureReserveAsCollateral on the LendingPoolConfigurator. Decoding the single on-chain action (a governance queue() call) shows an inner call to configureReserveAsCollateral(USDC, ltv=87.50%, liquidationThreshold=90.00%, liquidationBonus=4.5%). This matches the described intent — one asset, LTV and LT changes — and the extra liquidationBonus parameter is a mechanical requirement of the function signature rather than a hidden strategic change, so it is only a minor omission. However, the address cited in the Implementation section (0x311Bb...5756) as the LendingPoolConfigurator does not match the actual target address embedded in the calldata (0x4e1c7865e7BE78A7748724Fa0409e88dc14E67aA). This is a meaningful discrepancy for anyone trying to independently verify the call, though it does not appear to redirect funds or change control, and could plausibly be a copy-paste error in the description rather than malicious intent. Given the core financial parameters align with the stated intent and only the target-address citation is inconsistent, I classify this as a minor discrepancy with medium confidence, since the description's numeric detail is limited and I cannot independently confirm which address is canonically correct for the Aave Arc LendingPoolConfigurator.

Discrepancies

  • mediumtarget mismatch

    The description states that configureReserveAsCollateral will be called on a LendingPoolConfigurator at address 0x311Bb771e4F8952E6Da169b425E7e92d6Ac45756, but the decoded calldata actually targets a different address, 0x4e1c7865e7BE78A7748724Fa0409e88dc14E67aA, for the inner call. This could be a documentation typo referencing the wrong configurator address, but it means the address a delegate would use to verify the call does not match what actually executes.

    “calling `configureReserveAsCollateral` on the `LendingPoolConfigurator` contract at `0x311Bb771e4F8952E6Da169b425E7e92d6Ac45756`”

  • lowomitted in description

    The calldata also sets a liquidationBonus value (10450, i.e. a 4.5% bonus) as part of the configureReserveAsCollateral call, which the description does not mention at all (it only discusses LTV and Liquidation Threshold as the two parameters being changed).

    “adjusting two (2) total risk parameters, including LTV and Liquidation Threshold”

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
#0queue(address[],uint256[],string[],bytes[],bool[])chain 0x1
Target
0xace1…1218
Value
0 wei
Function
queue(address[],uint256[],string[],bytes[],bool[])
Arguments
{
  "values": [
    "0"
  ],
  "targets": [
    "0x4e1c7865e7BE78A7748724Fa0409e88dc14E67aA"
  ],
  "calldatas": [
    "0x7c4e560b000000000000000000000000a0b86991c6218b36c1d19d4a2e9eb0ce3606eb48000000000000000000000000000000000000000000000000000000000000222e000000000000000000000000000000000000000000000000000000000000232800000000000000000000000000000000000000000000000000000000000028d2"
  ],
  "signatures": [
    ""
  ],
  "withDelegatecalls": [
    false
  ]
}
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.