How Much Crypto Should You Send Across Chains?

Send the amount you need on the destination chain, plus enough to cover the route’s costs and any next transaction; there is no universal safe percentage. To work it out, start with the asset and amount you want to receive, then check what the route will deduct before the funds arrive.

What happens when crypto moves across chains?

A cross-chain swap usually has four moving parts. First, your wallet sends the source asset in a transaction on its original chain. You pay that chain’s network fee, whether or not the swap succeeds. The receiving network or protocol waits for the deposit to be confirmed, then processes the swap. Finally, it sends the destination asset to the address you specified, and that outgoing transaction has a cost too.

Some routes exchange one asset for another through liquidity pools; others move a representation of the same asset through a bridge. Those are different operations. In a pool swap, the trade changes the pool’s asset balance, so a larger trade relative to available liquidity can shift the price and reduce your output. THORChain, for example, can route a swap between two assets through RUNE internally. The user makes one deposit and receives the other asset. The linked thor swap explainer walks through that route in more detail.

Think of the quoted output like a price estimate at a shop: it tells you what the purchase may cost under current conditions, but the final amount depends on what happens before the trade completes. A quote can include estimated network fees and price impact, but it may change with pool depth, network congestion or the time taken to confirm the deposit.

How do I calculate how much to send?

Work backward from what you need to have available after the transfer. Check the quoted destination amount, subtract any fees or deductions shown, and leave a small usable balance for the next step. For example, if you need tokens to use in a contract, the tokens alone may not be enough: you may also need the destination chain’s native asset to pay transaction fees.

Before sending, check these four details in the route’s confirmation screen:

• Estimated receive amount: Compare it with the minimum amount the route says you will receive.
• Network fees: Account for the source-chain fee and any destination fee deducted from the output.
• Price impact or slippage: A larger trade against shallow liquidity can produce less than the displayed estimate.
• Address and asset: Confirm the destination address and that it accepts the exact asset and network you selected.

If the amount is large relative to the pool or your available balance, compare the quoted output for a smaller amount. Splitting a trade may reduce price impact on some routes, but each separate deposit can add another source-chain fee. Some protocols offer a streamed swap that divides one deposit into smaller trades over time; check whether the route supports it and how it affects timing and fees.

Should I send a test amount first?

Send a small test when you are unsure that the address, asset and route are correct, or when a failed transfer would be costly. The test confirms that the destination can receive the asset, but it does not guarantee that a later transfer will get the same quote or arrive at the same speed. You may also pay network fees for both transfers.

For a familiar route and a verified destination, a test can cost more than it tells you. The practical choice is to test when it meaningfully reduces the risk of a wrong address or unsupported asset, then size the main transfer from the current quote and your actual destination need. Keep enough on the source chain to pay the deposit fee, and avoid sending your entire balance if you will need funds for another transaction.