Skip to main content
Bundles are a new execution primitive for building chain-agnostic interactions in a single click. Bundles let users simply express what outcome they want and the system handles the execution flow across chains, while users keep full self-custody of their assets. Having users and developers wrestle with fragmented liquidity, native gas balances, RPC reliability, and cross-chain orchestration is a thing of the past. Bundles are the foundation of deBridge’s upcoming protocol evolution. They introduce a cleaner mental model for onchain experiences: intents over transactions, with deterministic execution rules and a unified interface across environments, including EVM chains and Solana.
Bundles are currently in a private rollout with a limited set of integrators. This page is a public overview meant to explain the “why”.

​
From Transactions to Intents

Onchain UX breaks down when users are asked to think like infrastructure. They have to manage approvals, keep native tokens for fees, retry failed actions, and check execution through multiple chains and tools. Even when everything works, the experience is not smooth. Bundles shift the interaction model. Users don’t stitch together steps; they express an intent - the desired result, and the underlying system coordinates the required actions to reach that result according to predefined rules. This makes complex multi-step workflows feel like a single operation, while keeping users in control of their assets.

​
Why Bundles Matter

Bundles remove the most common execution pain points that make multi-chain products hard to build and harder to use. The result is a more reliable runtime for applications and a dramatically simpler experience for users. For users, Bundles reduce the overhead of “being multi-chain” by abstracting away mechanics like native-fee management and multi-step orchestration. For developers, Bundles reduce the need to write repetitive boilerplate code for retries, landing transactions, and chain-by-chain edge cases.

​
A Better Build Surface for Developers

Bundles are designed to let teams focus on product instead of plumbing. When the execution layer becomes consistent and intent-driven, developers can spend their time on the actual user journey - onboarding, discovery, UX, and differentiation, rather than building and maintaining utility libraries. This is the kind of primitive that unlocks a new class of apps: wallets that feel seamless across chains, agents that can act on outcomes rather than raw transactions, and trading systems that can compose complex multi-chain steps into one coherent chain-agnostic operation.

​
What You Can Build

Bundles are a building block for any product where users want outcomes, not operations. Common starting points include multi-chain onboarding flows, one-click portfolio actions, cross-chain trading journeys, and application workflows that span multiple environments. As the ecosystem expands, Bundles are intended to power experiences across apps, wallets, agents, and advanced trading systems-while keeping execution deterministic and the interface consistent.

Wallets & Superdapps

Single-click flows that feel native, even when execution spans multiple chains.

Trading & Routing

Composable journeys that package multiple steps into one user action.

Apps & Workflows

Outcome-based actions that can include arbitrary logic without extra boilerplate code.

Agents & Automation

Intent-driven execution that is easier to reason about, test, and monitor.

​
Availability

Bundles are available today to a select group of integrators under restricted access. Public, user-facing experiences powered by Bundles will roll out in the near future. If you’re building a product where execution complexity is holding back UX, or where multi-chain support is becoming operationally expensive - Bundles are designed for you.

​
Request Access

If you’d like to evaluate Bundles for your product, request access to the private documentation and integration materials by contacting someone from the team or by filling this form.