Across bridge is now sold on a number: roughly two seconds for a mainnet fill. The catch is that “fill” is not the same as finality, settlement, or a guaranteed end-to-end arrival time. That distinction matters if a previous bridge left you waiting, overpaid, or holding the wrong asset. This article explains what changed, what the two-second figure contains, and the current approval path: fresh quote, correct token, correct recipient, and verified destination.
~2 seconds describes the relayer fill, not the whole blockchain journey
Across uses an intent model. You deposit on the origin chain, then a relayer uses its own destination-chain capital to send the requested asset to you. That user-facing fill can happen in about two seconds on selected mainnet routes, according to the Across feature documentation.
The number does not erase the origin-chain transaction, wallet confirmation, network congestion, or later settlement. Relayers are reimbursed through a batched process after the fill, so “fast” means the recipient usually receives funds before the system finishes its accounting. Last year’s advice to judge a bridge by its canonical message-passing or claim delay is therefore the wrong test for Across.
What is across bridge now, if it is not a conventional token tunnel?
Across Bridge is the user-facing application for cross-chain transfers, while the underlying protocol is a marketplace for intents. You specify what you want to move and where it should arrive; competing relayers decide whether and how quickly to fill that request. You are not normally waiting for a wrapped token to be minted and then redeemed through a second claim.
That design explains both the speed and the catch. The transfer depends on route liquidity, relayer availability, chain conditions, and the exact asset pair. A quote that looked good yesterday is not evidence for today’s transfer.
The displayed fee is built from LP and relayer costs
The total fee is the difference between the amount deposited and the amount received. Across separates it into two main protocol components:
| Component | What it pays for |
|---|---|
| LP fee | Liquidity-provider capital use and cross-chain rebalancing |
| Relayer fee | Destination gas, capital tied up before reimbursement, and execution risk |
The route, token, transfer size, pool utilization, gas market, and repayment chain can change the result. Some routes may show zero LP fees or promotional zero-fee bridge costs, but that is route-specific. An integrator may also add an app fee, which is separate from Across’s protocol fees. The fee breakdown documentation explains why the number must be fetched fresh.
Native USDC routes changed the safest asset choice
Across has been moving eligible USDC routes toward Circle’s Cross-Chain Transfer Protocol. That means native USDC can be used instead of assuming every USDC-looking token is interchangeable. Bridged USDC may no longer be accepted on migrated routes, so selecting the symbol alone is unsafe. Confirm the chain, token contract, input amount, output amount, and recipient before approving.
Four checks prevent the expensive version of a fast bridge
- Request a new quote immediately before sending; do not reuse an old fee or expected-time screenshot.
- Check the route’s minimum and maximum limits, output token, recipient address, and expected fill time.
- Verify that the wallet is signing on the intended origin chain and that the asset is the correct native or bridged version.
- After the deposit, track the transaction instead of submitting a second transfer or assuming a manual claim is required.
The useful figure is still about two seconds—but only when read correctly. Across is faster because relayers front the destination funds; the price of that convenience is variable fees and a route that must be checked at the moment you use it.