- Ethereum - proposal payloads
- 📜 🔺 Contract upgrades
Deploy two stataToken GSMs using the ERC4626 implementation developed by Aave Labs to replace the existing USDC and USDT GSMs.
Transaction: 0x8aef6973496ffda646fe76d0b16b6550648c2537695d50f42a5833bc64ed7072
proposalId: 267creator: 0x57ab7ee15cE5ECacB1aB84EE42D5A9d0d8112922accessLevel: 1ipfsHash: 0xa7a224eb00be690b558352b6afcf332e5e26693a337993e4624c78ee30fb9aeb
createProposal() Parameters
{
payloads: [
{
chain: "1",
payloads_controller: "0xdAbad81aF85554E9ae636395611C58F7eC1aAEc5",
payload_id: 257,
},
],
voting_portal: "0x9b24C168d6A76b5459B1d47071a54962a4df36c3",
ipfs_hash: "0xa7a224eb00be690b558352b6afcf332e5e26693a337993e4624c78ee30fb9aeb",
access_level: 1,
}
Proposal Report
Link to Seatbelt proposal report
Payload Reports
- Ethereum - payload Seatbelt report
During review we have found out the payload set the GSMs as GHO facilitators with the wrong bucket capacities (8M instead of 16M for USDC and 16M instead of 24M) . The fix will use the Bucket Steward that can double the amount of the bucket in each transaction.
Other than that no problem have been found. The set uo=p of the GSM was done correctly and securely.
The proposal is consistent with the description on both Snapshot and the governance forum.
- ✅ 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.