Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
LABS
Glossary

Cross-Chain Bundle

A Cross-Chain Bundle is a set of transactions intended for execution across multiple blockchains, submitted as a single unit to capture cross-domain MEV.
Chainscore © 2026
definition
BLOCKCHAIN INTEROPERABILITY

What is a Cross-Chain Bundle?

A cross-chain bundle is a single, atomic transaction that executes a sequence of operations across multiple, independent blockchain networks.

In technical terms, a cross-chain bundle is a programmable set of instructions, often facilitated by a relayer network or a specialized interoperability protocol, that coordinates state changes on two or more distinct blockchains. Unlike simple asset transfers via bridges, a bundle can orchestrate complex, conditional logic—such as performing a swap on Ethereum, using the proceeds to mint an NFT on Polygon, and then staking a derivative of that NFT on Avalanche—all within a single user-signed transaction that either completes entirely or fails atomically. This eliminates the need for users to manually sign and pay for gas on each chain sequentially, significantly improving the user experience for cross-chain applications.

The core innovation lies in its atomicity and composability. Atomicity ensures that if any step in the bundled sequence fails, all preceding operations are rolled back, protecting users from partial execution and financial loss. Composability allows developers to treat multiple blockchains as a single, unified execution environment, enabling new DeFi strategies and applications that leverage the unique strengths of different networks. Protocols like LayerZero with its Omnichain Fungible Tokens (OFT) standard and Axelar with its General Message Passing are foundational technologies that enable the creation and secure passage of these cross-chain instruction bundles.

From an architectural perspective, creating a cross-chain bundle typically involves an off-chain relayer or validator set that observes the source chain, verifies proofs of execution (like Merkle proofs or light client state proofs), and submits the verified messages to the destination chain(s). The bundle's logic is often encoded in a smart contract on the source chain (the sender) and executed by a corresponding contract on the destination (the receiver). This mechanism is central to cross-chain decentralized exchanges (DEXs), multichain yield aggregators, and interchain account abstraction, where a single action can trigger a cascade of dependent events across the ecosystem.

For users and developers, the practical implications are significant. Users benefit from a seamless, one-click experience for complex multichain operations, while developers can build applications that are no longer siloed to a single chain's liquidity and functionality. However, the security model is paramount; the trust assumptions shift from the security of a single chain to the security of the interoperability protocol and its relayers. Therefore, the resilience of the underlying cross-chain messaging layer is the critical factor in assessing the risk of any application built on cross-chain bundles.

how-it-works
MECHANISM

How Cross-Chain Bundles Work

A technical breakdown of the architecture and execution flow enabling atomic operations across multiple blockchains.

A cross-chain bundle is a set of interdependent transactions that are executed atomically across two or more distinct blockchains, meaning all transactions succeed or all fail together. This atomicity is enforced by a cross-chain messaging protocol or a specialized sequencer that coordinates the execution. The bundle is not a single transaction but a coordinated workflow where the outcome on one chain acts as a verifiable trigger or input for actions on another, creating a unified multi-chain operation. This is distinct from simple bridging, which typically involves a two-step, non-atomic asset transfer.

The core mechanism relies on conditional execution and state verification. A user or dApp submits a bundle specification to a cross-chain service provider (like a sequencer network or intent solver). This provider then orchestrates the sub-transactions in the required order, often holding assets in escrow or using advanced cryptographic proofs. Crucially, the execution on the destination chain is contingent on providing cryptographic proof—such as a Merkle proof or a zero-knowledge proof—that the required source-chain transaction was finalized and valid. Protocols like Chainlink CCIP, LayerZero, and Axelar provide infrastructure for this proof verification.

From a user's perspective, submitting a cross-chain bundle often involves expressing an intent—a declarative statement of a desired outcome (e.g., "swap ETH on Ethereum for SOL on Solana and deposit it into a lending protocol")—rather than manually crafting each low-level transaction. Solver networks then compete to discover and propose the most efficient bundle execution path across liquidity pools and chains. This intent-centric abstraction significantly improves user experience, hiding the underlying complexity of managing gas fees, nonces, and block times on multiple networks.

The atomic guarantee is the defining feature. If any single transaction in the bundle fails (due to slippage, insufficient liquidity, or a changed condition), the entire sequence is reverted. This is achieved through atomic commit protocols like hash time-locked contracts (HTLCs) in simpler cases, or via the rollback capability of the coordinating sequencer in more advanced systems. This eliminates the principal risk of partial execution, where a user's assets could be left stranded in an intermediate state on one chain without the corresponding action completing on another.

