How to Compare Wormhole Bridge Route Liquidity
If you need tokens for an app now, compare wormhole bridge routes by the token you will actually receive. A low bridge fee may still leave you with a token the app cannot use.
First, note the destination chain and the exact token your app accepts, including its contract address. Then use wormhole bridge to enter your source token, destination chain, and amount. On the Wormhole cross-chain bridge, check the received token’s address before signing.
Liquidity means the amount of a token available to trade or release. Check it for your full transfer amount. A quote for a small test transfer can hide a poor price on a larger one.
A Native Token Route Fits When the App Needs the Native Token
A native token route fits when it delivers the exact token your app accepts without another trade. “Native” here means the token issued for that chain, rather than a wrapped claim on a token held elsewhere.
Some routes burn tokens on one chain and mint them on the other. They need no trading pool to deliver the token, but they may have transfer limits or a queue. Check the quoted amount, any limit, and the estimated wait.
Other routes release tokens from a balance held on the destination chain. That balance must cover your transfer: a 500-token balance cannot release 700 tokens at once. If the balance is hard to find, use the live quote and maximum transfer amount as practical checks.
This option does not fit when your token pair lacks a native route or a limit delays your task. Include network fees on both chains and any fee for automatic completion when comparing amounts.
Token Bridge Fits When a Wrapped Token Is Usable
Token Bridge fits when your app accepts the wrapped token, or you intend to hold it. A wrapped token is a destination token backed by assets locked on the original chain.
The source transaction locks or burns the tokens. Guardians, the network’s message checkers, sign a verified action approval (VAA), which proves the transfer happened. A destination transaction uses that proof to mint wrapped tokens or release the originals.
Minting a wrapped token does not require a destination trading pool. Trading it for another token does. Check the wrapped token’s address against your app’s accepted address; matching names and symbols are not enough.
Manual completion requires a destination transaction and its network fee. Automatic completion charges for someone to finish that step. If you lack the destination chain’s fee token, include the cost of getting it before choosing manual completion.
A Swap Route Fits When the Final Token Matters Most
A swap route fits when a trade can deliver the token your app needs at a fair price. A trading pool is a shared supply of tokens. A thin pool gives larger trades a worse price.
Compare the amount left after the swap, bridge charge, network fees, and completion fee. Price impact is the price change caused by your trade size. Slippage is the further change you allow before the trade fails; check both at your full amount.
Say a wormhole bridge quote starts with 1,000 units. A wrapped route delivers 999, but selling those tokens yields only 986 units of the native token your app needs. A native route delivers 997 after fees, leaving 11 more usable units despite its higher displayed bridge charge.
Refresh swap quotes just before approval, since pool prices change. Choose the route that delivers enough of the exact token your app accepts, at a cost and arrival time that work for your task.