Content
@
0 reply
0 recast
0 reaction
will
@w
because of user op validation limitations, particularly re storage, a 4337 account can’t be an owner / signer for another 4337 account and in general smart contract ownership/signing via 1271 won’t work.
1 reply
0 recast
2 reactions
Adam Egyed
@adamegyed
One way these flows are handled is to start the UserOp from the parent smart accounts, and set the target of the `execute` call to the child account. The child account can validate that the caller is an owner in the execution phase.
0 reply
1 recast
0 reaction
Adam Egyed
@adamegyed
Unfortunately, this doesn't work with multisigs where one signer is a smart account, not sure if there's a solution for that yet.
0 reply
0 recast
0 reaction
