Skip to content

Latest commit

 

History

History
85 lines (49 loc) · 2.69 KB

289-treasury-management-acrv-usdt-otc.md

File metadata and controls

85 lines (49 loc) · 2.69 KB

Proposal 289. Treasury Management - swap USDT from treasury to aCRV


Voting link

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


Governance forum discussion

https://governance.aave.com/t/arfc-acquire-crv-with-treasury-usdt/14251


BGD analysis


Proposal types

🏦 treasury


Context

This proposal executes a first-of-its-kind swap of USDT from the Aave Ethereum Collector to aCRV, which the USDT atomically used to repay debt of USDT of address 0x7a16ff8270133f063aab6c9977183d9e72835428.


Proposal creation

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

- id: 289
- creator: 0x329c54289ff5d6b7b7dae13592c6b1eda1543ed4
- executor: 0xee56e2b3d491590b5b31738cc34d5232f378a8d5
- targets: [0x8eda0756f0d7dffc8488a19cf3b949bebd132191]
- values: [0]
- signatures: [execute()]
- calldatas: [0x]
- withDelegatecalls: [true]
- startBlock: 17871434
- endBlock: 17890634
- strategy: 0xb7e383ef9b1e9189fc0f71fb30af8aa14377429e
- ipfsHash: 0x03621fdd5b0f4431c88e43b154b7192c0dd0ab0c0cbecb2d6336c49a2a6bcc54

Aave Seatbelt report

Ethereum

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


Technical analysis

We have verified the proposal payload does the following:

  1. Transfer from the counterparty address 5'000'000 aCRV, to the Aave Ethereum Collector. This will depend on the counterparty having given approval in advance to the Aave Governance Level 1 Executor (Short Executor).

  2. Use 2'000'000 USDT from the Aave Ethereum Collector to repay same value of debt of behalf the counterparty address, with ~20'100'000 USDT outstanding borrowings at the moment.


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.

✅ Only one payload used via delegatecall

✅ BGD reviewed the procedure followed to submit the proposal.