Keep Gas at the Destination Before You Move Treasury Funds

0 destination-native tokens is enough to leave an EVM treasury unable to send its tokens onward, even when its token balance is intact. That zero measures the wallet’s balance of the chain’s native coin, which pays for transaction execution. A transfer is not operationally complete until the recipient can act on the funds.

Why does a destination chain need its own gas reserve?

Each chain accounts for transaction fees in its own native asset. On an EVM chain, sending an ERC-20 token, granting an allowance or calling a contract generally requires the sender to pay gas in that chain’s native coin. ETH on one network does not pay fees on another just because both networks use EVM-compatible software.

A bridge can deliver tokens to a destination address without delivering the coin needed to spend them. The recipient may then hold assets but be unable to move them, approve a contract or interact with a treasury workflow. If you are weighing bridge routes, this guide to when a native-asset bridge is the right route covers the route choice in more detail.

Keep the fee categories separate when comparing routes. A swap fee or bridge fee is charged for a service; destination gas pays for a later transaction on the receiving chain. If your route research includes Biswap, the same distinction applies: a venue or route label does not tell you whether the receiving wallet has gas.

How much gas should a treasury send?

There is no fixed reserve that fits every transfer. Gas use depends on the destination chain, the action you need to perform and the current fee conditions. A plain token transfer usually consumes less gas than a contract interaction, while a sequence of approvals and calls needs more than one transaction.

Start with the first action the recipient must take, not just the arrival transaction. Estimate its gas using the relevant wallet or transaction tooling, then set aside enough native coin for that action and a reasonable buffer for fee changes or a retry. A buffer should reflect the treasury’s actual workflow; an idle holding that is too large ties up funds without making the process safer.

• List the first required actions: transfer, approval, contract call or withdrawal.
• Estimate gas for those actions on the destination chain.
• Check the destination wallet’s native-coin balance before the transfer.
• Recheck after arrival and top up if the planned workflow needs more.

How can you make the reserve part of treasury operations?

Treat gas as a required operating balance for each destination chain, rather than as an incidental leftover. A treasury policy can set a minimum balance, assign who can replenish it and specify which address holds the reserve. Keep that balance distinct in records from tokens held for investment or payment.

Before sending, confirm the destination network and address, the token contract, and whether the recipient is a wallet or a contract with its own execution rules. For recurring transfers, test the full path with a small amount and check that the destination can complete the intended action. The practical rule is simple: fund the asset transfer and the next transaction the asset requires.