ExecuteUserOp support #17
Description
// ExecuteUserOp is ambiguous and not supported atm
// Reason: since Smart Account implementation is free to call whatever it wants inside
// executeUserOp, we can never be sure which part of callData is going
// to be executed if any at all, so we can't validate it with confidence
//
// However, using executeUserOp is important functionality and can be crucial for
// many usecases, so not supporting it is very limiting
//
// TODO: discuss it with auditors and potentially reconsider supporting the executeUserOp
// with stating in the module documentation that it expects the actual calldata to be appended
// to the executeUserOp.selector in the userOp.callData, otherwise it won't work as expected
Other solution would be to standardize the layout for calldata of the ExecuteUserOp in ERC7579
So we always know where's the calldata that will actually be used for execution.