Skip to main content
Bridging on DZap Core uses the same getTradeQuotes / trade flow as a same-chain swap — you just set toChain to the destination.

End-to-end: USDC Arbitrum → USDC Base

Tracking the bridge

Bridges settle asynchronously. Track with getTradeTxnStatus:
For multiple in-flight bridges, pass a comma-separated txIds and DZap returns a map.

What can go wrong

  • Refunds — if a bridge fails on the destination side, funds are refunded to the refundee address on the source chain. Always set refundee to a wallet you control.
  • Recipient ≠ sender — for cross-chain you can specify a different recipient (the destination address). Useful for paying on behalf of someone else.
  • Slippage on destination — bridges that swap on settlement (e.g. USDC → ETH on the destination side) honor slippage end-to-end.

Choosing a bridge

You don’t — DZap picks. The quote response surfaces which bridge will be used (protocol field). If you have a preference (e.g. “Across only”), filter the quote response client-side and re-call buildTradeTxn with that protocol. For more advanced flows (bridge + LP-deposit, bridge + claim), see DZap Fuse.
Last modified on May 4, 2026