Practical applications extend far beyond asset transfers. Use cases include cross-chain leveraged trading (opening a position using collateral on Chain A with a trade executed on Chain B), multi-chain governance (voting with tokens locked on one chain to execute a proposal on another), and unified liquidity provisioning (depositing into a single vault that automatically allocates funds across DeFi protocols on multiple chains). Each bundle encapsulates a complete, failure-immune business logic flow across the modular blockchain landscape.

key-features
ARCHITECTURE

Key Features of Cross-Chain Bundles

Cross-chain bundles are atomic, multi-step transactions that execute across multiple blockchains. They are defined by several core architectural features that ensure security, efficiency, and composability.

01

Atomic Execution

The fundamental property of a cross-chain bundle is its atomicity: either all constituent transactions across all involved blockchains succeed, or the entire bundle fails and state changes are reverted. This eliminates the risk of partial execution, where assets could be left stranded on an intermediate chain. It's enforced by a coordinator (like a relayer network or intent solver) that manages the conditional execution flow.

02

Multi-Step Transaction Logic

A bundle is not a single swap or transfer; it's a programmable sequence of actions. A typical flow might involve:

  • Step 1: Swap ETH for USDC on Ethereum.
  • Step 2: Bridge the USDC to Avalanche via a canonical bridge.
  • Step 3: Deposit the USDC into a lending protocol on Avalanche. This logic is defined in a single user intent or bundled by a solver, abstracting complexity from the end-user.
03

Decentralized Verification & Settlement

Bundles rely on cryptographic proofs (like Merkle proofs or zero-knowledge proofs) to verify the outcome of transactions on one chain before committing to actions on another. Settlement often occurs on a destination chain or a dedicated settlement layer (e.g., a rollup), which acts as the final arbiter, consuming proofs from all source chains to trigger the final state updates atomically.

04

Composability of Primitives

Bundles are built by composing existing DeFi primitives—bridges (e.g., Axelar, LayerZero), DEXs (e.g., Uniswap, PancakeSwap), and lending protocols (e.g., Aave, Compound)—into a single coherent operation. This turns isolated applications across chains into a unified, interoperable financial system. The bundle protocol acts as the orchestration layer that sequences these calls.

05

Intent-Based Design

Many bundle systems use an intent-centric architecture. Instead of specifying low-level transaction calldata for each chain, users submit a declarative goal (e.g., "Get the best yield for my ETH across chains"). Solvers (competitive networks of searchers) then find the optimal path, construct the concrete bundle, and submit it for execution, often competing on price and speed.

06

Fee Abstraction & Payment

A key UX challenge is paying for gas across multiple, potentially non-EVM chains. Cross-chain bundles solve this through fee abstraction. Users can often pay all gas fees in a single token (e.g., pay for an Avalanche and Polygon transaction in ETH on Ethereum) via a gas relayer or by having the solver include fee payment as a step within the atomic bundle itself.

examples
CROSS-CHAIN BUNDLE

Examples & Use Cases

Cross-chain bundles enable atomic execution across multiple blockchains. These examples illustrate their practical applications in DeFi, gaming, and asset management.

technical-details
CORE MECHANICS

Technical Details & Atomicity

This section details the fundamental technical properties that define a cross-chain bundle's behavior, focusing on the critical concept of atomicity and its implementation.

A cross-chain bundle is a set of interdependent transactions that must be executed atomically across multiple blockchains, meaning either all transactions succeed or the entire bundle fails, with no partial state changes. This atomicity is the defining and most critical property, as it eliminates the risk of a user's assets becoming stranded on one chain if a dependent transaction on another chain fails. Achieving this across heterogeneous systems with independent consensus and finality is the primary technical challenge that distinguishes cross-chain bundles from simple multi-chain transactions.

The atomic execution is typically enforced by a coordinator, often a smart contract or a decentralized validator set, which acts as an atomic commit coordinator. This entity verifies the preconditions for all transactions in the bundle across the involved chains. Only after confirming all preconditions are met does it sign and release the final authorization (like a commit message) that allows the transactions to be finalized. If any precondition fails, the coordinator issues an abort signal, and any provisional locks or holds on assets are released, rolling back the entire operation.

Implementing this requires sophisticated interoperability protocols. These protocols handle the secure messaging and state verification between chains, often utilizing light client proofs, optimistic verification, or trusted relayers. The security model of the entire bundle is only as strong as the weakest link in this cross-chain communication layer. Furthermore, the bundle must account for varying block times and finality mechanisms, employing techniques like hash time-locked contracts (HTLCs) or persistent conditional states to manage the temporal mismatch between different ledgers.

