KVORUM
aaveSource: Aave governor v2 · #237

BUSD Offboarding Plan Part II

executedJun 9, 2023, 02:55 AM UTCby320x329c…3ed4

01Summary

AISummary by Kvorumclaude-haiku-4-5

Aave proposal to offboard BUSD from Aave V2 Ethereum by modifying the interest rate strategy to increase borrowing costs (raising slope 2 from 200% to 300% and lowering uOptimal from 20% to 2%) and withdrawing Protocol Owned Liquidity aBUSD from the pool to force remaining borrowers to repay or face liquidation.

Type
parameter change

Key changes

  • Decrease uOptimal (optimal utilization ratio) from 20% to 2% for BUSD reserve(high)
  • Increase slope 2 (interest rate curve above optimal utilization) from 200% to 300% for BUSD reserve(high)
  • Withdraw Protocol Owned Liquidity aBUSD from Aave V2 Ethereum pool to increase utilization ratio(high)
  • Base rate remains unchanged at 3% and slope 1 remains unchanged at 7%(low)
  • Reserve factor remains unchanged at 99.9%(low)

Notable concerns

  • Proposal targets inactive or unaffected BUSD debt holders to force repayment or liquidation through unsustainable borrowing positions
  • Potential protocol bad debt risk from BUSD/Paxos situation necessitates concentrated offboarding effort
  • Withdrawn BUSD will be held in collector contract pending separate future AIP for asset swap
Contracts0x4Fabb145d64652a948d72533023f6E7A623C7C53AaveV2Ethereum.POOL_CONFIGURATORAaveV2Ethereum.COLLECTORAaveV2Ethereum.POOL
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

333 words

Simple Summary

This AIP proposes to change the InterestRate Strategy the BUSD reserve on the Aave V2 Ethereum pool and withdraw POL aBUSD from Aave V2 Ethereum Pool

Motivation

Please refers to the first part of the BUSD offboarding plan for more context.

The first part of the plan was a success, driving out liquidity and incentivizing active users to repay their debt and move their position to other stablecoins.

The remaining vBUSD debt holders seem to be inactive or unaffected by high rates, due to the time-sensitive nature of BUSD/Paxos situation and the potential risk of protocol bad debt.

This second part of the offboarding plan will concentrate efforts on creating unsustainable positions for remaining borrowers to either motivate them enough to repay or reach liquidation thresholds.

Both actions are proposed to be performed :

  1. modify risk parameters to "force" slope 2 interest rate curve and increase slope 2 aggressiveness
  2. remove Protocol Owned Liquidity aBUSD to increase the utilization ratio of BUSD and increase the cost of open positions.

Specification

Ticker: BUSD (BUSD)

Contract Address: 0x4Fabb145d64652a948d72533023f6E7A623C7C53

The offboarding plan will be carried out With the current AIP with the following parameters:

  • Decrease uOptimal from 20% to 2%.
  • reserveFactor remains unchanged at 99.9%.
  • base rate remains unchanged at 3%.
  • slope 1 remains unchanged at 7%.
  • Increase slope 2 from 200% to 300%.

Withdrawal of aBUSD from the collector contract. The BUSD will be kept as such in the collector contract, and a separate AIP will organize the swap of BUSD into other assets at a later stage.

contract AaveV2EthBUSDIR_20230602 is IProposalGenericExecutor {
  address public constant INTEREST_RATE_STRATEGY = 0xB28cA2760001c9837430F20c50fD89Ed56A449f0;

  function execute() external {
    AaveV2Ethereum.POOL_CONFIGURATOR.setReserveInterestRateStrategyAddress(
      AaveV2EthereumAssets.BUSD_UNDERLYING,
      INTEREST_RATE_STRATEGY
    );

    uint256 aBUSDBalance = IERC20(AaveV2EthereumAssets.BUSD_A_TOKEN).balanceOf(
      address(AaveV2Ethereum.COLLECTOR)
    );
    uint256 availableBUSD = IERC20(AaveV2EthereumAssets.BUSD_UNDERLYING).balanceOf(
      AaveV2EthereumAssets.BUSD_A_TOKEN
    );
    AaveV2Ethereum.COLLECTOR.transfer(
      AaveV2EthereumAssets.BUSD_A_TOKEN,
      address(this),
      aBUSDBalance > availableBUSD ? availableBUSD : aBUSDBalance
    );
    AaveV2Ethereum.POOL.withdraw(
      AaveV2EthereumAssets.BUSD_UNDERLYING,
      type(uint256).max,
      address(AaveV2Ethereum.COLLECTOR)
    );
  }
}

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Consistent

The decoded on-chain data contains a single action: a call to execute() on an external payload contract, which is the standard Aave governance execution pattern (IProposalGenericExecutor). The actual logic — setting a new interest rate strategy for BUSD and withdrawing aBUSD from the Collector — is embedded in the payload contract's bytecode and is not separately decoded in the provided calldata rows. The proposal description includes the full Solidity source of this exact payload contract (AaveV2EthBUSDIR_20230602), which implements setReserveInterestRateStrategyAddress for BUSD and the aBUSD withdrawal/transfer logic exactly as described in the Specification (uOptimal 20%→2%, slope2 200%→300%, reserveFactor/base/slope1 unchanged, and withdrawal of aBUSD balance capped by available liquidity). Since the single decoded action matches the expected pattern for this type of governance payload and the source code faithfully corresponds to the described changes, I find no evidence of a mismatch. However, because the calldata itself does not expose the granular interest-rate parameters or transfer amounts (they are only verifiable via the linked source code, not the decoded action), confidence is medium rather than high — a fully rigorous review would require confirming the deployed bytecode at the target address matches the provided source.

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
0x15e4…c23e
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.