Weekly Development Updates (5/23/24)

[CodesMcCabe]

• Experimental support for multiple validation functions feat: [v0.8-develop, experimental] multi validation in user op signature [5/N] reference-implementation#62

  • Allows switching between different validation functions using a field in the userOp signature for userOp validation and a calldata field for runtime validation.
  • This change no longer requires a ‘default’ or ‘primary’ validation per selector. Whenever a validation function needs to run, it is specified by the caller and checked by the account to be an installed validator for the given function.
  • Additional work to be done in this area:
    • Change how pre-validation hooks are assigned
    • Merge the signature validator & regular validation assignment during install
    • Introduce per-hook/per-validation data
    • External call filtering with hooks
  • The group deeply discussed pre-validation hook assignment and concluded that pre-validation hooks should limit gas spend, everything else should be validated in execution hooks. It should be noted that if execution hooks don’t get signer context, we can’t enforce spend limits

• Review of the [ERC-6900 v0.8 roadmap](https://github.com/orgs/erc6900/projects/1/views/1)

  • We urge the community to review the roadmap and provide feedback on prioritization or reach out to get involved with development.

• We are considering adding executeUserOp to ERC-6900 feat: add execute user op reference-implementation#57

  • This change would allow all ERC-6900 accounts to pass context from validation to execution via calldata.