If maintenance starts in 24 hours, for example, move your asset while the source chain still accepts transactions, then confirm it arrived on the destination chain. The right move depends on what the notice actually pauses: a website or wallet interface may be unavailable while the network keeps running, but a chain halt or paused withdrawals can prevent transfers.
What should you check in the maintenance notice?
Find the affected chain, the start time and the services that will stop. Check whether the notice names deposits, withdrawals, block production or only a particular app. If it is unclear whether on-chain transfers will work, ask the app or exchange that issued the notice before sending funds.
Choose a destination where you can use the asset during the maintenance window. A token on one chain and a token with the same ticker on another may be different assets; confirm the destination network and token contract against the receiving app’s instructions. If your task is to move value across chains and change assets in one transaction, a thor swap service is relevant when its available route matches your source asset, destination asset and networks.
How do you move the asset in one flow?
Suppose you hold an ERC-20 token on a chain whose withdrawals will pause tomorrow, and need ETH on another chain for an app. A cross-chain swap route can observe the incoming transfer, exchange through available liquidity and send the output to a wallet address on the destination chain. You authorize the source transaction from your wallet; the conversion and destination transfer are separate on-chain activity handled along the route. A single request does not mean one atomic transaction across both chains.
Here is the shortest useful sequence:
- Confirm the deadline. Read the maintenance notice and check the source chain’s current status. Leave time for source confirmations and destination processing; neither has a fixed universal duration.
- Pick the exact output. Match the destination chain and asset to the app’s deposit requirements. Check that the receiving address belongs to a wallet that can access that network.
- Keep gas aside. Leave enough of the source chain’s native coin to pay for the transfer. The swap amount also needs to cover network costs and any price impact; sending the entire balance can leave too little for gas.
- Review the quote and submit. Compare the estimated output with the minimum you would accept. Slippage is the difference between an expected and actual execution price; a volatile asset or thin liquidity can change the result before execution.
- Verify arrival. Check the source transaction and destination transaction on their respective explorers, then confirm the receiving app credits the correct asset. Keep the transaction IDs until the app shows the funds.
What can go wrong if you leave it late?
The key edge case is a transfer already in progress when maintenance begins. The source transaction may confirm, but the route’s destination transaction could still be waiting; if the relevant chain pauses observation, trading or outbound transfers, completion can be delayed. Starting early gives you time to check the status and resolve a pending transfer before the receiving app also closes deposits.
Costs vary by route and network conditions. Allow for source gas, the quoted exchange rate or price impact, and destination-chain costs; compare the final estimated output with simply holding the asset if you do not need to change chains. I would move only the amount needed for the app, then keep a separate gas balance and leave the remainder untouched until the maintenance status is clear.
What is the next step?
Start with the maintenance notice, not the swap quote: identify what stops and when. If on-chain withdrawals remain available, decide the exact asset and network the destination app accepts, then check whether a thor swap route can take your source asset there. Submit with time to spare and treat the destination explorer confirmation, followed by the app’s own credit, as the finish line.