Across Bridge: What Actually Happens in August 2026
Across bridge is a fast way to move tokens between supported blockchains, but the first attempt often goes wrong before the transfer starts: the quote is stale, the token is unsupported, or the wallet is connected to the wrong origin chain. Across handles the route and destination fill, while you still need to check the live quote, approval, recipient, and limits before signing.
Why did the first transfer seem stuck?
Across usually fills a mainnet transfer in about two seconds, but that does not mean the entire transaction is instant. Your wallet must first submit the origin-chain transaction, wait for it to confirm, and then a relayer supplies the destination-chain funds. If the origin transaction is still pending, the bridge has not received a deposit to fill.
Open the deposit status rather than repeatedly submitting the same transfer. A second attempt can create a duplicate deposit, while the original may still complete normally. Also check that the recipient address is correct and that you are viewing the destination network in your wallet.
Which number matters more than the advertised speed?
The output amount matters more than a headline fee or speed claim. Across calculates the total fee as the difference between what you deposit and what you receive. That amount can change with route, token, liquidity, gas prices, and relayer conditions, so a quote should be treated as live data rather than a permanent price.
| Part of the process | Practical expectation | What to check |
|---|---|---|
| Mainnet fill | About 2 seconds for most transfers | Whether the origin transaction confirmed |
| Testnet fill | About 1 minute | Use small test amounts only |
| Relayer reimbursement | About 1.5 hours | This is settlement, not your wait for funds |
| Deposit-address flow | 24-hour address lifetime | Send only the quoted asset and amount |
The distinction is useful: a user may receive funds in seconds even though the relayer is reimbursed much later. Those are separate stages.
How should you prepare a route before signing?
- Select the origin and destination chains deliberately. “Connected” is not the same as “selected,” and a wallet can remain connected to a different network than the route you intended.
- Choose the exact token on both sides. Native USDC, bridged USDC, USDT0, ETH, and similarly named assets are not interchangeable. Check the current token list and contract address through the Across chains and contracts documentation.
- Read the quote’s minimum output, fee breakdown, expected fill time, and limits. If the amount is below the route minimum, changing networks or increasing the amount may be necessary.
For a normal wallet transfer, the Swap API returns the transaction to execute. You approve the token if required, sign the deposit, and then track its status. The protocol chooses the settlement path under the hood, so there is no separate relayer-selection step for you.
When is Across a better choice than a traditional bridge?
Across is strongest when you want the destination asset quickly and do not want to wait for a canonical message-passing process. It is especially convenient for moving stablecoins between active rollups and then using those funds immediately in a destination-chain application.
It is less forgiving of casual assumptions. Support changes, route limits vary, and sponsored fees can disappear. The current fee documentation explains why two otherwise similar routes can produce different outputs.
That is why the sensible starting point is the Across bridge: use it to generate a fresh route, then judge the actual output and status—not a remembered quote from your last transfer.