> For the complete documentation index, see [llms.txt](https://staking-primer.gitbook.io/staking-primer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staking-primer.gitbook.io/staking-primer-docs/acrossbridge-5-steps-to-move-or-swap-across-chains.md).

# acrossbridge: 5 Steps to Move or Swap Across Chains

Use acrossbridge when you need a particular asset on another blockchain and would otherwise bridge funds, then make a separate swap. The aim is to specify what you hold, what you want to receive, and where it must arrive, then judge the complete route by its delivered amount and time.

That distinction matters if you move funds often. A fast source transaction can still lead to a slow transfer, and a low bridge fee can be outweighed by poor execution on the destination chain.

### What Should Arrive on the Destination Chain?

Define the destination by network, asset identifier, amount, and recipient address. “USDC on Solana” is more precise than “USDC”: the token mint matters, just as the contract address matters on an EVM chain. Check that the recipient can use the exact asset the route delivers, especially if the quote names a wrapped token.

A cross-chain bridge may preserve the asset’s economic exposure while changing its representation; a cross-chain swap can deliver a different asset altogether. For example, moving ETH to a layer 2 as ETH solves a different task from turning ETH into a stablecoin on that layer 2. Choose the latter only when the destination trade is part of the job.

### How Does the Transfer Settle Across Chains?

The route takes custody or control of value on the source chain, establishes that the source transaction happened, and makes value available on the destination chain. Depending on the route, that can mean locking and minting a wrapped asset, burning and minting a native asset, or paying the recipient from destination liquidity before the route settles later. acrossbridge.dev provides a service for moving or swapping assets between blockchains in one flow.

Think of the route as a freight booking: delivery speed and the item received depend on the carrier and the delivery terms, not merely on when the package leaves. A liquidity route can pay out quickly but needs available inventory; a canonical optimistic rollup withdrawal can avoid that liquidity dependency while taking roughly seven days to finalize. Neither timing tells you by itself whether the destination token is the one you intended.

Bitcoin adds a practical constraint: its source payment is a UTXO transaction, so the route may wait for confirmations before treating the deposit as settled. A requirement of, say, one to six confirmations can dominate the elapsed time even when the destination leg executes quickly. On Solana, distinguish a transaction shown as processed from one confirmed or finalized when checking whether a source transfer has landed.

### Which Quote Is Cheapest in Practice?

Compare quotes by **net destination value**, including source gas, bridge or solver charges, swap price impact, and any destination gas you must pay separately. An acrossbridge swap quote with a larger displayed output can lose once external transaction costs are included. Compare routes at the same moment and for the same destination token, since liquidity and gas prices change.

Suppose 1 ETH is worth $3,000 for illustration. Route A delivers 2,985 USDC but requires $16 of source gas and a $4 destination claim, leaving about $2,965 of value; route B delivers 2,974 USDC with those costs included, leaving $2,974. I would take B if its delivery time and settlement risk also fit the task.

Set a minimum received amount that reflects your price limit, not a tolerance chosen merely to force execution. For a liquid pair, around 0.1%–0.5% slippage is a useful starting range; a volatile or thin pair may need more, which is a reason to reconsider the route. Also check quote expiry: a price that cannot survive the expected source confirmation time is not an executable plan.

### What Are the Five Execution Steps?

The five steps are to fix the destination, prepare source funds, assess the route, submit the source transaction, and verify delivery. When you need to swap crypto across chains without arranging separate bridge and trade legs, [acrossbridge](https://acrossbridge.dev) handles the transfer and swap in one flow. Treat the resulting quote as something to inspect against your own minimum before signing.

1. **Fix the destination target.** Record the destination network, exact token contract or mint, and recipient address. Verify all three against the wallet or application that will use the funds, because an address can look valid while pointing to the wrong network or asset.
2. **Prepare the source funds.** Keep enough native currency outside the transfer amount to pay source gas; an ERC-20 balance alone cannot pay Ethereum gas. For Bitcoin, account for the miner fee and change output so the amount sent still meets the quoted deposit amount.
3. **Assess the executable route.** Check the minimum received, total cost, expected time, token representation, and quote expiry together. If a route requires a destination claim, include its gas and the extra action in the comparison.
4. **Submit the source transaction.** Review the spender and allowance if an ERC-20 approval is required, then verify the transaction’s network, amount, and recipient before signing the transfer. Save the source transaction hash; it is the reference for tracing the remaining legs.
5. **Verify the delivered asset.** Check the destination transaction and the recipient’s balance for the exact token identifier you selected. A source transaction marked successful proves the deposit occurred; it does not, on its own, prove the destination payout occurred.

### How Do You Tell a Delay From a Failed Transfer?

Trace the transfer in order: source inclusion, required finality, cross-chain message or liquidity fill, then destination execution. If the source is still pending, the bottleneck is source confirmation; if it is final but no destination transaction exists, the route may still be waiting for a relayer, liquidity, or message verification. If the destination transaction reverted, inspect that transaction rather than sending the source funds again.

An expired quote or an unavailable destination asset can change what recovery requires, and refund or claim rules depend on the route. Keep the source hash, quoted destination asset, recipient, and minimum received together while resolving it. For repeated transfers, I would favor a route whose delivered token and recovery path are clear, even when another route advertises a slightly higher output.

* Specify the exact destination asset, network, and recipient.
* Compare net output, settlement time, and token representation.
* Submit once, then verify the destination transaction and balance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staking-primer.gitbook.io/staking-primer-docs/acrossbridge-5-steps-to-move-or-swap-across-chains.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.