Skip to main content

Batched Transactions on EVM: Execute Multiple Operations

Batched transactions combine multiple blockchain operations into a single transaction. Instead of submitting separate transactions (each with its own gas cost and confirmation), you execute everything atomically in one go.
Batching is enabled by smart contract wallets (account abstraction).
Gas savings example:
Using AbstractJS SDK with MEE:
MEE (Modular Execution Environment) provides all the batching capabilities of ERC-4337 bundlers and paymasters, plus cross-chain orchestration. Use MEE instead of configuring bundlers and paymasters separately.
You can batch any combination of EVM operations:Common batching patterns:Example: Multi-token transfer
Atomic execution means all operations succeed or all fail. There’s no partial state.Why this matters:
Biconomy ensures atomicity:
Yes! Use runtime values to reference outputs from earlier operations:
The runtime.outputOf(0) is resolved at execution time with the actual value from the first operation.
Batch size is limited by:
  1. Block gas limit: Total gas must fit in a block
  2. Bundler limits: Typically 5-10M gas per UserOperation
  3. Practical limits: More operations = higher failure risk
Guidelines:Best practices:
Default behavior: Atomic revert
For non-critical operations, use conditional execution:
Pre-validate operations:
Yes! Cross-chain batching is possible with Biconomy’s orchestration:
See Multi-Chain Execution for details.
Example 1: DeFi Yield Optimization
Example 2: NFT Marketplace Listing
Example 3: Payroll Distribution

Learn more

Multi-Chain Execution

Batch across multiple chains

Onchain Orchestration

Coordinate complex workflows