Crypto treasuries should compare what arrives, not just quotes

Crypto treasuries moving funds between chains should compare the amount that arrives, because a large quote can shrink after fees and swaps. Liquidity is split across networks, tokens and trading pools. A route may bridge funds, swap them, or do both before the treasury can use them.

For example, a treasury might hold a stablecoin on one chain and need it on another. One route can bridge that token directly. Another can swap it for a different asset, bridge that, then swap back. This explainer on how Biswap moves crypto across chains covers the swap mechanics behind routes like these. The useful comparison is the final balance, not the route’s first quoted amount.

What does net delivery mean for a crypto treasury?

Net delivery is the amount the treasury can use after the route’s costs are taken out. Start with the expected destination amount, then account for trading fees, bridge charges, network gas and price movement while the transaction runs.

Some costs are easy to miss. Gas may be needed on both the sending and receiving chains. A route that swaps through several pools can also lose value to slippage, the difference between the expected price and the price at execution. If a fee is taken in a token the treasury does not hold, acquiring that token adds another step.

How should teams compare cross-chain routes?

Compare routes using the same starting amount, destination asset and deadline. Then check the amount expected to arrive, the steps required, and what happens if one step fails. A route with a lower displayed fee may still deliver less if its swaps move the market price more.

• Net amount: Compare the destination balance after fees and estimated price impact.
• Execution time: Include bridge processing and the time needed for the destination chain to confirm the transfer.
• Failure handling: Check whether funds can be recovered or a route can be retried if a swap or transfer does not complete.
• Operational fit: Confirm the route meets the treasury’s asset, approval and record-keeping requirements.

These checks matter more for larger transfers. A route that works well for a small test may have limited pool depth at a larger size. Splitting a transfer can reduce price impact, but it can add transactions, gas and time. Teams should compare the full cost of splitting against one transfer.

When is the simplest route the better choice?

The simplest route is often better when two options deliver similar amounts. Fewer steps can mean fewer fees and fewer points where execution can stall. A more complex route can still make sense if it offers a clearly better net result and the treasury accepts its added dependencies.

Before moving a large balance, teams can check a fresh quote, confirm the destination token and network, and send a small test if the route is unfamiliar. The key is to compare expected delivery with the amount that actually arrives. Watch how quotes change with transfer size, and whether routes disclose all costs before execution.