deBridge is a cross-chain liquidity network that uses a competitive solver auction to settle transfers in 15 to 90 seconds across 10+ chains. Unlike most aggregators that route through other bridges, deBridge runs its own solver infrastructure — the deBridge Liquidity Network, or DLN — and exposes that infrastructure through APIs and a hosted app. This guide explains how deBridge's DLN works, which chains and assets it supports, how the fee model and solver economics function, and how deBridge compares to other intent-based bridges like Across and Eco.
​

The DLN handled over $20B in cumulative cross-chain volume across 25+ blockchains. That puts deBridge in the top 10 cross-chain protocols by volume, smaller than Across or Stargate but materially ahead of most aggregators. The technical model — solvers competing on quote, optimistic settlement, source-chain claim — is the same model Across pioneered and Eco extends to stablecoin-specific orchestration. Understanding deBridge is the most direct way to understand the intent-based bridging architecture that increasingly dominates fast cross-chain transfers.
​

deBridge is a cross-chain interoperability protocol with two primary products: deBridge Messaging (a generic cross-chain message-passing layer) and the deBridge Liquidity Network, called DLN (a solver-based asset transfer layer). Most users interact with DLN, which is what the name "deBridge" refers to in casual usage. deBridge.finance is the hosted swap interface; the underlying network is permissioned for solvers but open for users.
​

DLN's architecture is purpose-built for fast cross-chain transfers with low slippage. The protocol does not lock liquidity in escrow contracts on each chain (the Stargate model). It does not use a multisig or validator set to mint wrapped tokens (the Wormhole model). It uses a competitive auction among approved solvers who front the destination liquidity from their own balance sheets, then claim the source funds back through deBridge's verification layer once the source-chain transaction finalizes.
​

The model means deBridge has effectively no protocol-owned liquidity at risk. Solvers carry the inventory; the protocol carries the verification. That separation is why deBridge can offer 15-second finality on transfers up to $1M without warehousing TVL on each chain. deBridge's architecture documentation describes the verification layer in detail.
​

A DLN transfer goes through five stages: order creation, solver auction, destination fill, source unlock, and reconciliation.
​

Order creation happens on the source chain. The user signs a transaction that escrows the source asset in deBridge's source-chain contract along with the order parameters — destination chain, destination asset, minimum receive amount, deadline. The order is broadcast to the solver network.
​

Solver auction runs off-chain across deBridge's approved solver set. Each solver evaluates the order and decides whether to bid based on its inventory on the destination chain, its risk model for the source chain, and the order's minimum receive amount. The lowest acceptable bid wins. The auction completes in milliseconds.
​

Destination fill is when the winning solver sends the destination asset to the user from its own inventory. This happens 15 to 90 seconds after order creation, depending on destination-chain block times. The user sees the transfer "complete" at this point even though the source-chain unlock has not yet happened.
​

Source unlock happens once deBridge's verification layer confirms the destination fill. The protocol releases the escrowed source asset to the solver. This typically takes 1 to 10 minutes depending on source-chain finality requirements. For Ethereum source the wait is longer (probabilistic finality); for Solana source it is faster.
​

Reconciliation is the protocol-level accounting that ensures every order was filled correctly and every solver was paid. deBridge runs a continuous monitoring layer that flags any anomalies and can pause the network if a solver misbehaves. The verification model is closer to optimistic rollup design than to traditional multisig bridge design.
​

deBridge supports 10+ chains across EVM and Solana: Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, Avalanche, Linea, Solana, and a few rollup additions through 2025-2026. The chain list is shorter than LiFi or Squid by design — solvers must maintain inventory on every supported chain, and adding a new chain requires solver buy-in on inventory commitment.
​

Asset coverage is broader than chain coverage. deBridge supports the major stablecoins (USDC, USDT, DAI, USDS, FDUSD), the major bridge-able assets (ETH, WBTC, native chain tokens), and a long list of long-tail tokens via DEX integration on each end. A USDT-on-Polygon-to-WBTC-on-Ethereum transfer goes through DEX swaps on each chain plus the cross-chain leg, all stitched into one signature.
​

