Across Bridge: How Fast and How Much Does It Cost?

Verdict: The across bridge is a strong first choice when you want a fast, simple transfer between supported chains, especially for familiar assets such as USDC. Its headline advantage is speed, but the trade-off is variable pricing, chain-and-token eligibility checks, and a settlement system whose behind-the-scenes work continues after your funds arrive.

How fast is the Across bridge?

Across says most mainnet transfers fill in about two seconds. That is the time a relayer takes to deliver the output asset on the destination chain. A relayer is a network participant that uses its own funds to pay you first, then waits for reimbursement from the protocol.

This distinction matters. Your funds can arrive quickly even though final settlement happens later. Across says relayers are generally reimbursed through bundled settlement roughly every 1.5 hours. For a normal user, that delay stays in the background; for someone integrating the system, it is part of the design.

What does Across bridge cost?

There is no single Across bridge fee. The quoted cost is the difference between the amount deposited and the amount received. It is made from two main parts: an LP fee paid to liquidity providers and a relayer fee covering destination-chain gas, locked capital and operational risk.

Liquidity providers, or LPs, supply capital to the protocol’s pools. Their fee changes with pool utilization: when available liquidity is plentiful, the charge can be lower; when a pool is heavily used, the fee curve rises. The relayer fee also varies by destination chain and route. Ethereum, for example, can require more gas than a lower-cost network.

That makes the quote more useful than a headline “flat fee.” Check the actual output amount and fee breakdown immediately before approving the transaction. Developers should use Across’s Swap API, which returns the transaction and fee details; an integrator may also add a separate application fee.

What happens when you use Across?

1. Select the origin chain, destination chain, token and amount.
2. Review the returned quote, output amount, estimated fill time and fee breakdown.
3. Approve the token and submit the generated transaction.
4. Wait for the relayer to fill the transfer on the destination chain.
5. Check the deposit status if the destination balance does not appear as expected.

Why does Across bridge work so quickly?

Across does not wait for a traditional bridge message to complete before delivering funds. Your deposit is recorded in an origin SpokePool, a smart contract handling deposits on that chain. A relayer then fills the request from a destination SpokePool using its own capital.

Later, the Dataworker groups completed fills into a bundle and submits it to the HubPool on Ethereum. The UMA Optimistic Oracle provides the dispute mechanism: a proposed bundle is accepted unless someone challenges it with evidence. This architecture is what separates fast user delivery from slower protocol settlement.

Who should use Across?

Across suits beginners who want a straightforward route, developers who prefer one Swap API instead of separate integrations, and users moving assets across supported networks without waiting through lengthy finality periods.

It is less suitable if your exact chain or token is unsupported, if you need a fixed fee before requesting a quote, or if you mistake a two-second fill for instant final settlement. Check support and the live quote first. For the routes it covers, Across earns its reputation chiefly through fast delivery and a clear explanation of what that speed costs.