Multi Owned ECDSA Validation Module

[filmakarov]

Summary

Allows having several owners, each one of them can independently sign a userOp.

Related Issue

Change Type

• New Feature

Checklist

• My code follows this project's style guidelines
• I've reviewed my own code
• I've added comments for any hard-to-understand areas
• I've updated the documentation if necessary
• My changes generate no new warnings
• I've added tests that prove my fix is effective or my feature works
• All unit tests pass locally with my changes
• Any dependent changes have been merged and published

Additional Information

• Requested by Customer.
• They agreed to use it unaudited.

For the sake of saving time, only the core functionality is tested and only via Bundler (to ensure the new storage structure complies with 4337 restrictions).

❓ Need to decide do we want to audit it and release it publicly.

[Aboudjem]

could be swapped if the first value is always true and the second is always false:
similarly to this

uint256 a = 1;
uint256 b = 2;

(a, b) = (b, a);

[filmakarov]

interesting :) is it cheaper?

[filmakarov]

if not, I would suggest not doing this as in this exact case it makes things less readable

(_smartAccountOwners[owner][smartAccount], _smartAccountOwners[newOwner][smartAccount]) = (_smartAccountOwners[newOwner][smartAccount], _smartAccountOwners[owner][smartAccount]);

looks bulky

[Aboudjem]

yes it's cheaper but agree that it makes it very difficult to read 😅 let's discuss when we will focus on optimization

[Aboudjem]

🚀🚀🚀