Skip to content

Latest commit

 

History

History
88 lines (52 loc) · 2.66 KB

237-aave-v2-ethereum-busd-offboarding-pt2.md

File metadata and controls

88 lines (52 loc) · 2.66 KB

Proposal 237. Aave v2 Ethereum - BUSD off-boarding pt 2


Voting link

https://app.aave.com/governance/proposal/?proposalId=236


Governance forum discussion

https://governance.aave.com/t/arfc-busd-offboarding-plan-part-ii/13048


BGD analysis


Proposal types

🔧 📊 params-update

💸 funds-release


Context

This proposal proceeds with another phase of the off-boarding of BUSD on Aave v2 Ethereum, by modifying its rate strategy and withdrawing the aBUSD held by the Collector to BUSD.


Proposal creation

Transaction: https://etherscan.io/tx/0xe1eb60141520672a09481f7e602fab6f62f20de26e3ac9dffd0ac2bdf6027da9

- id: 237
- creator: 0x329c54289ff5d6b7b7dae13592c6b1eda1543ed4
- executor: 0xee56e2b3d491590b5b31738cc34d5232f378a8d5
- targets: [0x15e4c34a4a3cd147856cc6a293e25ea5385ec23e]
- values: [0]
- signatures: [execute()]
- calldatas: [0x]
- withDelegatecalls: [true]
- startBlock: 17420650
- endBlock: 17439850
- strategy: 0xb7e383ef9b1e9189fc0f71fb30af8aa14377429e
- ipfsHash: 0x682d51cb497c3e479740500d2f8cf128996a1301192c59d68bf7d69000d7ca46

Aave Seatbelt report

Ethereum

https://github.com/bgd-labs/seatbelt-for-ghosts/blob/main/reports/Aave/0xEC568fffba86c094cf06b22134B23074DFE2252c/237.md


Technical analysis

The proposal payload does the following:

  1. Replace the interest rate strategy with a new one with the following changes:
  • Optimal usage point: 20% -> 2%
  • Variable rate slope 2: 200% -> 300%
  • Stable rate slope 2: 2000% -> 3000%
  1. Withdraw the current balance of aBUSD (~300'000 BUSD, but can change depending on available liquidity) to BUSD to the Aave Collector, common for Aave v2 and v3. The payload properly checks available liquidity to avoid any kind of revert.

BGD validations

✅ The code on the proposal payload corresponds to the proposal specification.

✅ The proposal includes a proper tests suite, checking all necessary post-conditions.

✅ BGD reviewed the payload before the proposal was submitted.

✅ Multiple payloads used via delegatecall

✅ BGD reviewed the procedure followed to submit the proposal.