How Cross-Chain Swaps Work
A cross-chain swap moves value from one blockchain to another and delivers an asset on the destination chain. There are several ways to do it, with different trust, speed, cost and asset-support trade-offs. This page explains the common designs and where Chainflip and Broker as a Service fit.
Terms in this page are defined in the glossary. The role of the broker is explained in What Is a Chainflip Broker?.
The cross-chain problem
Blockchains exist in siloed environments: a chain has no native way to read another chain's state or move another chain's assets (Ethereum.org: Bridges). A swap from BTC on Bitcoin to ETH on Ethereum therefore needs something outside both chains to observe the deposit on one side and deliver the output on the other.
Bridges are one common way to connect chains. Atomic swaps, intent-based systems and native settlement protocols such as Chainflip are others. Each one answers the same questions differently: who verifies the deposit, who holds the assets in between, and what the user receives on the destination chain.
Bridges and wrapped assets
Common bridge designs are lock-and-mint, where the original asset is locked on the source chain and a wrapped copy is minted on the destination chain, and burn-and-mint, where the asset is burned on one chain and minted on the other (Ethereum.org: Bridges). A wrapped asset is a token that represents the original on another chain; its value depends on the bridge that backs it.
Ethereum.org groups bridges into trusted designs, verified by an external set of verifiers, and trustless designs, which rely on the connected chains themselves. It lists the risks of using any bridge as:
- Smart contract risk: one flaw in a bridge contract can expose the assets it holds.
- Systemic financial risk: many bridges use wrapped assets, and wrapped versions of tokens have been exploited.
- Counterparty risk: some bridges ask users to trust that their validators will not collude.
The same page states that bridges have no perfect solution, only trade-offs between security, convenience, connectivity, the ability to pass more complex data, and cost-effectiveness.
Atomic swaps
An atomic swap exchanges assets directly between two parties on two chains, with no wrapped asset in between. It is usually built from Hashed Time-Locked Contracts (HTLCs): a conditional payment with a hash lock, which the receiver unlocks by revealing a secret, and a time lock, after which the sender can take the funds back (Bitcoin Optech: HTLC). Because both legs use the same secret, either both payments complete or both can be reclaimed. HTLCs are also the building block of the Lightning Network (BIP 199, a historical specification whose status is Closed).
An atomic swap needs a counterparty willing to take the other side at the agreed rate, and both chains must support the hash and time locks the contract uses. Ethereum.org lists atomic swaps among the transfer methods used by liquidity-network bridges (Ethereum.org: Bridges).
Intents and solvers
An intent is a signed set of declarative constraints: the user states the outcome they want, such as "at least this much of asset B on chain Y for this much of asset A on chain X", and outsources how the transaction is built (Paradigm: Intent-based architectures and their risks). At least one other party must be aware of the intent, incentivised to execute it and able to do so in time.
ERC-7683, a Draft standard, describes cross-chain intents in this model: users express the outcome they want as orders, and solvers, also called fillers, execute those orders and are paid for doing so. Paradigm describes the risks of intent systems, including the trust placed in the executing party, the incentive not to share order flow, MEV, and the opacity of off-chain execution.
Chainflip's native settlement model
Chainflip is a protocol for swapping native assets between chains. A permissionless network of up to 150 validators uses threshold signatures (TSS) to control vaults, simple smart contracts and wallets on each supported chain; the protocol's own blockchain, the State Chain, is a Substrate-based chain that keeps the accounting (Chainflip: Protocol Overview).
Swaps execute in Chainflip's Just-In-Time AMM. The AMM is virtual: funds are not held in on-chain pools of wrapped assets, but traded as balances on the State Chain and settled with the native assets the vaults hold. Validators witness deposits into the vaults and broadcast the output to the destination chain (Chainflip: Protocol Overview).
The deposit-address flow
The most common way to start a Chainflip swap is a deposit channel (Chainflip: How Swapping Works):
- A broker opens a deposit channel on the State Chain with the destination asset, destination address and swap parameters, and returns a deposit address on the source chain.
- The user sends the source asset to that address.
- Validators witness the deposit once a chain-specific safety margin of block confirmations has passed. The safety margin varies by chain; Chainflip lists it per chain in its ingress documentation.
- The swap executes in the JIT AMM.
- The network broadcasts the native destination asset to the destination address.
Chainflip calls this flow fire-and-forget: once the deposit is made, the user does not need to do anything for the swap to complete. With Broker as a Service, Starting a Swap opens the channel and Get Swap Status follows the swap through these steps.
Vault swaps
A vault swap skips the deposit channel: the user's transaction sends funds directly to a Chainflip vault, or calls the vault contract or program, with the swap parameters encoded in the transaction (Chainflip: Vault Swaps). Chainflip lists the downsides: a vault swap transaction is single-use, whereas deposit channels can be used multiple times once opened; it is more complex than a simple transfer, which makes integration harder and can cost the swapper more; and Chainflip's documentation lists chain-specific limitations.
Broker as a Service returns unsigned vault swap payloads for Bitcoin, EVM chains, Solana and Tron, which your application or wallet signs and submits; see Vault Swap Transaction Payloads.
Trade-offs
None of these designs is right for every case. The questions to compare them on:
- Trust assumptions. Who verifies the deposit and controls the assets in between: a bridge's verifiers, the two parties of an atomic swap, a solver, or a validator network such as Chainflip's (Ethereum.org: Bridges; Chainflip: Protocol Overview).
- What you receive. A wrapped asset that depends on its bridge, or the native asset of the destination chain.
- Confirmation delay and finality. Any cross-chain design waits for the source chain's deposit to be final enough to act on; how long depends on the chain (Chainflip: Ingress).
- Cost. Network fees on both chains, protocol and broker fees, and the price impact of the available liquidity.
- Asset and chain support. Which chains and assets a design connects, and whether it can carry more than a transfer.
- Refunds and expiry. What happens when the price is not met or a deposit arrives late. On Chainflip, a swap that cannot meet its minimum price within its retry duration is refunded to the refund address (Chainflip: Swapping Basics).
- Liquidity. Atomic swaps need a counterparty for each trade, intents need solvers willing to fill, and an AMM needs liquidity in its pools.
Where Chainflip and BaaS fit
Chainflip is the settlement protocol: it witnesses native deposits, executes the swap and delivers native assets, without wrapped tokens or a bridge (Chainflip: Protocol Overview).
Broker as a Service operates a hosted Chainflip broker (Welcome to Broker as a Service) and exposes it through a REST API, a JSON-RPC drop-in and an MCP server. Your application asks for a quote, opens a deposit channel or builds a vault swap payload, and follows the status. The user sends the source asset to the deposit address, or signs the vault swap transaction, and the output goes to the destination address; no account is created for the end user (Starting a Swap).
- What Is a Chainflip Broker? explains the broker's role and the choice between running your own and using a hosted one.
- Use Cases covers why teams use a hosted broker.
- Getting Started takes you from an API key to your first swap, through Asking for a Quote, Starting a Swap and Get Swap Status.
Sources
All sources were accessed on 2026-11-18.
- Ethereum.org, Bridges: siloed chains, bridge designs, wrapped assets, risks and trade-offs.
- Bitcoin Optech, Hash Time Locked Contract (HTLC): hash lock, time lock, use in atomic swaps and Lightning.
- Bitcoin Improvement Proposals, BIP 199: Hashed Time-Locked Contract transactions: the historical HTLC specification (status Closed).
- Paradigm, Intent-based architectures and their risks: intents as declarative constraints and their risks.
- Ethereum Improvement Proposals, ERC-7683: Cross Chain Intents: the Draft order and solver model.
- Chainflip, Protocol Overview: validators, vaults, State Chain and the virtual AMM.
- Chainflip, JIT AMM Protocol: the Just-In-Time AMM.
- Chainflip, How Swapping Works: the native swap flow.
- Chainflip, Ingress, Witnessing Deposits: safety margins per chain.
- Chainflip, Vault Swaps: vault swaps and their downsides.
- Chainflip, Swapping Basics: minimum price, retry duration and refunds.
- Broker as a Service: Welcome to Broker as a Service, Starting a Swap, Vault Swap Transaction Payloads.