Batching

What Is Batching in Crypto?

Batching is the process of grouping multiple crypto transactions, payments, messages, operations, or data items together so they can be processed, submitted, settled, or verified more efficiently.

In cryptocurrency, batching is used to reduce fees, save blockspace, improve throughput, simplify settlement, and make blockchain applications more scalable.

A batch can include many user payments in one transaction, many Layer 2 transactions in one rollup submission, many smart wallet operations in one on-chain transaction, or many settlement instructions in one protocol action.

The basic idea is simple.

Instead of sending one separate transaction for every action, a system groups related actions and submits them together.

Bitcoin payment batching is one of the oldest and clearest examples.

The Bitcoin Optech payment batching guide defines payment batching as including multiple payments in the same on-chain transaction.

Ethereum rollups also rely heavily on batching because rollup operators group many off-chain transactions and post compressed data to Ethereum.

The Ethereum optimistic rollup documentation explains that optimistic rollup operators bundle many off-chain transactions into large batches before submitting them to Ethereum.

Batching is therefore not one single feature.

It is a broad scaling pattern used across wallets, blockchains, rollups, bridges, DeFi protocols, smart accounts, and infrastructure systems.

Why Batching Matters

Batching matters because blockchain blockspace is limited and can become expensive during periods of high demand.

When each payment or operation is submitted separately, every action carries its own transaction overhead.

That overhead can include signatures, inputs, outputs, calldata, execution gas, fixed transaction fields, network propagation, and settlement cost.

Batching spreads some of that overhead across many actions.

This can lower the average cost per payment or operation.

It can also reduce congestion because fewer top-level transactions need to be included on-chain.

The Ethereum data availability documentation explains that rollup batches can represent thousands of off-chain transactions in a single Ethereum transaction, reducing base-layer congestion and user fees.

This is one reason batching is central to the rollup-centric scaling roadmap.

Batching is also important for user experience.

A wallet can combine several actions into one approval flow.

A protocol can settle many accounts together.

A payment sender can pay many recipients in one transaction instead of making users wait for many separate confirmations.

For crypto systems, batching is often the difference between a product that works only for small usage and a product that can handle real scale.

How Batching Works

Batching works by collecting multiple actions and packaging them into one larger action.

The system then submits the larger action to a blockchain, smart contract, rollup contract, bridge contract, settlement layer, or off-chain network.

Inside the batch, each individual item still needs to be represented clearly.

For example, a Bitcoin payment batch must include the right outputs for each recipient.

A rollup batch must include enough transaction data or state information for verifiers to check the result.

An ERC-4337 bundle must include multiple UserOperations and follow validation rules before submission.

The ERC-4337 specification defines bundling as the process where a bundler collects multiple UserOperations and creates a single transaction to submit on-chain.

Batching therefore has two sides.

The first side is compression or aggregation.

The second side is correct accounting for every item inside the batch.

A batch is useful only if the system can still prove, execute, refund, or settle each included action correctly.

Payment Batching

Payment batching means sending many payments inside one blockchain transaction.

This is common in UTXO-based systems because one transaction can have multiple outputs.

The Bitcoin developer transaction guide explains that each Bitcoin transaction has inputs and outputs, and outputs represent amounts that can later be spent.

A sender can create one transaction with many recipient outputs instead of creating many separate transactions.

This can reduce the average fee per payment because shared transaction data is paid only once.

Payment batching is especially useful for services, payroll systems, mining payouts, airdrop-style distributions, treasury operations, and high-volume withdrawal systems.

For example, a company that needs to pay 100 users can create one transaction with 100 outputs instead of 100 separate transactions.

The total transaction may be larger than one single payment.

However, it is usually smaller than 100 separate payments combined.

This is why batching can save blockspace and fees.

Batching in Bitcoin

Bitcoin batching is mostly about using the transaction structure efficiently.

The Bitcoin transaction reference states that a transaction may have multiple inputs and outputs.

This structure allows one transaction to spend selected inputs and create many outputs for different recipients.

Bitcoin Optech explains that batching splits the cost of creating a transaction, spending inputs, and creating change across many payments.

This can make batching one of the most practical fee-saving tools for high-frequency Bitcoin spenders.

However, batching also creates planning trade-offs.

A sender may need to wait until enough payments are ready to create an efficient batch.

That waiting period can introduce payout delay.

Recipients may also see their payments grouped with other outputs in the same transaction.

This can create privacy concerns because observers may infer that the outputs were created by the same sender.

Bitcoin batching is powerful, but it should be used with fee strategy, timing, and privacy in mind.

Batching in Ethereum Rollups

Batching is one of the main reasons Ethereum rollups can reduce user costs.

A rollup processes transactions outside Ethereum and then posts compressed data, state roots, proofs, or commitments back to Ethereum.

The Ethereum optimistic rollup documentation explains that rollup operators bundle many off-chain transactions together before submitting them to Ethereum.

The Ethereum zero-knowledge rollup documentation says ZK-rollups bundle transactions into batches executed off-chain and submit summaries plus validity proofs to Ethereum.