Across Bridge is the better choice when the cost of waiting exceeds the cost shown in a live quote. The old cross-chain routine made users choose a route, lock assets, wait for finality, and hope destination liquidity held. An intent-based transfer changes the job: the user specifies the outcome, while relayers compete to deliver it.
That distinction matters to anyone defending the choice internally. The decision point is not another explainer but the bridge itself: across bridge. Across Bridge is an intent-based way to move or swap assets across chains without making the user manage the settlement path.
How fast is Across Bridge compared with a traditional bridge?
Across reports most mainnet fills in about two seconds; its settlement, however, operates on a separate clock of roughly 1.5 hours. That is not a contradiction. A relayer fronts destination-chain capital immediately, then is repaid later through aggregated settlement. For a trader, treasury operator, or product team, the practical gain is measured in minutes or days avoided—not merely a prettier interface.
| Decision number | What it means | Why it matters |
|---|---|---|
| ~2 seconds | Expected fill time for most transfers | Funds can be usable on the destination chain almost immediately. |
| ~1.5 hours | Relayer reimbursement cadence | The protocol shifts settlement waiting away from the user. |
| 27 mainnet chains | Reported chain coverage | Fewer separate bridge integrations or liquidity decisions. |
| 8 testnets | Reported development coverage | Teams can test before committing production capital. |
| Up to $10 million | Native USDC settlement cited for CCTP V2 routes | Large transfers still require route-specific limits and quotes. |
What does Across Bridge cost?
The honest answer is that there is no single percentage worth quoting. The total is the gap between the amount sent and the amount received, composed of an LP fee and a relayer fee. The relayer portion reflects destination gas, capital tied up during reimbursement, and execution risk; the LP portion changes with route utilization and rebalancing needs.
The case for Across is that pricing is route-specific and visible before execution. The case against it is equally important: a cheap-looking route can stop being cheap when gas, token liquidity, or an added application fee changes. The right approval standard is therefore a fresh quote, not a remembered fee.
Is Across Bridge secure enough for a business transfer?
Its design reduces settlement work by aggregating many fills into one bundle, making that layer O(1) rather than one verification per fill. Bundles are proposed with a bond and can be challenged through UMA’s optimistic verification process. That is a meaningful efficiency advantage, but it is not a reason to ignore operational controls.
- Verify the origin and destination chain, token, recipient, and minimum received amount.
- Check the live quote, including any application fee and route limit.
- Start with a test transfer when an address or route is new.
When is Across Bridge the wrong choice?
It is the wrong choice when the destination chain, token, limit, or quoted output does not match the required outcome. It is also the wrong choice for anyone who cannot accept smart-contract, relayer, chain-finality, or operational risk. But when the real alternative is manual route selection followed by avoidable waiting, Across Bridge makes the stronger economic case: it buys back time while showing the price before the transfer is made.