Proposal Updates Jan 21st
Proposals 522 and 523 have been reviewed, and no issues were found.
Proposals 524, 525, 526, 527, and 528 have been reviewed, and no issues were found.
Note that seatbelt simulations fail for proposals 524 and 525 due to message passing to Ronin. Price registries are not updated properly in the simulation environment, causing the simulations to fail. We’re closely monitoring these proposals and expect them to be executable on-chain when the price registries are up-to-date.
Proposals 524 and 525 are currently not executable. ETH-nominated fees for message passing to Ronin have increased, exceeding the hardcoded fee paid by the proposals. As the proposals are not time-sensitive, we will wait about a week to see if the fees normalize and the proposals can be executed. Otherwise, updated proposals will be resubmitted.
Proposal 529 has been reviewed, and no issues were found.
Proposals 530, 531, 532, 533 and 534 have been reviewed and no issues were found.
Proposals 535, 536, 537 and 538 have been reviewed and no issues were found.
Proposals 539, 540, 541, 542, 543 and 544 were reviewed and no issues were found. Proposals 539 and 540 are resubmissions of 524 and 525, with the only difference being that the required fee is paid in GHO instead of ETH, making them resistant to unexpected market movements.
Proposal 546 was reviewed and no issues were found. Proposal 545 was cancelled due to a missing description.
Proposals 547 and 548 have been reviewed and no security issues were found.
Note on Proposal 548: The supply cap update for weETH on the USDS comet included in this proposal will not take effect upon execution, as no comet upgrade is triggered afterward. Gauntlet is aware of this and has determined that canceling the proposal is unnecessary since there are no security implications.
Proposal 549 has been reviewed and no issues were found. Note that the proposal addresses the minor issue of 548.
Proposals 550 and 551 were reviewed and no issues were found.
Notes:
We are working on a post-mortem for the redirect incident and will publish it soon.