Weekly Development Updates (6/13/24)

[CodesMcCabe]

• Finalize and launch v0.8 by September
  • Draft proposal planned to be completed by the end of June followed by 1 month of testing and iterating
• Allow per-hook data to be passed into pre-validation hooks feat: [v0.8-develop] per validation hook data reference-implementation#66
  • To better compose plugins, it is useful to allow extra data to be passed to hooks, to prevent having to do non-standard calldata encoding or require re-defining execution functions.
  • This is necessary for certain types of permissions-enforcing hooks to be used in a composable way – for example, an access control plugin implemented via a merkle tree requires proofs to be passed along with each call.
• Add an allowlist sample hook & refactor test base feat: [v0.8-develop] Add allowlist sample hook, refactor test base reference-implementation#70
  • To provide better context for how pre-validation hooks should be used, it would help to provide some real use cases. A simple case is an allowlist plugin - limiting the addresses, and possibly the selectors, of the targets of execute and executeBatch when using a specific validation function.
  • Added a fuzz test suite and simplified existing and new tests.