Swap treasury holdings into the destination chain’s native gas token before the transfer run. Size the purchase from expected transaction demand, fees, and a reserve policy, then verify the received token in the destination wallet.
Set the gas target from expected activity
Calculate the gas reserve from the transactions the wallet must execute, not from the value of the payouts. A wallet sending ERC-20 payouts on Ethereum needs ETH for transaction gas; a wallet receiving tokens but making no outbound transactions may need no immediate gas at all.
For an operating wallet, estimate gas units per transaction, multiply by the expected gas price, and add a buffer for congestion. For example, if a batch is expected to use 1.5 million gas at 30 gwei, budget 0.045 ETH before the buffer. Re-estimate when contract behavior, batch size, or network conditions change.
Set a minimum balance and a replenishment trigger. I would fund to cover the next run plus a defined reserve, rather than repeatedly swapping tiny amounts: each replenishment has source-chain gas, swap costs, and reconciliation overhead. The right reserve depends on how quickly the treasury can top up and how costly a missed payout window would be.
Choose holdings and a route that deliver native gas
Start with an asset the treasury can spend and a destination gas token the wallet can use. A token that tracks the gas asset, such as wrapped ETH, is not automatically interchangeable with native ETH for transaction fees; the wallet must receive the asset the chain’s execution environment accepts as gas.
A same-chain token conversion changes denomination on one network, while a thor swap aggregator can compare cross-chain routes that convert holdings on one network into a destination asset on another. The route may use different liquidity sources and settlement steps, so compare the estimated amount received, fees, slippage, and expected completion time—not just the displayed exchange rate.
For example, a treasury holds USDC on a supported source chain and needs ETH in its Ethereum payout wallet. Quote USDC to native ETH, enter the actual destination wallet address, and check that the quote identifies ETH on Ethereum as the output. If the available route returns wrapped ETH or a token on a different network, it does not meet the gas requirement without another transaction.
Run a controlled replenishment
Use this sequence for each replenishment, with the same wallet and approval controls as other treasury transactions.
- Confirm the trigger. Compare the destination wallet’s spendable native balance with the reserve threshold and the gas forecast for the next payout run.
- Select the source balance. Check its chain, token contract, and spendable amount; retain enough native source-chain gas to submit the swap.
- Request a fresh quote. Set the destination chain and native gas asset, enter the receiving wallet, and review expected output, route, source and destination fees, slippage, and quote expiry.
- Apply the execution limit. Set the minimum acceptable output or slippage tolerance supported by the route. A tight limit protects the treasury’s conversion rate but can cause execution to fail if the market moves before settlement.
- Approve and submit. Verify the token, amount, spender or transaction details, and destination address in the wallet signing prompt; then sign the source-chain transaction.
- Reconcile settlement. Track the inbound transaction and destination delivery separately. Record both transaction identifiers, actual received amount, fees, and the resulting gas balance before releasing the payout batch.
In this workflow, thor swap is relevant when treasury holdings and the required gas token sit on different chains; it is the routing interface in the funding step, not a substitute for verifying the destination asset or wallet controls. Quotes are estimates until settlement, and the source transaction can confirm before the destination transfer completes.
Handle route and settlement failures
A quote can become stale or fail if liquidity, gas estimates, or the route changes. Refresh it before signing if it expires or the expected output moves outside policy. If the transaction is submitted, monitor its status before retrying: a second swap can overfund the wallet if the first one is delayed rather than failed.
Check the destination chain’s token and address format before submission. A valid address on one EVM chain may be syntactically valid on another, yet still point to a wallet the business does not monitor. For non-EVM networks, use the required address format and any memo or tag the receiving wallet requires. If a route fails and refunds, the refunded amount may be reduced by network costs; reconcile the actual refund before calculating a replacement swap.
For recurring transfers, automate the balance check and alerting, but keep quote review, signing authority, and settlement reconciliation tied to treasury policy. Avoid setting the trigger so low that a single payout batch can consume the remaining gas before the next funding transaction settles.
Questions to settle before the next run
Can I swap directly into a chain’s gas token?
Only if the selected route supports that token as its output and delivers it on the intended chain. Inspect the quoted output asset and network explicitly. A token with a similar ticker, a wrapped version, or an asset on another network may have market value but still be unusable for the wallet’s gas fees.
How much destination gas should treasury keep?
Use a forecast based on expected transaction count, gas units, and a plausible gas-price range, then add a reserve for volatility and replenishment delay. Review it after changes to payout contracts or batching. A fixed token amount can become inadequate when gas prices rise or transaction volume grows.
What should I do if the source transaction confirms but gas has not arrived?
Track the swap using its transaction status and route details before submitting another. Cross-chain settlement can take longer than source-chain confirmation, and retrying too early risks duplicate funding. If the route reports failure, confirm the refund destination and amount, then obtain a fresh quote before replacing the funds.
Before signing, ask: will the wallet receive enough native gas on the correct chain, in time for the next transfer run?