Summary: deBridge is a solver-market execution layer that packages cross-chain and same-chain actions without keeping a shared liquidity pool. The clean read is not bridge, but bigger; it is a routing and fulfillment layer that sits above deeper settlement and verification rails, with most of the product differentiation living in solver behavior, order flow, and middleware packaging.
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 source-chain order creation, solver detection and fulfillment, solver-side destination gas payment, and user cancellation rights for unfilled orders
The security docs argue that the 0-TVL design removes the shared-liquidity honeypot typical of many traditional bridges and emphasize per-order isolation plus guaranteed recovery for unfilled orders
The documentation set shows a broader product surface than a bridge frontend, including DLN, DMP, hooks, same-chain routing, infrastructure-as-a-service, token deployment tooling, and monetization features for integrators
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 transaction-link generation
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.