Skip to the article
Token Trail

News from across crypto

How to move treasury funds across chains with biswap

A treasury move starts with the destination, asset and amount; bridge mechanics, swap choices and checks shape what arrives and what the team can do next.

By The Token Trail Desk3 min read

How to move treasury funds across chains with biswap

To move treasury funds across chains with biswap, choose a destination network, send an asset across, then confirm the balance where the team plans to use it. A treasury is the pool of funds an organisation manages for operations, reserves or payments. The move may also involve a swap, which changes one token into another. When a team needs that cross-chain step, biswap is a bridge and swap service that lets users move and swap crypto across blockchains in one flow. The service describes support for Bitcoin, Ethereum, BSC, Solana and major layer 2 networks, which are chains built to handle activity alongside a main blockchain.

How does biswap move treasury funds?

A cross-chain transfer has two sides: the source chain, where funds start, and the destination chain, where they need to arrive. A bridge coordinates the move. Depending on its design, it may lock or burn an asset on the source chain and release or create a corresponding asset on the destination, or use funds held in pools to pay the recipient there. A swap can happen as part of the flow if the treasury wants a different asset on arrival.

For example, a team holding one token on Ethereum might need a different token on a layer 2 network to pay a contractor. It should set the destination and final asset first, then work out how much value it needs to arrive. The received amount can differ from the starting amount because of the swap rate and transaction costs on the networks involved. A bridge moves value between chains; it does not make the assets or their uses identical.

What should a treasury decide before a biswap transfer?

Write down the purpose of the transfer before sending funds. That helps the team choose the destination chain and asset based on where the money will be used, rather than moving funds first and solving the next step later. Record who approved the move and how the team will check that it arrived.

  • Destination: Confirm the chain the recipient or treasury wallet is set to use.
  • Asset: Check whether the destination needs the same token or a different one.
  • Amount: Set the amount to arrive, allowing for the swap and network costs.
  • Receipt: Confirm the balance on the destination chain before treating the funds as available.

What risks matter when moving treasury funds across chains?

The main trade-off is that a cross-chain move depends on more than one network and on the bridge design. A delayed transaction may leave funds unavailable for a time. A contract flaw or a problem with a bridge’s liquidity can affect whether and when the destination receives the expected value. The team should understand those dependencies before moving a large share of its reserves.

For routine operations, move only what the destination task needs and keep a record of the source asset, destination asset and amount received. For a large transfer, a small initial move can confirm that the destination wallet and process work before the treasury sends the rest. The practical rule is simple: choose the destination and required asset first, then verify receipt on that chain before spending or counting the funds.