Send cross-chain deposits with expiry time in hand

To time a cross-chain deposit before expiry, check the route’s closing time, then send early enough for the source-chain transaction to be seen and confirmed. A deposit address can stop accepting new transfers even while a transaction is waiting in a wallet or mempool, the queue of unconfirmed transactions. Expiry rules differ by service, so use the time or block height shown for that specific deposit.

When should I send a cross-chain deposit?

Send once the route details are final and you have enough time left for the source chain to process the transaction. Don’t treat the address’s expiry as a target send time: a wallet may broadcast quickly, but the network still needs to include the transaction in a block, and the swap service may require further confirmations.

Check the source chain’s recent pace, especially if it is busy. A fast chain can still slow down, and a fee set too low may leave a transaction waiting. The fuller chainflip article explains how the deposit step fits into a native cross-chain swap flow. Keep the deposit amount, source asset and destination address beside you while reviewing the route; correcting those details after sending may be difficult or impossible.

What does a deposit expiry actually mean?

Expiry marks the end of the period in which a service expects a deposit for that route. Some services show a clock time, while others show a block height, the number assigned to a block on the source chain. A block-height deadline moves with that chain’s block production, so it is not always possible to convert it into an exact wall-clock time.

Expiry does not mean the swap itself has a countdown that can be extended. The route may be tied to a particular deposit address and set of instructions. A transfer sent after the channel closes may not be recognised automatically, even if the address still looks usable. Follow the service’s stated rule for whether a transaction must be broadcast, included in a block or confirmed before the deadline.

How much time should I leave for confirmation?

Work backwards from the displayed deadline and leave a buffer for both inclusion and the required confirmations. The right buffer depends on the source chain, current congestion and the service’s confirmation policy; there is no safe number of minutes that fits every deposit.

• Read the expiry in the route details before opening your wallet.
• Check the source chain and asset match the instructions exactly.
• Use a fee likely to get the transaction included in time.
• Leave room for the service to observe the required confirmations.

If there is too little time to leave that buffer, open a fresh route if the service allows it and use its new instructions. Don’t send to an old address just because it remains visible in your history.

What should I do after sending?

Save the transaction ID and watch its status on the source chain and in the swap service. A wallet’s “sent” message means it broadcast the transaction; it does not prove the service has received or accepted the deposit. If the transaction is still pending near expiry, avoid sending a second deposit unless the service tells you what to do. Two transfers can create two separate cases to resolve.

The practical rule is simple: prepare first, then send with time to spare. If the deadline is close or unclear, a new route is usually easier to track than trying to race an expiring one.