daimo-eth / bulk Goto Github PK

Currently you can only submit 1 userop in the BundleBulker

It would be useful to be able to submit multiple userops, each with its own specified inflator (which can differ for ops in the same batch)

Maybe could also have another one for the case when all the ops in the batch have the same inflator, so you don't need to specify the inflator for each and you can save some calldata

Goal

Make it easy for any app or wallet to use bundle compression.

Prototypes

Prototyping with Pimlico. If all goes well, this new API endpoint would eventually become an eth_... endpoint proposed via ERC.

V0

pimlico_sendCompressedUserOperations. Takes a complete compressed bundle, passes to BundleBulker

(So the bundler is not bundling, just forwarding--but useful to test integration.)

V1 / Option A

This lets you bundle compressed ops from multiple users into a single compressed bundle.

• pimlico_sendCompressedUserOperations
  • input: CompressedOp[], where each op is {"opInflatorAddr":"0x...", "compressedOp":"0x..."}
  • output: op hashes, + optionally the containing bundle tx hash
  • suggested semantics...
    • loop thru ops
      • inflate each one calling the provided opInflatorAddr.
      • validate op using normal op validation
      • get inflator ID from Pimlico's PerOpInflator by calling inflatorToID(opInflatorAddr)
      • ...if inflatorID is 0, register the op inflator on your PerOpInflator first
    • finally, submit a bundle to BundleBulker

Whenever you want to change your beneficiary address, set the beneficiary on your PerOpInflator.

If you ever observe a submitted bundle revert (and rule out bundler errors such as not passing enough gas), it means one of the inflators changed its behavior between (validation offchain call to inflate) and (onchain submit) a second or two later.

Could temporarily flag/block API users that do this.

V1 / Option B

Same as above, but with a pimlico_sendCompressedUserOp singular. (If sending multiple ops, user just calls more than once.)

Separately, as an optimization, it's possible to do the inflator-registering and bundle-submitting in a single atomic multicall.

V1 / Option C

User is responsible for registering their own IOpInflator with bundler's PerOpInflator ahead of time. Then,

• pimlico_sendCompressedUserOp(uint256 opInflatorId, byte[] compressedOp)
  • as above, but skip the steps related to registering an op inflator
  • instead, just look up an existing op inflator via idToInflator(opInflatorID), then use its inflate(), then validate the resulting UserOp

Goal

• Compress our common-case Daimo 4337 bundle from ~1.5kb to ~350bytes
• See how much we save on fees

Steps

• Deploy to Base Goerli. Done. Generic BundleBulker, example DaimoTransferInflator
• Manual testnet integration. Submit compressed bundles from sendUserOp in daimo-api.
• Pimlico testnet integration.
• Pimlico mainnet
• Live

it might be a nice affordance to put the compress function in a solidity view function

• as a bundler you can then simulate the corresponding compress function yourself for a userop without any custom code from developer
  • can add bundle compression without any developer involvement
• can unit/fuzz test compress and inflate against each other in solidity

From Kristof