Cross-chain / Bridge·EVM · Solana · Multi-chain
deBridge
Intent-based cross-chain swap and messaging infrastructure. The deBridge Liquidity Network (DLN) lets users post intents that competing solvers fill on the destination chain, with 1:1 target-output guarantees (no slippage) and near-instant settlement across 26+ chains.
- 01intent-based cross-chain swaps with guaranteed output
- 02EVM <-> Solana fast settlement
- 03embedded cross-chain swap widget
- 04stablecoin transfers with deep solver liquidity
- 05AI agent / MCP-driven bridging flows
- pnpm add @debridge-finance/dln-client viem
- pnpm add @debridge-finance/dln-taker
| Variable | Scope | Description |
|---|---|---|
| DEBRIDGE_API_URL | Client | DLN API base URL (default `https://dln.debridge.finance/v1.0`). Public access works for low RPS; commercial use requires an API key. |
| DEBRIDGE_API_KEY | Server | Optional DLN API key for elevated rate limits and integrator-fee attribution. Request via debridge.finance. |
Use the DLN REST API for intent-based swaps: `GET https://dln.debridge.finance/v1.0/dln/order/create-tx?srcChainId=&srcChainTokenIn=&srcChainTokenInAmount=&dstChainId=&dstChainTokenOut=&dstChainTokenOutAmount=auto&dstChainTokenOutRecipient=&srcChainOrderAuthorityAddress=&dstChainOrderAuthorityAddress=&affiliateFeePercent=` returns a quote and a ready-to-sign `tx` payload. Submit the ERC20 approval to `tx.allowanceTarget`, then send `tx.data` to `tx.to` with `value = tx.value`. Poll order status via `GET /v1.0/dln/order/{orderId}` until `state === 'Fulfilled'` (and `ClaimedUnlock` for finality). Solver fills the destination 1:1 to `dstChainTokenOutAmount` — there is NO destination slippage. For programmatic Solana / EVM integration the `@debridge-finance/dln-client` SDK exposes typed contract bindings. Chain IDs follow EVM conventions for EVM, with synthetic IDs for Solana (`7565164`).
- ⚑DLN is intent-based with a 1:1 target output: you specify EXACT `dstChainTokenOutAmount` (or use `auto` for max-out). The user signs an order; if no solver fills within the order's `giveOrderExpirationTime` it auto-cancels and refunds — handle the `OrderCancelled` state.
- ⚑Solana uses a synthetic chain ID (`7565164`); the order-create-tx response returns a Solana-specific `tx` payload, not EVM calldata. Branch transaction submission by chain.
- ⚑`affiliateFeePercent` and `affiliateFeeRecipient` must both be set together for fee attribution. Setting only one silently no-ops.
- ⚑Solver liquidity is concentrated on stablecoin pairs and major routes; long-tail tokens may quote but never get filled — treat unfilled-after-N-minutes as a failure and surface a refund flow.
- ⚑Public API rate limit is low (a few RPS) — production traffic must use an API key or self-host the relay infra.
- ⚑The order's `srcChainOrderAuthorityAddress` controls cancellation/refund. If this differs from the user's signer they cannot self-cancel — usually keep it equal to the signer.
- ⚑MCP integration (Feb 2026) uses a separate JSON-RPC interface; do not assume the REST API and MCP semantics are 1:1.