Debridge networks are DLN Route Endpoints With Pair-Specific Limits
Debridge networks are the source and destination blockchains that DLN accepts for solver-filled cross-chain orders, yet a listed chain alone does not make every route executable. A usable path needs two different chain IDs, recognized token identifiers, a valid recipient and a quote that gives a solver enough destination-side margin. Ethereum, Arbitrum, Base, BNB Chain and Solana illustrate the range: EVM addresses coexist with Solana public keys and SPL Token mints. This field manual focuses on the limits that matter before signing: chain selection, asset resolution, amount encoding, fill economics, order states and the difference between network support and a fillable token pair.
SOL output must reach 0.001 SOL when Solana is the destination and SOL is requested.
DLN Routes Versus Circle CCTP
DLN serves broader token-to-token intents than Circle CCTP, whose cross-chain path moves native USDC through burn-and-mint settlement. Circle CCTP fits a native USDC transfer between supported domains; DLN fits an order that starts and ends with different assets, such as ETH on Arbitrum and USDC on Solana. DLN solvers supply destination inventory and later claim source assets, so route availability follows solver economics. CCTP availability follows Circle’s supported USDC domains and attestation flow. The decision turns on output asset, destination coverage and delivery mechanism.
Route Availability Has Three Gates
A DLN route opens only when its network, asset mapping and solver economics all pass separate checks.
Network admission starts with the chain identifiers accepted by the route builder, then asset admission resolves a token address or native-token sentinel on each side. Ethereum, Optimism, BNB Chain, Polygon, Base, Arbitrum, Avalanche and Linea share EVM-style addressing, yet their ERC-20 contracts remain chain-specific. Solana uses program accounts and SPL Token mint addresses. A USDC symbol therefore cannot substitute for its exact mint or contract. The request must bind each asset to its chain before it calculates output, because an address copied from another network identifies a different account or no account at all.
EVM And Solana Identifier Details
EVM Identifiers
An EVM account or token address holds 20 bytes and displays as 0x plus 40 hexadecimal characters. The chain ID separates Ethereum 1 from Arbitrum 42161 even when the wallet displays the same externally owned account.
Solana Identifiers
Solana public keys encode 32 bytes, and DLN uses internal identifier 7565164 when building its cross-chain route.
Solver Economics
Solver admission is economic rather than symbolic. DLN holds no shared pool for the order; a solver pays the requested asset on destination, sends the unlock message and later claims the locked source asset. That sequence creates three operating transactions, plus any source or destination swap for non-reserve assets. A supported route becomes unattractive when gas, swap impact or inventory rebalancing exceeds the offered spread. Refreshing the quote updates these live inputs without changing network identifiers. Fillability returns when revised terms cover delivery and settlement.
What Stops A Listed Route From Filling?
A listed DLN route remains unfilled when its promised output leaves no viable margin for a solver.
Market orders use a quoted output designed for immediate solver interest, while limit orders encode an output target that can remain pending. The response separates PreSwap, EstimatedOperatingExpenses and TakerMargin components before the wallet creates the order. If nobody accepts those terms, status stays Created until a fill, patch or cancellation changes it.
Cancellation begins on the destination chain and sends a deBridge Messaging Protocol message back to the source. The destination authority controls that action, while the source cancellation beneficiary receives the returned input. An integration-only auto-cancellation option uses 5 minutes for unprofitable market orders and 15 minutes for other eligible cases. It requires approval and excludes limit orders. Those fixed timeouts apply only when that feature is enabled, so an ordinary order follows its recorded state transitions.
The Seven-Stage Route Check
The DLN route check follows seven stages, from network selection through destination fill and source-chain unlock.
| Stage | DLN Action | Hard Limit Or Threshold |
|---|---|---|
| 1. Choose Networks | Set source and destination chain IDs | Two different chain IDs |
| 2. Resolve Assets | Bind a contract, mint or native-token sentinel to each chain | One source and one destination token identifier |
| 3. Encode Amounts | Express input in base units and set output to automatic or explicit | Source amount above zero |
| 4. Set Parties | Add the destination recipient and both order authorities | One recipient and two authority fields |
| 5. Request Quote | Calculate swaps, protocol fields and solver expenses | Transaction data required before signing |
| 6. Create Order | Approve ERC-20 spending when needed and sign on source | Allowance no less than input; one creation signature |
| 7. Fill And Unlock | Deliver destination output, send DMP message and claim source assets | Full encoded take amount before Fulfilled |
| Route Ready | Every preceding condition passes | All seven stages complete |
The table separates chain admission from route execution. A selector entry proves only stage 1; the order still needs exact asset identifiers, authorities, recipient data and amounts. On EVM sources, an ERC-20 transfer also needs allowance for the transaction target returned with the quote. Native ETH, BNB or POL uses transaction value instead of ERC-20 allowance. When SOL is the destination asset, the API enforces 0.001 SOL, equal to 1,000,000 lamports, as the minimum output. That fixed floor belongs to destination requirements, while the source input needed to obtain it moves with the requested pair and quote.
Chain IDs, Token Standards And Decimal Handling
DLN chain IDs identify execution domains, while token standards and decimal precision define the actual assets moved.
DLN identifies Ethereum as 1, Optimism as 10, BNB Chain as 56, Polygon as 137, Base as 8453, Arbitrum as 42161, Avalanche as 43114, Linea as 59144 and Solana as 7565164. These values are identifiers, not block counts, so they never take thousands separators. EVM token addresses follow ERC-20 conventions, while Solana routes point to SPL Token mints. Selecting the right chain without the right asset identifier still describes the wrong order.
Amounts travel as integers in smallest units. ETH uses 18 decimals, so 1 ETH equals 1,000,000,000,000,000,000 wei; USDC uses 6 decimals, so 1 USDC equals 1,000,000 base units. Solana defines 1 SOL as 1,000,000,000 lamports. Interfaces format those integers for reading, but DLN matches the encoded amount. A decimal mismatch changes magnitude rather than market price, and the route becomes valid only after loading the correct token metadata.
Can Every Supported Chain Pair Be Quoted?
No, two chains in the selector still need a quotable token pair, valid direction and executable destination delivery.
The corresponding notes are kept in Debridge choosing eligibility. The route request tests the exact source asset, source amount, destination asset and recipient together. Ethereum USDC to Solana SOL presents different swaps and solver costs from Arbitrum ETH to Base USDC, even though all four networks have recognized identifiers. This is why Debridge networks should be read as eligible execution domains rather than universal asset corridors. A fresh response must return estimation fields and transaction data for the specified pair; only that concrete response establishes an executable route under the chosen amount and recipient.
Solver Settlement Across Two Contracts
DLN settles through DlnSource and DlnDestination, with solvers financing the destination leg before claiming source liquidity.
Order Creation On The Source
DlnSource receives the give asset and records the take chain, asset, recipient and authorities. Creation carries one flat fee in the source gas token and one percentage fee in the input token; contract state and the quote set both. A cancelled order returns the locked source asset plus those fees. The deterministic order ID binds the encoded structure.
Destination Fill And Unlock
A solver watches Created orders, transfers the full take amount through DlnDestination and marks the destination state Fulfilled. A solver completes three transactions: fulfill on destination, send the unlock message and claim the source-chain assets. DLN exposes eight API status values: None, Created, Fulfilled, SentUnlock, ClaimedUnlock, OrderCancelled, SentOrderCancel and ClaimedOrderCancel. The order ID is a 32-byte Keccak-256 hash derived from the serialized fields, so both chains reproduce the same identifier. Settlement completes when ClaimedUnlock releases source assets to the solver.
The Source-Signature Decision Rule
The route deserves a signature when every identifier, amount, recipient and state-changing transaction matches the reviewed quote. Confirm that source and destination differ, read the token contract or mint and retain native gas for the source transaction. Save the 32-byte order ID. If status remains Created, the existing order keeps its encoded take amount until fulfillment, patching or cancellation, even when later quotes change.
Debridge networks: quick answers
How long should I rely on the same DLN quote?
Treat a DLN quote as short-lived and refresh it immediately before signing. Signing more than about 30 seconds after retrieval introduces quote staleness. Gas, exchange impact and solver operating expenses can move during that interval, even though the chain IDs and token addresses remain unchanged. A new quote may change source input, destination output or transaction value, so the wallet should sign only the transaction built from the reviewed response. Route menus should discard the earlier response rather than reuse its amounts.
Can a DLN route start with a non-reserve token?
A DLN route can start with a non-reserve token when the source chain offers a swap into a solver reserve asset. The builder includes that pre-swap in the source transaction and exposes its impact in the quote. The locked asset may differ from the token selected. If cancellation follows conversion, the returned asset follows the encoded source reserve path rather than an assumed ticker match.
Does an affiliate fee make a DLN route less competitive?
An affiliate fee reduces the input value available to the route and can therefore make the solver economics less attractive. The cross-chain create request expresses that fee as a percentage of the input token and names a source-chain beneficiary. The API caps the configured percentage at 10%. EVM beneficiaries receive it when the order reaches ClaimedUnlock, while Solana beneficiaries withdraw it separately. The route should be requoted after any affiliate-fee change because the solver sees less reserve value behind the same gross user input.
Why is an ERC-20 approval separate from the DLN order transaction?
An ERC-20 approval authorizes the transaction target to transfer the source token before DlnSource creates the order. The approval changes allowance; the next transaction locks the give amount and records the order. Native ETH and BNB do not use ERC-20 allowance. A permit can combine authorization with the route when supported, but the signed amount must cover the quoted input plus source gas for that transaction.
Can the destination recipient differ from the source sender?
The destination recipient may differ from the wallet that creates the DLN order on the source chain. The create request carries a dedicated destination recipient plus separate source and destination authority addresses. That separation supports sending assets to another wallet without transferring management rights implicitly. Address format must match the destination: an EVM address for Ethereum-family chains or a Solana public key for Solana. Review all three fields before signing because they control delivery and later order actions across two distinct execution domains.
Is an exact destination amount available for a cross-chain DLN quote?
DLN supports a reverse-market quote that fixes destination output and calculates required source input automatically. The request sets the destination amount to an exact base-unit value and asks the source amount to resolve automatically. This mode helps when the recipient needs a defined quantity, including the 0.001 SOL destination minimum. The source amount remains quote-sensitive, so rebuild the transaction if market inputs change before signature.