Feature

PodExecutorV2

Fixes a bug in the PodExecutor.sol whereby the executeBatch() method was not correctly exposed. Also updates an event to emit the proposalId rather than a custom hash of the data being executed.

Adds much more extensive testing, with most state variables that are touched being tested.

Benefit of a PodExecutor contract vs making EXECUTOR an open role

The main benefit using a PodExecutor contract vs making the EXECUTOR role an open role and publicly available is that the PodExecutor is pauseable. It will allow the Guardian to pause the contract and prevent execution if an issue is found with a queued transaction.

TODO

• Add test for proposalId emitted in event
• Deploy new contract and validate
• e2e tests for execute() and executeBatch()
• Deprecate old EXECUTOR
• TC proposal to grant EXECUTOR role to this contract
• Verification that a proposal can be batch executed through this

PR Checklist - Feature (Proposal)

• All Tests Passing
• Proposal Added to ProposalsConfig
• Fork Block Correct
• Remove Any .only's on Tests
• Update Documentation If Needed
• Update Roles Config
• Proposal Submitted