For Solana coverage specifically, deBridge is one of three major intent-based bridges (with Mayan and Wormhole NTT) that supports native Solana transfers without wrapped IOU intermediaries. Artemis stablecoin data shows Solana stablecoin volume reached 14% of total weekly cross-chain volume in March 2026. For any product flow involving Solana, deBridge is a relevant option.
​

deBridge's fee model has two components: a flat protocol fee (currently $0.50 per transfer) and a solver-set spread on the destination quote. The protocol fee is fixed and visible. The solver spread is implicit in the destination amount — the solver bids what they are willing to give the user, which captures the market price plus the solver's margin.
​

On a $1,000 USDC Ethereum-to-Arbitrum transfer in late March 2026, deBridge quoted $0.86 in total cost (protocol fee + solver spread) with 18-second finality. That is competitive with the cheapest aggregator route and faster than most. On a $10,000 transfer, the cost was $1.80 — solver spreads compress at higher volumes because the solver's risk-of-non-finality is fixed in dollar terms while their reward scales with notional.
​

For very large transfers (>$1M), deBridge's solver inventory becomes the constraint. A $5M USDC Ethereum-to-Solana transfer might split across multiple solvers or get routed through Wormhole NTT instead of DLN. The hosted UI surfaces this routing decision; the API returns it in the quote response. deBridge's quick start guide describes the size-based routing logic.
​

deBridge's headline speed is 15 to 90 seconds, with median time around 30 seconds for EVM-to-EVM transfers and 60 seconds for transfers involving Solana. The variance is driven by destination-chain block times and solver response time. The fastest routes (Arbitrum or Base destination) consistently complete in under 25 seconds.
​

The finality model is solver-mediated. The user sees their destination asset before the source-chain transaction has finalized. This is the same model Across uses, and the same model Eco uses internally. The risk to the user is zero — the solver has fronted the destination liquidity, so the user's transfer is complete when they see the destination credit. The risk is on the solver: if the source-chain transaction reverts, the solver eats the loss. Solvers price that risk into their spread.
​

For source chains with weak finality (probabilistic chains like Ethereum pre-Casper, or chains with reorg history), solver spreads are wider. For source chains with deterministic finality (Solana, most rollups after their finalization period), spreads are tighter. The cost difference is small for most transfers but visible at scale.
​

deBridge sits in a category with Across, Eco, and Mayan — bridges that use solver auctions to deliver fast finality on cross-chain transfers. The differences across these protocols are about chain coverage, asset focus, and the layer of abstraction each one targets.
​

Across is the largest intent-based bridge by volume, with deeper EVM coverage and longer-track-record solver liquidity. Across's settlement uses UMA's Optimistic Oracle for source-chain verification, which adds 2-4 hours to source-unlock time but lets the protocol operate without a permissioned solver set. DefiLlama shows Across at $14B+ cumulative volume through Q1 2026.
​

Mayan is the Solana-native intent-based bridge, with strong coverage across Solana and EVM chains. Mayan's solver model is similar to deBridge's; the network is smaller but tightly focused on Solana. For any flow that primarily routes through Solana, Mayan and deBridge are comparable choices.
​

Eco is the layer above the intent-based bridge category. Where deBridge, Across, and Mayan each operate as a single bridge, Eco operates as an orchestration layer that can route through any of them. An Eco intent might be filled by a deBridge solver, an Across relayer, or a Mayan auctioneer — the integrating team doesn't pick. Eco Routes exposes that orchestration as a stablecoin-specific API.
​

Understanding solver economics is the most direct way to understand why deBridge can quote sub-30-second finality without locking liquidity in escrow. Solvers are professional market makers who have committed inventory to the DLN. Each solver runs a continuous risk model that prices three things: inventory rebalancing cost, source-chain finality risk, and destination-chain gas variance.
​

