Skip to main content
Composer runs cross-chain deposits between Composer-supported EVM chains: for example, USDC on Arbitrum into a Morpho vault on Base. LI.FI selects the bridge, adds any swaps and runs the deposit on the destination chain. The request is the same as for a same-chain deposit, with different fromChain and toChain values. If a bridge plus a DEX swap into the vault token is cheaper, the quote uses that route and contains no Composer step. Check includedSteps for tool: "composer" to see which one you got.

Route shapes

A cross-chain Composer route has one of two shapes:
  • One transaction. The bridge carries the Composer deposit as a destination call. The user signs once on the source chain, and the bridge runs the deposit when the funds arrive. The route has a single step whose includedSteps look like feeCollection, across, composer. GET /v1/quote only returns this shape.
  • Two transactions. The route has two steps: a bridge step on the source chain, then a separate composer step on the destination chain. The user signs the second transaction on the destination chain after the bridge lands, so the wallet must switch chains and hold gas there. POST /v1/advanced/routes can return this shape; set options.allowSwitchChain: false to exclude it.
Each chain’s part is atomic, but the route as a whole is not: the bridge can succeed while the destination deposit does not run. See Partial failure handling.

Example 1: USDC (Arbitrum) → Morpho vault (Base)

Bridge 1,000 USDC from Arbitrum and deposit it into the Spark-curated Morpho USDC vault on Base. This example runs end to end: quote, approval, transaction and status polling.

More cross-chain routes

These routes use the same flow as Example 1; only the quote parameters change. For more protocols, see Deposit Examples.
  • USDT → Morpho: the vault accepts USDC, so the route also swaps, either before the bridge or on Base. includedSteps shows the chosen sequence.
  • USDC → Aave V3: the user receives aOptUSDCn, Aave’s receipt token for native USDC on Optimism.
  • ETH → wstETH: stakes through Lido’s direct staking on Base. Skip the approval: the source token is native ETH.

Status tracking

After the source-chain transaction confirms, poll GET /v1/status until the status is DONE or FAILED (step 4 of Example 1), then read substatus: For two-transaction routes, the first step’s status reaches DONE when the bridge delivers. Then request the destination step’s transaction and send it on the destination chain. The LI.FI SDK does this for you. For every status and substatus value, see Transaction Status Tracking.

Partial failure handling

In rare cases the bridge succeeds but the destination deposit does not run, for example because the vault price moved past the slippage tolerance. The status is then DONE + PARTIAL, the user holds the bridged asset (for example USDC on Base) instead of vault tokens, and the gas is spent. Show the user which token arrived (receiving.token in the status response) and offer a same-chain deposit from that token. For two-transaction routes, the user is in the same position until they send the destination transaction.

Bridge-then-act with the Composer API

The LI.FI API bundles a bridge with a predefined deposit. To control what happens on the destination chain, use the Composer API. A cross-chain flow bridges the funds into an escrow on the destination chain and then runs a destination flow that you author, with a minimum received that the settlement contract enforces onchain. See Build a cross-chain flow. Cross-chain flows are available only through the Composer API, not through GET /v1/quote.

Bridge and deposit recipe

Bridge, then deposit on the destination chain with a Composer API flow

Cross-chain flows

How the escrow and the destination flow work

Next steps

SDK Integration

Managed cross-chain execution, including two-transaction routes

Supported Protocols

Protocols and chains available for cross-chain deposits