How to choose a wormhole bridge route for your app

Choose a wormhole bridge route by starting with the chains your app needs to connect and the job the transfer must do. A route has a source chain, where the user starts, and a destination chain, where the app needs the asset or message to arrive. Those choices shape what your app must check and show to users. For a transfer between Solana, Ethereum, or another blockchain, use the wormhole bridge for that step: Wormhole is a cross-chain protocol that moves tokens and messages between those chains.

What does a wormhole bridge route need to do?

A route needs to carry the right thing from the right chain to the right place. Decide first whether the app is moving a token, sending a message, or doing both. A token transfer changes where an asset is held. A message lets one chain tell an app or contract on another chain to take an action.

Then name the source and destination in the app’s own terms. If a user deposits an asset on one chain and expects to use it on another, make both steps clear before they confirm. The app should also identify the asset it expects at the destination. A token with a familiar name may not be the same asset across chains.

How should an app compare bridge routes?

Compare routes by how well they fit the user’s task, then check what the app can reliably communicate about the transfer. A route that connects the needed chains but cannot complete the app’s full action is not a useful choice. Check these points:

• Chain pair: Does the route connect the exact source and destination the app requires?
• Transfer type: Does the task need a token, a message, or both?
• Completion: What event tells the app the transfer is ready for the next step?
• Failure handling: What will the user see if the transfer is delayed or does not complete?

For most apps, the better route is the one that covers the full user action and has a clear completion signal. Extra chain options do not help if the app cannot explain what happens after the user sends funds. Keep the chosen route tied to a specific action, such as funding an account or passing a message to a destination app.

What should an app do when a bridge transfer stalls?

Show the transfer’s source, destination, and current status, and let the user know what action is safe to take next. A cross-chain transfer can involve separate steps on two networks, so a delay on the destination does not by itself tell the user whether the source action succeeded. Do not ask the user to repeat a transfer until the app has checked its status.

Before launch, test the full route with the same asset or message flow the app will use. Check what the app records at each step, what it displays while waiting, and how it handles a failed or repeated request. The route choice is part of the product: users need to understand where an action starts, what should arrive, and how the app knows it is done.