Smart Account Support

[alexmmueller]

We currently return transaction data to the user in the form of an EOA. We also enable support for SmartAccounts via UserOps.

Requirements:

• Simple: Simply convert a tx -> userOp so a paymaster can pay on behalf of the user.
• Hard: For token transfers, batch approve + transfer functions into the transaction

Blockers:
There is no standard interface for building userOps and we need to monitor a few EIPs to do this correctly.

• eip7677
• eip7679

[GregTheGreek]

@mpetrunic Updated a bit

[mpetrunic]

I don't think we are blocked for simple solution as we can follow 4337?
Also simple solution is probably not that much work.

[GregTheGreek]

Agreed! Let's do simple 4337

Chatted with Sequence, sending approvals + transactions as vanilla ERC20 (EOA style) works for them since the bundler handles it. So B3 SCW should be trivial

[GregTheGreek]

TBH I wonder if we need to do this at the API level, or we do this at the JS level? We provide all the necessary information, and you could use something like permissionless.js or native SCW provider to just handle everytihng

[mpetrunic]

Yeah, I think it's best if we do it in sdk, to not slow down api with userOps which may not be used