Skip to the article
Token Trail

News from across crypto

How to Price a Cross-Chain Treasury Transfer

A treasury should price a cross-chain transfer by comparing the amount that leaves with the amount expected to arrive, including network, bridge, swap and timing costs.

By The Token Trail Desk3 min read

How to Price a Cross-Chain Treasury Transfer

Price a cross-chain treasury transfer by comparing the value sent with the value expected to arrive, then account for the fees and risks along the route. A transfer can involve two networks, a bridge and sometimes a token swap. The headline fee alone will not show the full cost.

Start with the amount the treasury needs on the destination chain. Then check how much of the source balance must leave to deliver it. A route may charge network fees in each chain’s native token, even when the treasury is moving a stablecoin. Some routes also build their charge into the exchange rate or the amount delivered. For a route between Ethereum and Solana, this RenBridge explainer on the stablecoin route gives more detail on the mechanics. The key pricing question is still what arrives, and when.

Which costs belong in the transfer price?

Count every cost that changes the treasury’s balance or its ability to use the funds. Network fees pay for transactions on the source and destination chains. A bridge or relayer fee pays the service that moves or advances the funds. A relayer is an operator that submits transactions across chains. A swap can add a trading fee and slippage, the difference between the quoted and executed price.

Record these costs separately where the quote allows it:

  • Source-chain transaction fee, including any fee to approve or deposit tokens.
  • Bridge, relayer or liquidity charge.
  • Destination-chain fee and any account setup cost.
  • Swap fee and expected price impact, if the route changes tokens.

Some routes quote one total deduction instead of breaking out each part. That can still be useful, but compare the amount delivered and the quote’s expiry time. Network fees can shift while the transfer is pending.

How should treasuries compare routes?

Compare routes on the same basis: same source amount, destination asset and required arrival time. Use the expected net amount received, converted to the treasury’s accounting currency, as the main comparison. Then add any costs the quote leaves out, such as gas paid separately from the wallet.

For example, a route with a lower stated fee may deliver less if its exchange rate is worse. A faster route may charge more because a provider advances liquidity before the source transfer settles. That price can make sense when funds are needed quickly; if timing is flexible, the cheaper route may be better. A route using RenBridge is one example to assess by its quoted output and timing, rather than its name or headline fee.

What should the treasury record?

Keep the quote, the amount sent, the amount received, the chain fees and the completion time with the transfer record. Note whether fees were paid in the transferred asset or in a separate token. This makes later reconciliation clearer and helps compare the next transfer with the same destination and urgency.

For most routine treasury moves, the better choice is the route with the strongest predictable net delivery, not simply the lowest advertised fee. Recheck the quote before signing, especially if it has expired or the amount has changed.