> For the complete documentation index, see [llms.txt](https://across-bridge.gitbook.io/across-bridge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://across-bridge.gitbook.io/across-bridge-docs/how-to-set-up-across-bridge-wallet-network-first-transfer.md).

# How to Set Up Across Bridge: Wallet, Network, First Transfer

<figure><img src="/files/ZB2oFiN7tSJjUTBP7iIW" alt=""><figcaption></figcaption></figure>

[Across Bridge](https://across-bridge.app/) helps you move crypto from one chain to another without treating the bridge like a swap app. If your funds are on Ethereum but you want to use them on Arbitrum, Base, Optimism, Polygon, zkSync, or another L2, the setup comes down to a few careful choices: wallet, source chain, destination chain, token, amount, and fees.

The risk for beginners is not usually the button clicking. It is choosing the wrong network, sending the wrong token, ignoring gas, or assuming every bridge works like a decentralized exchange.

Across is an intents-based cross-chain bridge. You deposit on the source chain, a relayer quickly fills the request on the destination chain, and the relayer is later reimbursed after optimistic settlement. That is why transfers can feel fast, even though settlement continues in the background.

### What You'll Need

Have these ready before you bridge:

* A non-custodial wallet, such as MetaMask
* Crypto on the source chain you want to bridge from
* The destination chain where you want funds to arrive
* A little native token for gas on the source chain
* Time to review the token, amount, route, and fees

The source chain is where your funds are now. The destination chain is where you want to use them next. Your wallet address may be the same across Ethereum, Arbitrum, Optimism, Base, Polygon, and zkSync, but the balances are separate on each network.

### Set Up Across Bridge the Right Way

Step 1: Connect your wallet.

Open the bridge interface and connect your wallet. If you use MetaMask, your browser will ask you to confirm the connection. Connecting does not move funds by itself; it lets the app read your public address and prepare transactions for review.

Check that the wallet account is the one you actually want to use. A correct transfer from the wrong account is still a problem.

Step 2: Pick the source and destination chains.

Choose the chain where your funds currently sit as the source chain. Then choose the chain where you want the funds to arrive as the destination chain.

Do not rush this step. If your funds are on Arbitrum, the source should be Arbitrum. If you want the funds on Base, the destination should be Base. Ethereum, Arbitrum, Optimism, Base, Polygon, and zkSync are separate networks, even if they appear inside the same wallet.

Step 3: Select the token and amount.

Choose the token you want to move and enter the amount. For a first transfer, use a small test amount. The goal is to prove that your wallet, route, token, and destination chain are correct before moving more.

Across is a bridge, not a swap AMM. You are asking for value to move from one chain to another, not mainly trading through a liquidity pool. The ACX token belongs to the Across ecosystem, but you do not need ACX to understand a basic bridge transfer.

Step 4: Review fees and gas.

Before approving, look at the estimated received amount, the bridge fee, and the gas cost in your wallet. The bridge fee pays for the route. Gas is the network cost for processing transactions. These are not the same thing.

Think about gas after arrival too. If you bridge funds to Base or Optimism and then want to use an app there, you may need native gas on that destination chain.

Step 5: Approve and confirm the transfer.

Some tokens require an approval transaction before the bridge transfer. If your wallet asks for approval, read the spending permission and confirm that the token and network are correct.

When everything checks out, use [Across Bridge](https://across-bridge.app/) to submit the transfer. Your wallet may ask for one confirmation for approval and another for the actual bridge transaction. Read both before signing.

After your source-chain transaction is accepted, the relayer can fill the request on the destination chain. Later, optimistic settlement reimburses the relayer.

Step 6: Check the destination chain.

Once the transfer is filled, switch your wallet to the destination chain and check the balance there. If you bridged to Polygon, look on Polygon. If you bridged to Base, look on Base.

If the token does not appear immediately, do not repeat the transfer without checking. Some wallets need you to display or import a token on a specific network. First confirm that you are viewing the correct destination chain.

### Common Mistakes That Cost Beginners Money

Wrong destination chain: Decide where you need the funds before you bridge. Moving funds to the wrong L2 can mean extra fees and extra steps.

Wrong token: Check the token symbol and network version before approval. Similar names can be misleading.

Ignoring gas: Keep enough native token for the source-chain transaction, and remember that later destination-chain activity may also need gas.

Treating a bridge like a swap: Across is for cross-chain bridging. If your goal is a token swap, understand whether another app or route is involved.

Using unofficial front-ends: Be careful with links from ads, comments, direct messages, or copied posts. A fake front-end can make a normal wallet confirmation dangerous.

Skipping a test transfer: For a new wallet, new chain, or larger amount, a small first transfer is practical. It confirms the route before more money is involved.

Bridge risk is real. Smart-contract risk, changing gas fees, liquidity limits, and user error can all matter. Fast does not remove risk.

### First Transfer Checklist

Before you confirm, make sure:

* Your wallet is connected to the right account
* The source chain matches where the funds are now
* The destination chain matches where you want to use the funds
* The token and amount are correct
* The bridge fee and gas estimate make sense
* You are leaving enough gas for the transaction
* You understand this is a bridge transfer, not an AMM swap

That checklist is simple, but it catches most beginner errors.

### Make Your First Transfer Carefully

Across makes cross-chain bridging feel fast because relayers fill transfers before they are later reimbursed through optimistic settlement. Your job is to give the system the right instructions: correct wallet, correct source chain, correct destination chain, correct token, and a realistic fee check.

Start with a small transfer on [Across Bridge](https://across-bridge.app/), confirm that the funds arrive on the destination chain, and only then consider moving a larger amount.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://across-bridge.gitbook.io/across-bridge-docs/how-to-set-up-across-bridge-wallet-network-first-transfer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
