Acrossbridge Transfer Types, Explained

Three broad transfer types define how acrossbridge can move assets: a same-asset transfer, a transfer followed by an action on the destination chain, and a swap that can also trigger an action. The difference is what you ask the destination chain to deliver. Choose by the outcome you need, because each added step brings more flexibility and more things that must work.

What are the three acrossbridge transfer types?

The simplest type moves the same asset between chains, such as sending USDC from one supported network to another. You specify the source and destination chains, the token, the amount, and the recipient; a relayer can supply the destination funds while the protocol settles the transfer afterward.

The second type adds an action after arrival. You can bridge a token and have it used in a destination-chain transaction, such as a deposit into a supported application, instead of receiving idle tokens and submitting another transaction yourself. The linked acrossbridge reference fits this distinction: the request can describe a transfer alone or a destination action too.

The third type swaps as part of the cross-chain request. You specify the asset you are starting with and the output you want on the destination chain; some routes can also execute a follow-up action there. This is useful when the token you hold is not the one you need, but the output amount depends on the route and market conditions.

How does a transfer get from one chain to another?

For a standard deposit, you send tokens into an Across contract on the origin chain with instructions for delivery. A relayer watches for the deposit and may front the requested funds on the destination chain, so you do not have to wait for the protocol’s later accounting and reimbursement to complete.

That fast fill is the common path, but it is not the only one. If relayers do not fill a request, liquidity-provider capital can be used for a slower fill through settlement; this fallback can take longer because it waits for the protocol’s verification process. Acrossbridge’s speed therefore comes from relayers taking on the wait, not from eliminating settlement.

The user-facing request and the back-end fill are separate choices. When you compare quotes, check the estimated output, fee, route, recipient, and any destination action you have attached. A transfer with an extra action can save you a transaction, but it also depends on that action succeeding on the destination chain.

Which transfer type should you choose?

For a straightforward move between chains, same-asset transfer is usually the clearest option: there is no destination swap or contract call to account for. If you already know what you want to do after arrival, combining the transfer with an action can reduce steps and avoid manually coordinating separate transactions.

Choose a cross-chain swap when the output token matters more than receiving the same asset. Review the minimum output and the route before signing, especially if price movement could change how much you receive. Support varies by chain, token, and route, so a transfer type available for one pair may not be offered for another.

There are also different ways to initiate a request, including a wallet transaction, a gasless signature flow, or a persistent deposit address in supported setups. Those are submission methods, not additional transfer types: the core distinction remains whether you move an asset, add a destination action, or swap along the way. For most readers, start with the simplest request that delivers the right asset to the right place.