How to Move Crypto Faster With Acrossbridge

acrossbridge can deliver tokens on a destination chain in seconds when your route has a live quote and a relayer can fill it. You deposit on the origin chain, receive a specified output on the destination, and leave the later settlement to the protocol. For a frequent sender, the useful questions are whether the exact token pair is supported, how much arrives, and what happens if no one fills the order.

The Route Determines What You Can Send

A transfer is an on-chain order specifying an input token and amount, an output token and amount, a recipient, and a destination chain. For repeat transfers, acrossbridge lets you price that outcome before committing the origin transaction. Across Bridge supports direct token transfers and routes that include a swap, so check the output token’s contract address rather than relying on its symbol.

Support is specific to the chain pair, tokens, and amount. A route can exist for USDC from Ethereum to one chain yet have no quote for another token or a larger size. Available liquidity and relayer inventory also affect whether a quoted transfer is likely to receive a fast fill.

Relayers Deliver Before Settlement Finishes

A relayer delivers the quoted output from its own inventory after your deposit reaches the origin SpokePool. The deposit emits an event containing the order terms; a relayer observes it and calls the destination SpokePool to fill the order. The destination contract records the fill so another relayer cannot collect payment for the same order.

Your deposit is escrowed in a contract during this process, which is what makes the service non-custodial without keeping the tokens in your wallet. Settlement happens afterward: a dataworker matches fills to deposits, groups repayments into a bundle on Ethereum, and proposes it with a bond. The UMA Optimistic Oracle’s challenge process checks that bundle before relayers are repaid and liquidity pools are rebalanced. Bundles are proposed roughly every 1.5 hours; you do not wait for that cycle to receive a successful fast fill.

The distinction matters when judging speed. A destination fill can take around two seconds on a healthy route, while origin confirmation and status indexing add time you may see in the interface. A pending status for a few seconds does not, by itself, mean the destination transaction failed.

The Quote Reveals the Real Cost

The amount you receive is the useful fee measure for a same-token transfer. The gap between input and output pays the relayer for destination gas, capital and risk, and may pay a liquidity pool for rebalancing. You also pay origin gas for the deposit; an ERC-20 approval can require another transaction unless your wallet flow already covers it.

For example, suppose a quote takes 1,000 USDC and delivers 998.80 USDC. The bridge spread is 1.20 USDC; if origin gas costs about $0.15, the total is about $1.35, or 0.135% of the input. Redo that calculation with the quote’s actual output and your wallet’s gas estimate. On a small transfer, fixed gas can dominate; on a large one, pool utilization and the relayer’s capital cost matter more.

Use the quote’s minimum output when a route includes a swap, because its expected output can move before execution. Fees and maximum amounts vary by route and market conditions, so a stale quote is a poor basis for a repeat order. I would re-quote after changing the amount, recipient, token, or chain, and check the destination token address again before signing.

A Fast Transfer Still Needs a Failure Plan

Send only after the quoted route, recipient, minimum output, and origin gas match what you intend. The normal sequence is to approve the input token if prompted, submit the deposit transaction, then track its deposit ID or origin transaction hash until the destination fill appears. These are the states that change what you do next:

• Pending: The deposit exists, but no destination fill has been recorded. Check the origin transaction before attempting another transfer.
• Filled: The destination SpokePool has delivered the output. Check the recipient’s balance on that chain.
• Expired: The fill deadline passed without a fill. The escrowed deposit is eligible for a refund.
• Refunded: Settlement has returned the funds to the configured refund address.

Across chain transfers can expire when an amount exceeds practical relayer inventory, a route becomes unattractive, or relayers are unavailable. An expired deposit does not refund instantly: the next bundle, challenge period, and cross-chain settlement can take several hours. Check the refund address before sending, especially when the recipient differs from the depositing wallet.

For repeated sends, keep the origin transaction hash until the order is filled or refunded. Choose the route when its quoted minimum output, origin gas, and expected fill time beat the cost of waiting or retrying for your specific amount.