---
title: "What is a crypto bundler?"
description: "A crypto bundler combines multiple transactions or operations into one onchain submission across batching, MEV, rollups, token launches, and account abstraction."
---

# What is a crypto bundler?

<ImageBlock
  src="https://media.alchemy.com/overviews/crypto-bundler-hero-2026-06-23.png"
  alt="What is a Crypto Bundler?"
  width={1920}
  height={900}
  priority
/>

Few words in crypto carry as many meanings as "bundling." An app batching twenty balance reads into one call is bundling. A rollup compressing thousands of transactions into a single L1 submission is bundling. A searcher submitting an ordered set of trades to a block builder is bundling. So is a trader buying up a token's supply across a dozen wallets in the block it launches. Same word every time, different mechanics every time.

At a high level, a crypto bundler refers to a specific operation that combines multiple transactions into one onchain submission. Bundling shows up wherever doing things one at a time would cost more, leak more value, or fail more often than doing them together. The mechanics change across [Ethereum](https://www.alchemy.com/ethereum), [Solana](https://www.alchemy.com/solana), and the L2s, which is half of why the word causes so much confusion.

## What does a crypto bundler do?

A crypto bundler is any actor, contract, or service that combines multiple pending operations into a single onchain transaction. Traders bundle to control how a token launch lands. Searchers bundle to guarantee execution order. [Rollups](https://www.alchemy.com/rollups) bundle to amortize settlement cost. Wallets and apps bundle to cut request overhead, make multi-step actions atomic, and [sponsor gas](https://www.alchemy.com/gasless-transactions) so users never have to hold the native token.

The implementations of these different bundlers share little beyond the verb. Some bundlers are [trading bots](https://www.alchemy.com/blog/how-to-build-an-ai-trading-bot), some are protocol infrastructure, some are a single deployed contract anyone can call, and one is a named role in an Ethereum standard. The only way to know which one a doc means is context. The common types of bundlers are below.

## Why bundle in the first place?

In general, bundling is doing one of three jobs. It cuts cost, locks in order, or acts on someone's behalf, usually more than one of these at once.

The obvious one is cost. Every onchain transaction pays a fixed overhead before it does anything useful: 21,000 gas on EVM chains, plus calldata and signature costs. Pack ten operations into one transaction and you pay that toll once instead of ten times. For anything high-frequency, like DEX routing or indexer reads, the difference adds up fast.

Then there is ordering. Some operations are only safe, or only profitable, when they run together in a fixed sequence. An approval and the swap that follows it can be front-run in the gap between them. An arbitrage falls apart if anything slips between the buy and the sell. A launch snipe, or a buy placed the instant a token launches, only works if the buy lands in the same block the token is created. Bundling collapses "these, in this order, or nothing" into a single guarantee.

The subtlest reason is delegation. A [smart contract account](https://www.alchemy.com/overviews/how-do-smart-contract-wallets-work) cannot send its own transaction, so something holding a private key has to wrap the account's intent, pay the gas, and submit it. That is the job of an account abstraction bundler, and it is how an app pays gas on a user's behalf or signs for an agent that holds no ETH.

## What are the kinds of bundling in crypto?

There are five common types of bundling in crypto.

### Transaction batching and multicall

Multicall is the everyday form of bundling, a small contract that fans one transaction out into many calls. The canonical implementation is [Multicall3](https://github.com/mds1/multicall3), deployed at `0xcA11bde05977b3631167028862bE2a173976CA11` on 100+ EVM chains. Its most common job is batching reads. An app that needs balances, allowances, and prices across twenty tokens issues one `eth_call` against Multicall3 instead of twenty separate JSON-RPC requests. For writes, including router calls and DeFi protocol composition, batching from a single sender makes a multi-step action atomic: the approval and the swap land together or not at all.

The crucial limit with this kind of bundling is that multicall does not aggregate across senders. The transaction comes from one account, hits the batching contract, and fans out from there. There is no mempool and no operator. A large share of production reads on EVM chains route through Multicall3, which makes it one of the highest-volume and least visible forms of bundling here.

### MEV bundles

A MEV (maximum extractable value) bundle is an ordered list of transactions a searcher wants included atomically in the next block. The searcher submits it to a [block builder or relay](https://www.alchemy.com/overviews/proposer-builder-separation) instead of the [public mempool](https://www.alchemy.com/overviews/what-is-a-mempool), paying for inclusion. The point is order: an arbitrage that depends on a buy and a sell executing back to back only works if the searcher controls the sequence. Flashbots ships this on Ethereum through mev-boost; Jito ships the equivalent on Solana through its Block Engine.

The bundle is sealed, which means every transaction executes in the exact order specified, or none do. Builders, including Beaverbuild, Titan, and Flashbots, compete to assemble blocks from the most valuable bundles, and relays sit between builders and validators. See our [MEV protection overview](https://www.alchemy.com/overviews/what-is-maximum-extractable-value-and-mev-protection) for what this means for ordinary users routing through public mempools.

### Rollup batches

A [rollup sequencer](https://www.alchemy.com/overviews/optimistic-rollups) bundles transactions by default: it orders L2 transactions, compresses them, and submits hundreds or thousands of them as the calldata or blob payload of one L1 transaction. Optimism, Arbitrum, Base, and every other major rollup work this way. From the user's view, an L2 transaction looks like any other. From L1's view, the rollup paid one transaction's overhead to settle the whole batch.

[EIP-4844 blobs](https://www.alchemy.com/overviews/danksharding), introduced in the Dencun upgrade in March 2024, cut the L1 cost of those batches by roughly an order of magnitude, which is the structural reason L2 fees collapsed from cents to fractions of a cent. This is the most invisible form of bundling for a developer, because no application code touches it, and the most consequential for L2 economics.

### Token launch bundling

On memecoin launchpads, a "bundler" is a trading tool. It deploys a token and buys a slice of the supply from multiple wallets in the same block, landed atomically. On Solana, this usually happens through a Jito bundle. Creators use it to beat snipers to their own launch, or to spread an insider position across wallets so it is harder to see. The supply looks distributed onchain; in practice one party controls it.

That is why "bundled" reads as a warning label in trading dashboards. Tools that screen [Pump memecoin launches](https://pump.fun) flag the share of supply bought in the creation block, because hidden concentration can exit all at once. The mechanism is the same atomic, ordered inclusion a MEV bundle uses. The difference is what it is used for.

### Account abstraction bundlers

In smart-account documentation, "bundler" usually means the ERC-4337 actor: an offchain service that collects [user operations](https://www.alchemy.com/overviews/user-operations), packs many of them into one transaction, fronts the gas, and gets reimbursed by the account or by a [paymaster](https://www.alchemy.com/overviews/what-is-a-paymaster) that sponsors it. If you arrived here from wallet or [account abstraction](https://www.alchemy.com/overviews/what-is-account-abstraction) documentation, this is the bundler you are thinking of.

<ImageBlock
  src="https://media.alchemy.com/1703862507-user-operations-validations-executions.png"
  alt="Diagram showing how user operations are validated and executed through an account abstraction bundler"
  width={960}
  height={540}
/>

## How the five kinds of crypto bundlers stack up

<EmbeddedTable
  table={{
    columns: [
      {
        key: "bundlingType",
        width: 220,
        title: "Bundling type",
        dataType: "object",
      },
      {
        key: "whatGetsBundled",
        width: 240,
        title: "What gets bundled",
        dataType: "object",
      },
      {
        key: "whoDoesIt",
        width: 240,
        title: "Who does it",
        dataType: "object",
      },
      { key: "why", width: 280, title: "Why", dataType: "object" },
    ],
    data: [
      {
        bundlingType: { title: "Multicall / batching", tooltip: "", icon: "" },
        whatGetsBundled: {
          title: "Many contract calls from one sender",
          tooltip: "",
          icon: "",
        },
        whoDoesIt: {
          title: "Any wallet or app calling a batching contract",
          tooltip: "",
          icon: "",
        },
        why: {
          title: "Cut request overhead; make multi-step actions atomic",
          tooltip: "",
          icon: "",
        },
        id: 0,
      },
      {
        bundlingType: { title: "MEV bundle", tooltip: "", icon: "" },
        whatGetsBundled: {
          title: "An ordered set of transactions",
          tooltip: "",
          icon: "",
        },
        whoDoesIt: {
          title: "Searchers, via block builders and relays",
          tooltip: "",
          icon: "",
        },
        why: {
          title: "Guarantee order and atomic inclusion",
          tooltip: "",
          icon: "",
        },
        id: 1,
      },
      {
        bundlingType: { title: "Rollup batch", tooltip: "", icon: "" },
        whatGetsBundled: {
          title: "Thousands of L2 transactions",
          tooltip: "",
          icon: "",
        },
        whoDoesIt: { title: "The rollup's sequencer", tooltip: "", icon: "" },
        why: { title: "Amortize L1 settlement cost", tooltip: "", icon: "" },
        id: 2,
      },
      {
        bundlingType: { title: "Launch bundle", tooltip: "", icon: "" },
        whatGetsBundled: {
          title: "Token creation plus multi-wallet buys",
          tooltip: "",
          icon: "",
        },
        whoDoesIt: {
          title: "Trading bots on launchpads",
          tooltip: "",
          icon: "",
        },
        why: {
          title: "Control or conceal early supply",
          tooltip: "",
          icon: "",
        },
        id: 3,
      },
      {
        bundlingType: {
          title: "Account abstraction bundle",
          tooltip: "",
          icon: "",
        },
        whatGetsBundled: {
          title: "User operations from smart accounts",
          tooltip: "",
          icon: "",
        },
        whoDoesIt: {
          title: "Bundler services and wallet infrastructure",
          tooltip: "",
          icon: "",
        },
        why: {
          title: "Let accounts without keys or gas transact",
          tooltip: "",
          icon: "",
        },
        id: 4,
      },
    ],
  }}
/>

Same bundling concept, five different implementations and reasons behind it. The quickest disambiguation is to ask who benefits. A trader profits from a launch bundle, a searcher from a MEV bundle, a rollup's users from a batch, and an app's users from batching and sponsorship.

## Frequently asked questions

### Is a bundled token launch a scam?

Not always, but it is a red flag. Bundling lets a creator buy much of a token's supply across many wallets in the launch block. That can be legitimate sniper protection, or a way to hide concentrated ownership that dumps later. Treat heavily bundled supply as a risk signal worth checking before you buy.

### How do I tell if a token launch was bundled?

Onchain analytics tools and memecoin dashboards flag the share of supply bought in the same block the token was created. A high percentage spread across many fresh wallets is the tell. Check the token's first-block buys and holder distribution before trusting that the supply looks organically spread.

### What is a bundler in ERC-4337?

In ERC-4337 account abstraction, a bundler is an offchain service that collects user operations from smart contract accounts, packs several into one transaction, pays the gas, and submits it to the EntryPoint contract. It is reimbursed by the account or a paymaster. Alchemy runs an open-source one called [Rundler](https://github.com/alchemyplatform/rundler).

### Is Multicall the same as a bundler?

Not quite. Multicall, usually Multicall3, batches many calls from a single sender into one transaction, mostly to cut RPC requests for reads. An ERC-4337 bundler aggregates user operations from many different smart accounts and pays their gas. Same instinct, different scope. Multicall stays inside one sender; a bundler spans many.

### What is the difference between a MEV bundle and a rollup batch?

A MEV bundle is an ordered set of transactions a searcher submits to a block builder for atomic, front-run-resistant inclusion. A rollup batch is thousands of L2 transactions a sequencer compresses into one L1 submission to amortize settlement cost. One controls ordering, the other controls cost.

## Building on crypto bundlers with Alchemy

Our [RPC API](https://www.alchemy.com/rpc-api) is the entry point for the bundling surfaces a developer touches directly: the batched reads contracts like Multicall3 fan out, the rollup RPC interfaces L2 traffic flows through, and the standard endpoints on every chain we host. For teams building smart-account flows, we also ship [Rundler](https://github.com/alchemyplatform/rundler), our open-source Rust bundler, and [Gas Manager](https://www.alchemy.com/gasless-transactions) for gas sponsorship policies. See [how we built Rundler](https://www.alchemy.com/blog/open-sourcing-rundler) for the design.

Create an app, grab a key, and the same key works across all of it. No contracts, no waitlist. [Start building](https://dashboard.alchemy.com/).

There is no single thing called a bundler, and there probably never will be. The word travels because the problem under it, do more in one transaction, turns up at every layer of crypto. Spot the layer, whether a contract call, a block, an L2 batch, a token launch, or a smart account, and you have spotted which bundler someone means.