Inventory rebalancing is the dominant cost. A solver that fills a $100,000 USDC transfer from Ethereum to Arbitrum has $100,000 less USDC on Arbitrum and $100,000 more USDC on Ethereum (after the source-claim). The solver needs to rebalance — either by waiting for a reverse-direction order (cheap) or by bridging back via a different route (paying gas plus possible spread). The expected rebalancing cost gets priced into every solver bid.
​

Source-chain finality risk is the chance that the source-chain transaction reverts before the solver claims it. For Ethereum source the probability is small but nonzero (deep reorgs are rare but possible). For Solana source the probability is near zero after a few blocks. Solvers price this risk into spreads — Ethereum-source orders carry slightly wider spreads than Solana-source orders for the same destination.
​

Destination-chain gas variance is the chance that gas spikes between bid and fill, eroding the solver's margin. For low-gas chains (Arbitrum, Base) this is small. For Ethereum destination the variance is meaningful and gets priced in. The cumulative effect of these three variables is why deBridge spreads vary by route in ways that aren't obvious from the user's perspective.
​

Use deBridge directly for one-off transfers between supported chains where the user values speed and reliability. The hosted app is the easiest way to access DLN. For developer integrations, deBridge's API is well-documented and the SDK is in active maintenance.
​

Use deBridge programmatically for any product flow that needs sub-minute finality on EVM-to-EVM or EVM-to-Solana transfers and where the user's source and destination chains are in deBridge's supported list. The finality SLA is the strongest in the category at small-to-medium notional sizes.
​

For stablecoin-specific orchestration at scale — recurring payments, treasury rebalancing, exchange deposit automation — Eco's Routes infrastructure handles the layer above deBridge. Eco can route through deBridge as one of its underlying bridges when deBridge wins the intent auction, but the integrating team submits a single intent and gets a single settlement event without picking a bridge.
​

Eco does not replace deBridge — Eco can route through deBridge. The orchestration vs. aggregation distinction is the same one that exists between an order management system and a single execution venue in equity markets. deBridge is a venue (one solver network). Eco is the OMS — it picks the venue, routes the order, handles the failure modes, and reconciles the outcome.
​

For stablecoin payments teams, this matters because deBridge alone is insufficient. A payment processor that integrates deBridge directly still has to handle the case where DLN inventory is exhausted on a chain, the case where deBridge is paused for maintenance, and the case where a different bridge would be cheaper or faster for a specific route. Eco handles those cases by treating deBridge as one of many possible underlying routes. The integrating team submits an intent and gets a settled balance.
​

For non-stablecoin or arbitrary-asset flows, integrating deBridge directly remains the right pattern. The orchestration value is highest for stablecoin flows because stablecoins have the most fungibility (1 USDC = 1 USDC across chains) and therefore the most route-substitution opportunity.
​

deBridge's DLN settles cross-chain transfers in 15 to 90 seconds, with median times around 30 seconds for EVM-to-EVM transfers. Speed depends on destination-chain block times and solver response. The fastest routes (Arbitrum, Base) consistently complete in under 25 seconds.
​

deBridge supports 10+ chains including Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, Avalanche, Linea, and Solana. The chain list is shorter than aggregators like LiFi by design — solvers must maintain inventory on every supported chain. See our crypto bridging guide.
​

deBridge charges a fixed protocol fee (currently $0.50 per transfer) plus solvers capture an implicit spread in the destination quote. Solvers compete on the spread, which compresses cost for users at higher volumes. The protocol does not warehouse liquidity, so its risk is operational rather than financial.
​

No. deBridge is a direct cross-chain bridge with its own solver network, not an aggregator that routes through other bridges. The user-facing experience is similar to an aggregator — a single quote and execution — but the underlying mechanism is the DLN solver auction, not external bridge selection.
​

Both use solver-based intent settlement. Across has larger volume and uses UMA's Optimistic Oracle for source verification. deBridge uses its own verification layer with faster solver settlement. For most users the difference is operational rather than functional. See our bridging guide for the comparison framework.
​