Skip to content

Latest commit

 

History

History
219 lines (148 loc) · 10.5 KB

v3-178-aave-v3-multichain-v3.20-upgrade-liquid-EMode.md

File metadata and controls

219 lines (148 loc) · 10.5 KB

Proposal 178. v3.20 Upgrade to Liquid EMode and StableDebt Removel.


Voting link

https://vote.onaave.com/proposal/?proposalId=178


Governance forum discussion

https://governance.aave.com/t/bgd-aave-v3-2-liquid-emodes/19037


Payloads


Certora analysis


Proposal types

📜🔺 contract upgrade

💰 🧾 asset transfer


Context

The Aave 3.2 upgrade proposal aims to introduce significant improvements to the Aave protocol. The primary feature of this upgrade is the debut of Liquid eModes, which enhances the flexibility of Aave’s eModes by allowing assets to be listed in multiple categories and providing granular control over which assets can be used as collateral or borrowed. Additionally, the proposal finalizes the deprecation of stable borrowing by removing its residual artifacts, streamlining the protocol to reduce gas consumption and optimize code efficiency. The upgrade also includes provisions for reimbursing security audit costs, ensuring the protocol maintains its high standards of safety.


Proposal creation

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

- proposalId: 178
- creator: 0xf71fc92e2949ccf6a5fd369a0b402ba80bc61e02
- accessLevel: 1
- ipfsHash: 0x2e51e731f54ed0b5a0e3133b6f0de76c24ddf43e74c2c60ede057326ef7ae2d7

createProposal() parameters

{
  "payloads": [ 
    { 
      "chain": "1", 
      "accessLevel": "1", 
      "payloadsController": "0xdAbad81aF85554E9ae636395611C58F7eC1aAEc5", 
      "payloadId": "184" 
    }, 
    { 
      "chain": "137", 
      "accessLevel": "1", 
      "payloadsController": "0x401B5D0294E23637c18fcc38b1Bca814CDa2637C", 
      "payloadId": "84" 
    }, 
    { 
      "chain": "43114", 
      "accessLevel": "1", 
      "payloadsController": "0x1140CB7CAfAcC745771C2Ea31e7B5C653c5d0B80", 
      "payloadId": "56" 
    }, 
    { 
      "chain": "10", 
      "accessLevel": "1", 
      "payloadsController": "0x0E1a3Af1f9cC76A62eD31eDedca291E63632e7c4", 
      "payloadId": "52" 
    }, 
    { 
      "chain": "42161", 
      "accessLevel": "1", 
      "payloadsController": "0x89644CA1bB8064760312AE4F03ea41b05dA3637C", 
      "payloadId": "54" 
    }, 
    { 
      "chain": "1088", 
      "accessLevel": "1", 
      "payloadsController": "0x2233F8A66A728FBa6E1dC95570B25360D07D5524", 
      "payloadId": "26" 
    }, 
    { 
      "chain": "8453", 
      "accessLevel": "1", 
      "payloadsController": "0x2DC219E716793fb4b21548C0f009Ba3Af753ab01", 
      "payloadId": "39" 
    }, 
    { 
      "chain": "100", 
      "accessLevel": "1", 
      "payloadsController": "0x9A1F491B86D09fC1484b5fab10041B189B60756b", 
      "payloadId": "33" 
    }, 
    { 
      "chain": "534352", 
      "accessLevel": "1", 
      "payloadsController": "0x6b6B41c0f8C223715f712BE83ceC3c37bbfDC3fE", 
      "payloadId": "24" 
    }, 
    { 
      "chain": "56", 
      "accessLevel": "1", 
      "payloadsController": "0xE5EF2Dd06755A97e975f7E282f828224F2C3e627", 
      "payloadId": "23" 
    }, 
    { 
      "chain": "324", 
      "accessLevel": "1", 
      "payloadsController": "0x2E79349c3F5e4751E87b966812C9E65E805996F1", 
      "payloadId": "6" 
    }, 
  ], 
  "votingPortal": "0x9b24C168d6A76b5459B1d47071a54962a4df36c3", 
  "ipfsHash": "0x2e51e731f54ed0b5a0e3133b6f0de76c24ddf43e74c2c60ede057326ef7ae2d7" 
}

Aave Seatbelt report

Proposal report

https://github.com/bgd-labs/seatbelt-gov-v3/blob/main/reports/proposals/178.md

Payload reports


Technical analysis

In the audit of the Aave 3.2 upgrade proposal, the primary focus was on verifying the correct implementation of Liquid eModes. The payload logic was thoroughly reviewed to ensure it allows for the increased flexibility of Liquid eModes, enabling assets to be listed in multiple eModes and offering more granular control over collateralization and borrowing. While the reset of eModeCategory bits in the reserve data storage was considered optional, this was not performed, and it is acceptable in the current context.

Secondary checks confirmed that the stableDebtToken address was correctly set to 0 on all assets, completing the final deprecation of stable borrowing. The audit also verified the transfer of 76,000 GHO to the BGD-controlled address for reimbursement of security procedure costs.

In addition to these checks, we confirmed the deployment included all necessary components, such as the new configuration engine, pool configurator, logic libraries, pool implementation, and both pool data provider and UI pool data provider. A thorough comparison of chain code diffs ensured consistency across implementations, and the seatbelt checks confirmed the bitmap configuration was correct.

Overall, these checks validate that the Aave 3.2 upgrade is correctly implemented and ready for deployment.


The proposal is consistent with the description on both Snapshot and the governance forum.


Certora 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.

✅ Certora reviewed the procedure followed to submit the proposal.