What Happens to Your Tokens if a Bridge Pauses Mid-Transfer?

10 October 2026

If a bridge pauses while your transfer is in progress, your tokens remain on the source chain in a locked or burned state - they are not lost, but you cannot access them on the destination chain until the bridge resumes. The exact outcome depends on whether the pause happens before or after the bridge’s validators or relayers have processed your transaction.

When the pause occurs

Bridges pause for several reasons: a suspected hack, a detected bug, a validator quorum failure, or a planned upgrade. The timing of the pause relative to your transfer determines what you can do.

Pause before source chain confirmation

If the bridge pauses before your transaction is confirmed on the source chain (meaning it’s still pending in the mempool or not yet included in a block), the transfer never starts. Your tokens never leave your wallet. The pause simply prevents the transaction from being mined. You can resubmit once the bridge resumes, or cancel the pending transaction if needed.

Pause after source chain confirmation but before destination mint

This is the scenario that worries most users. Your tokens have been locked in the bridge contract (or burned, depending on the model) on the source chain. The bridge has seen this transaction and may have queued it for relayers or validators. If the pause interrupts processing at this stage:

• Lock-and-mint bridges: Your tokens are locked in the source contract. They are not lost - the contract holds them. You cannot withdraw them until the bridge unpauses and completes the mint on the destination, or until the bridge team provides a manual recovery mechanism.
• Burn-and-mint bridges: Your tokens are burned on the source chain. They are permanently destroyed there. Recovery depends entirely on the bridge’s ability to mint equivalent tokens on the destination chain after unpausing.

In either case, the bridge’s internal state (a ledger or message queue) records that your transfer is pending. When the pause ends, relayers or validators will process the backlog. Your tokens should arrive on the destination chain, possibly with some delay.

Pause during a message-passing bridge

Message-passing bridges (like LayerZero or Wormhole) work differently. They send a message from the source chain to a destination chain. If the pause occurs after the message is sent but before it’s delivered:

• The message is stuck in the bridge’s relayer network or validator quorum. It will be delivered once the network resumes normal operation, assuming the message is still valid (some messages have timeouts).
• If the pause is caused by a security incident, the bridge team may invalidate certain messages. This is rare but happens during exploits.

Can you get your tokens back manually?

Generally, no. You cannot force a bridge to release your tokens. The source chain contract is designed to only unlock tokens when the destination chain confirms receipt - or when the bridge governance decides to reverse a transaction.

Some bridges offer a manual recovery or emergency withdrawal function, but these are controlled by the bridge’s multi-sig or governance. They are only used in extreme cases, such as a permanent bridge shutdown. If the pause is temporary, the standard process resumes.

What to Do While a Bridge Is Paused

1. Check the bridge’s official status page or social media. Most bridges announce pauses and provide estimated resolution times. Look for a “Status” or “Incidents” section on their website.
2. Do not resubmit the same transaction. Resubmitting will not speed things up and may cause confusion. The original transaction is still pending.
3. Do not interact with any “recovery” links or DMs. Scammers target paused bridges. Recovery is handled through official channels only.
4. Monitor your source chain wallet. If the bridge unpauses and your transfer completes, you will see the mint on the destination chain. You may also see a reversal if the bridge team decides to cancel the transfer (rare).
5. Wait at least 24 - 48 hours before contacting support. Many pauses resolve within hours. If the pause lasts longer, use the bridge’s official support channels - never third-party helpers.

How long can a pause last?

There is no standard. Some bridges pause for minutes during a routine upgrade. Others pause for days during a security investigation. In extreme cases, a bridge may pause permanently if the team decides to shut down. This is uncommon, but it has happened.

If a bridge pauses permanently, your tokens are stuck unless the team provides a withdrawal mechanism. In a lock-and-mint bridge, the source contract still holds the locked tokens. The team can deploy a function to allow users to withdraw back to the source chain. In a burn-and-mint bridge, recovery is more complex and may require minting new tokens on the source chain - something most bridges cannot do by design.

The Bottom Line

A bridge pause is not a loss of funds, but it is a loss of access until the bridge resumes. Your tokens are safe in the bridge contract or burned state. The risk is that the pause may be long, or the bridge may never resume. This is why you should only use bridges with a track record of transparent incident response, clear governance, and a non-custodial recovery plan.

Before bridging, ask yourself: Can you afford to have those tokens inaccessible for a day? A week? A month? If the answer is no, consider using a centralized exchange withdrawal or a more conservative bridge with shorter finality.

Back to bridges