deBridge

• Name: deBridge
• URL: https://debridge.com/
• Tags: ethereum-ecosystem solana-ecosystem
• Category: cross-chain execution middleware / solver-routed bridge-and-swap packaging
• Summary: deBridge is solver-routed execution middleware. The 0-TVL line matters, but it is still mostly a packaging layer above deeper settlement and verification rails. The useful question is who controls quote formation, fulfillment behavior, timeout defaults, and the route surface an integrator hands to users.
• What it does:
  • Provides cross-chain and same-chain execution for token swaps and other onchain actions through the deBridge Liquidity Network (DLN)
  • Uses a solver-based model where users create source-chain orders and third-party solvers fulfill those orders on the destination chain
  • Exposes a separate messaging layer, the deBridge Messaging Protocol (DMP), for authenticated cross-chain messaging and contract interactions
  • Offers widgets, APIs, quickstarts, protocol specs, supported-chain docs, and operational guidance for integrators building cross-chain user flows
  • Publishes AI-facing surfaces including llms.txt documentation indexing and an MCP server for conversational quoting and swap-link generation
• Key claims:
  • The docs define deBridge as a non-custodial execution layer for cross-chain and same-chain actions using a 0-TVL architecture with no shared liquidity pools.
  • The execution-model docs describe a simple solver loop: users create source-chain orders, solvers detect and evaluate them, a solver fulfills on the destination chain from its own inventory, then claims the locked source-side assets.
  • The same docs make the gas and timeout policy explicit: the user pays source-chain gas, the solver pays destination-chain gas and bakes that cost into the quoted rate, and users can cancel unfilled orders.
  • deBridge also exposes integration-level auto-cancellations where it subsidizes gas after a timeout if that feature is enabled, which is exactly the kind of middleware default that matters more than generic non-custodial branding.
  • The broader documentation set shows a real operator stack rather than a mere bridge frontend: DLN, DMP, hooks, same-chain routing, infrastructure tooling, and integrator-facing APIs all sit under one branded control surface.
  • The docs also reveal unusually strong machine-readable and agent-facing surfaces, including llms.txt and an official MCP server package for AI-assisted quoting and swap-link generation.
  • That still does not make deBridge the trust anchor. It makes deBridge the layer that decides how much solver, messaging, and route complexity gets hidden behind one integrator-facing surface.
• Whitepaper: No classic standalone whitepaper was confirmed during this pass. The strongest primary materials were the docs welcome page, architecture and security docs, documentation index, and MCP-server docs; see ../whitepapers/debridge-primary-sources-2026-04-26.md.
• Sources:
  • https://debridge.com/
  • https://docs.debridge.com/
  • https://docs.debridge.com/home/architecture/execution-model
  • https://docs.debridge.com/home/security/security-overview
  • https://docs.debridge.com/llms.txt
  • https://docs.debridge.com/dln-details/mcp/mcp-server

Internal linkages

• Best upward reads for route control and fulfillment-default power: across and relay.
• Keep this note on solver behavior, quote packaging, timeout handling, and execution truth rather than on every settlement rail deBridge can sit above.

Control surface

• The leverage is in solver participation, quote and status APIs, destination-gas pricing inside the quoted rate, cancellation policy, and which settlement or messaging rails deBridge exposes at all.

• 0-TVL removes one familiar pool-risk story. It does not make deBridge neutral. Users and integrators still inherit middleware defaults about order visibility, fulfillment timing, timeout handling, and route packaging.

• Last reviewed: 2026-06-14 UTC