Cross-Chain Swap

Overview

A cross-chain swap lets a user pay with one asset and network while receiving another asset on a different network. Execution may combine a same-chain trade with a bridge, use destination liquidity from a solver, or exchange through hash-locked atomic transactions.

Quotes depend on exchange rate, route fees, gas, liquidity, slippage, confirmation time, and refund conditions. The source asset may be spent before destination delivery, so the provider’s settlement and recovery model is important. Interfaces should specify exact token contracts, chains, minimum output, recipient, expiry, and approval scope. Integrators must reconcile order, source, and destination identifiers and handle partial failure idempotently. The swap is complete only after the expected destination asset reaches final settlement.

Paused contracts, depleted liquidity, delayed proofs, or destination failure should enter review rather than being reported as a completed cross-chain payment. Reliable operation requires separate status for every stage, timeout and replay protection, route-specific monitoring, and a documented recovery path. The workflow should be modeled as a multi-stage operation: source authorization, source inclusion and finality, message or proof production, relay, destination verification, destination execution, and destination finality. Completion of an early stage does not prove that value or instructions reached the destination.

Relevant assumptions include the validator or signer set, multisignature policy, light-client or proof design, relayers, upgrade authority, rate limits, and liquidity providers. Being described as official does not eliminate the underlying trust and control assumptions. The security model depends on the exact verification route. Implementation note: Cross-chain swaps combine trading and interoperability risk, requiring precise quotes, asset identification, execution tracking, and refund rules.