If your app exposes a manual destination claim, prompt users to redeem it promptly and treat 24 hours as the safe operational window—not a universal deadline after which funds vanish.

The window protects VAA verification, not the transfer itself

For a manual Wrapped Token Transfer (WTT), the 24-hour window is guidance tied to the Guardian Set that signed the transfer’s Verifiable Action Approval (VAA). The source contract emits a message, Guardians attest to it, and the resulting VAA carries the signing set’s index. The destination contract checks those signatures before it allows the claim.

Guardian Sets can rotate. A set remains valid for a period after replacement, but if the old set expires before the VAA is submitted, destination verification can reject it. Wormhole’s WTT guidance says manual transfers should be completed within 24 hours because Guardian Sets are guaranteed to remain valid for at least that long. The exact on-chain cutoff depends on the set’s expiration time; 24 hours is a safe operating window, not a timer embedded in every transfer.

That distinction matters in the interface: an unclaimed transfer does not automatically become a refund when this window passes. The source transaction has already happened. The pending destination claim may still be recoverable by updating its signatures, provided the transfer itself remains valid and unclaimed.

Track the source message and make recovery actionable

Keep the source transaction hash as the user’s recovery handle, and track the VAA’s emitter chain, emitter address, and sequence number. Together, these identify the message used to retrieve its attestation. Don’t treat “VAA not available yet” as an expired claim; wait for the source transaction to reach the required finality and for Guardians to produce the VAA.

For example, when a route shown among Portal Bridge supported chains needs a manual destination claim, your status view should distinguish source confirmation, VAA availability, and destination redemption. Tell users which chain needs gas for the claim transaction, and retain the source transaction hash so they can resume if they leave the flow.

If submission fails because the VAA’s Guardian Set has expired, follow Wormhole’s procedure for replacing outdated VAA signatures with signatures from the current set. The message body—and therefore the transfer details—stays the same; the signatures are refreshed. Have the user retry the destination claim with the updated VAA instead of sending the source transfer again, which could create a second transfer.

Check the failure before offering a retry

Before retrying, identify whether the VAA is missing, its signing set is expired, or the destination claim already succeeded. These states need different actions: keep waiting for an attestation that has not arrived, refresh signatures for an expired set, and stop once the destination transaction has consumed the claim.

A useful edge case is a claim transaction that succeeds on-chain while your app times out before receiving the response. Query the destination state or transaction receipt before presenting a retry button: Wormhole transfer contracts use replay protection, so a second redemption of an already completed message should fail rather than pay out twice. Show the destination transaction hash when available and reconcile the UI with chain state.

For manual WTT claims, build around a 24-hour operational target, expose the VAA and destination-claim stages separately, and preserve enough source-message data to recover an expired signature set. The window is about whether the destination can verify the VAA; it does not itself cancel an unclaimed transfer.