From a developer's perspective, constructing a bundle involves defining a clear dependency graph for the transactions. For example, a bundle to swap Token A on Ethereum for Token B on Avalanche and then supply it as liquidity on a Avalanche DeFi protocol has a strict sequence: the swap depends on the bridge outcome, and the liquidity provision depends on the swap. The bundle's atomic guarantee ensures a user cannot end up with bridged tokens but no liquidity position, or vice-versa, protecting them from market volatility and failed intermediate steps.

The concept extends to generalized atomicity, where bundles can include not just asset transfers but any state change—governance votes, NFT minting, or oracle updates—across chains. This enables complex, multi-chain applications (MApps) that behave as a single coherent system. The technical frontier involves standardizing bundle definitions (e.g., using formats like the Inter-Blockchain Communication (IBC) packet) and improving the efficiency of cross-chain state proofs to make atomic bundles faster and more cost-effective.

ecosystem-usage
CROSS-CHAIN BUNDLE

Ecosystem & Protocol Usage

A cross-chain bundle is a single, atomic transaction that executes operations across multiple, distinct blockchain networks. It is a core primitive for interoperability, enabling complex workflows that leverage the unique capabilities of different chains.

01

Atomic Cross-Chain Execution

The defining feature of a cross-chain bundle is atomicity: either all operations across all chains succeed, or the entire bundle fails and all state changes are reverted. This prevents partial execution, a critical property for complex financial transactions like cross-chain arbitrage or collateralized lending where funds move between networks. It ensures users are never left with assets stranded on an unintended chain.

02

Core Components & Flow

A bundle typically consists of:

  • Source Chain Actions: Initiation, often locking or burning assets.
  • Messaging/Proof Relay: A verifiable message (proof) of the source action is transmitted via a cross-chain messaging protocol (e.g., IBC, LayerZero, Wormhole).
  • Target Chain Actions: Execution of the intended operation (e.g., minting assets, calling a contract) upon verification of the relayed proof. The bundle manager (often a relayer or sequencer) coordinates this multi-step flow.
03

Primary Use Cases

  • Cross-Chain Swaps: Swap a token on Chain A for a different token on Chain B in one atomic action.
  • Cross-Chain Yield Farming: Deposit collateral on Chain A to farm rewards or borrow assets on Chain B.
  • Unified Liquidity Pools: Contribute liquidity to a pool that spans multiple chains from a single interface.
  • Cross-Chain NFT Minting/Bridging: Mint or use an NFT on one chain to trigger an event or claim an asset on another.
05

Security & Trust Models

Bundles inherit security from the underlying cross-chain communication layer:

  • Native Verification: Protocols like IBC use light client verification for maximal security, trusting only the consensus of the connected chains.
  • External Verification: Protocols like LayerZero and Wormhole rely on a decentralized network of oracles and relayers or a guardian set to attest to message validity.
  • Economic Security: Many systems incorporate slashing mechanisms and bonding for relayers to disincentivize malicious behavior.
06

Developer Considerations

Building with cross-chain bundles requires handling asynchronous execution and message ordering. Developers must account for:

  • Gas Management: Paying for execution on multiple chains, often requiring gas abstraction solutions.
  • Error Handling & Retries: Designing for scenarios where a target chain is congested or a relayer fails.
  • State Consistency: Ensuring application logic remains consistent across all chains despite latency in message delivery. SDKs from major interoperability protocols abstract much of this complexity.
security-considerations
CROSS-CHAIN BUNDLE

Security Considerations & Risks

Cross-chain bundles enable atomic execution across multiple blockchains, but introduce unique security challenges beyond single-chain transactions.

02

Atomicity Failure

The core promise of a cross-chain bundle is atomic execution: all actions across chains succeed or fail together. Key failure modes include:

  • Partial execution: A transaction succeeds on Chain A but fails on Chain B due to slippage, insufficient gas, or state changes, leaving the user's assets stranded.
  • Front-running and MEV: Searchers can exploit the time delay between chain commitments to profit at the user's expense, breaking intended execution logic.
  • Reorg attacks: A blockchain reorganization on one chain after a bundle is considered final can invalidate the entire atomic operation.
03

Complexity & Audit Surface

The system complexity of coordinating multiple smart contracts, oracles, and relayers across heterogeneous chains drastically expands the attack surface. This includes:

  • Contract vulnerabilities: Bugs in any single chain's bundle handler contract can be exploited.
  • Oracle manipulation: If bundle validity depends on price or state oracles, these become attractive targets.
  • Upgrade risks: Bundles often involve upgradeable proxy contracts; a malicious upgrade can compromise the entire system.
  • Difficult formal verification: Proving correctness across multiple, asynchronous state machines is exceptionally challenging.
