How a Bridge Delivers Tokens Across Networks

A bridge can deliver a token to a wallet on a network that does not issue it by moving value across chains and arranging a matching asset on the destination. The route may create a token representation there, or swap the source asset for a token the destination network already supports. The distinction matters: a wallet address can be the same across networks, but the assets and balances on each network are separate.

A cross-chain route connects contracts and services on both sides. The source contract receives or locks an asset, while a bridge’s relayer or validator system reports that event to the destination. A destination contract then releases or creates an asset, or a swap service uses available liquidity to deliver a different one. For a worked example of a route that turns ETH into SOL in one cross-chain swap, see mayan bridge. The route’s exact steps depend on which networks and tokens it supports.

What happens when a token crosses networks?

A cross-chain transfer starts with a transaction on the source network. The user chooses a source asset, a destination network, and a supported destination asset or token representation. The route shows the expected output and asks the user to approve the relevant token allowance or transaction.

In a lock-and-mint design, the source contract holds the original tokens. A bridge system observes the deposit and sends proof to a contract on the destination network. That contract mints a corresponding representation to the recipient. The representation is a claim linked to the locked asset; it is not the same token contract as the original. When the user returns it through the bridge, the destination representation can be burned and the source asset released.

Other routes use liquidity pools. Instead of minting a new representation, the route can pay the recipient from assets already available on the destination network. Some routes combine a bridge transfer with a swap, so the asset delivered differs from the one sent. These steps can be handled by separate contracts or coordinated by a routing service.

How can a network receive a token it does not have?

The network can receive a token contract deployed there, but it cannot receive the source network’s original contract or balance. If the bridge supports a wrapped version, it creates or releases that representation on the destination. If the goal is a native asset or another established token, the route must also find a way to acquire it, usually through destination liquidity and a swap.

That difference affects what the recipient can do next. A wrapped token may work in applications that recognize that representation, but it may not be accepted everywhere the original asset is. A destination swap can deliver a more familiar asset, but the output depends on available liquidity, fees, and the route’s execution conditions. A route may also fail if the destination token or recipient format is unsupported.

What should you check before sending?

Check the route’s supported source and destination networks, then confirm the exact token contract or asset name shown for the output. A ticker or token name alone does not identify a contract. Also confirm which address receives the asset and whether you need the destination network’s native token to pay for later transactions.

• Confirm the destination network and recipient address.
• Check whether the output is a wrapped representation or a swapped asset.
• Review the quoted output, fees, and any minimum received before approving.
• Keep enough destination gas token for a later transfer or application transaction.

The useful mental model is a parcel forwarded between depots: the source network records what was sent, and the route arranges a deliverable asset at the destination. The bridge does not make one network share another’s token contracts. It links separate systems through custody, verification, liquidity, or a combination of them. For most users, the better route is the one that clearly names the destination asset and leaves them with a token they can use there.