04

Liquidity & Settlement Risk

Bundles that involve cross-chain swaps or lending are exposed to liquidity risk and settlement finality discrepancies. Critical considerations are:

  • Slippage across chains: Liquidity pools on the destination chain may be insufficient, causing failed trades and broken atomicity.
  • Varying finality times: A transaction may be considered final on a fast chain (e.g., Solana) but only provisional on a slower, probabilistic chain (e.g., Ethereum during reorgs).
  • Wrapped asset depeg: If a bundle uses a wrapped asset (e.g., wBTC), its value depends on the custodian's solvency and the underlying bridge's security.
05

Validator Set Attacks

For bundles secured by light clients or fraud proofs that validate headers from other chains, the security reduces to that of the connected chains' validator sets. This creates risks:

  • Long-range attacks: An attacker gaining control of a chain's historical validator set could create fraudulent proofs.
  • Economic finality vs. probabilistic finality: Bundling a transaction from a chain with economic finality (e.g., Cosmos) with one from a chain with probabilistic finality (e.g., Bitcoin) creates mismatched security guarantees.
  • Consensus-level exploits: A 51% attack or other consensus failure on one chain can invalidate proofs for all dependent bundles.
06

User & UX Risks

End-users face opaque risks due to the abstraction layer of cross-chain bundles. Primary concerns include:

  • Unclear liability: When a bundle fails, determining which intermediary (relayer, bridge, chain) is at fault is complex, complicating recourse.
  • Gas estimation complexity: Accurately estimating total cost (fees on multiple chains + relayer fees) is difficult, leading to failed transactions.
  • Phishing and spoofing: Fake front-ends can mimic bundle interfaces to steal signatures and funds.
  • Privacy leakage: The bundle's full intent is often visible to relayers and sequencers, exposing user strategy.
BUNDLE ARCHITECTURE

Comparison: Single-Chain vs. Cross-Chain Bundles

A technical comparison of transaction bundle execution models based on their operational scope and architectural constraints.

Feature / MetricSingle-Chain BundleCross-Chain Bundle

Execution Scope

Transactions within a single blockchain network

Transactions across multiple, heterogeneous blockchain networks

Atomicity Guarantee

Native atomic execution via mempool ordering

Relies on external protocols (e.g., bridging, MPC, oracles) for cross-chain atomicity

Settlement Finality

Determined by the consensus of the single underlying chain

Finality is asynchronous; depends on the slowest chain in the bundle

Fee Structure

Single gas token (e.g., ETH, SOL) from one fee market

Multiple gas tokens and fee markets; requires fee abstraction or aggregation

State Access

Direct, synchronous read/write to a single state machine

Indirect, asynchronous; requires cross-chain messaging for state proofs

Developer Complexity

Lower; uses standard SDKs and tooling for one chain

Higher; requires managing multiple RPC endpoints, gas tokens, and latency

Primary Use Case

Complex DeFi interactions, MEV arbitrage, on-chain gaming

Cross-chain swaps, multi-chain liquidity management, omnichain applications

Latency Profile

Bounded by block time of a single chain (e.g., 12s, 400ms)

Bounded by the slowest chain's block time plus cross-chain message delay (seconds to hours)

CROSS-CHAIN BUNDLES

Frequently Asked Questions (FAQ)

Cross-chain bundles are a fundamental primitive for executing complex, multi-chain transactions. This FAQ addresses common technical and operational questions.

A cross-chain bundle is a single, atomic transaction that executes a sequence of operations across multiple, distinct blockchain networks. It works by leveraging a cross-chain messaging protocol (like LayerZero, Axelar, or Wormhole) and a sequencer or relayer network. The process involves: 1) A user or dApp submits a bundle definition, 2) A sequencer orders and coordinates the execution, 3) Messaging protocols pass data and proofs between chains, and 4) Executors on each target chain finalize the operations. The entire bundle either succeeds on all chains or fails entirely, ensuring atomicity.

ENQUIRY

Get In Touch
today.

Our experts will offer a free quote and a 30min call to discuss your project.

NDA Protected
24h Response
Directly to Engineering Team
10+
Protocols Shipped
$20M+
TVL Overall
NDA Protected Directly to Engineering Team
Cross-Chain Bundle: Definition & MEV Guide | ChainScore Glossary