Monad bridge cancellation: pending versus included
Can you cancel a Monad bridge transfer after signing? Only while its source transaction is pending; after inclusion, plan for delivery or a route-specific refund.
The Finality Desk4 min read#b5bec6

Monad bridge transfers can be cancelled only while the source transaction is pending; after it is included in a block, it cannot be cancelled. The answer changes at inclusion: before it, the transaction may be replaceable; after it, the nonce is consumed and the bridge message has been emitted.
- Signed, not submitted: nothing has moved; decide whether to submit the transaction.
- Pending on Ethereum: replace it with a same-nonce transaction carrying a higher fee.
- Included: track attestation and destination delivery, or check whether the route provides a refund for a failure.
Signing creates an authorized transaction; it does not itself transfer tokens or create a bridge message. The source chain must include the deposit transaction for the transfer to begin. For an integration using Monad bridge, the Monad bridge link identifies the cross-chain transfer whose cancellation state your code must expose.
Can you cancel a Monad bridge transfer after signing?
Yes, but only before the source transaction is included, and only by replacing the pending transaction under the same account nonce. A replacement is a new transaction that competes for inclusion; it is not a bridge-level undo command.
On Ethereum, transactions from one account are ordered by nonce. A pending deposit uses its nonce, so a replacement must use that same nonce and offer a higher fee to take its place. For a standard Ethereum externally owned account, a common cancellation attempt is a 0-ETH self-send with the same nonce and a higher fee. If that replacement is included first, the deposit is not included under that nonce.
The distinction matters because signing and inclusion are separate states. A signed transaction may still be local or waiting in the mempool. A submitted transaction may also remain pending while the chain has not included it. In either case, the replacement works only while the original is still eligible to be replaced. Fee requirements and replacement handling depend on the chain and the node or service receiving the transaction.
Once the deposit is included, its nonce has been used. A second transaction with that nonce cannot undo the first transaction’s effects. The inclusion emitted the bridge message, so the transfer has moved beyond the source transaction’s pending state.
What happens after the source transaction is included?
After inclusion, a bridge transfer proceeds through message emission, attestation, and destination delivery. The source transaction is the event that starts this sequence; it is not an escrowed operation that the sender can later revoke with another transaction.
For a Wormhole route, Guardians observe the source-chain message and sign a VAA once 13 of the 19 Guardians agree. Once signed, that VAA cannot be revoked. The destination can use the attestation to deliver the tokens. Axelar is another name developers may encounter when comparing cross-chain verification paths, but the cancellation decision still turns on whether the source transaction was included.
That is why “stuck” can describe different states. A pending source transaction has not started the bridge message flow and may still be replaceable. An included transaction has started it; a delay in attestation or delivery does not make the source transaction cancellable. If a destination action fails, the outcome depends on the route’s refund behavior. Do not promise users that an included transfer can be reversed or that a refund is automatic.
Track each transfer by its source transaction hash and expose distinct states: pending, included, attested, and delivered. A source transaction that reverts never emitted the bridge message, so mark that outcome separately from an included transfer waiting for destination delivery. The observable difference is the source-chain receipt: pending has no inclusion; included has a block receipt and a bridge message. Treating those states as equivalent could offer a cancellation control after it can no longer work.
Related
What happens to a Monad bridge transfer that is stuck?
A stuck transfer needs a state check before any action. If its source transaction is still pending, a same-nonce replacement may cancel it. If it is included, follow the message through attestation and delivery; do not submit a cancellation transaction for an already consumed nonce.
Does a failed Monad bridge transfer get refunded?
A refund is not guaranteed by source inclusion alone. If the source transaction reverted, no bridge message was emitted. If it was included but destination delivery failed, only the route’s refund mechanism determines whether the assets return. Show users the observed state and the route-specific outcome rather than labeling every delay a failed transfer.
For cancellation handling, let users replace only a still-pending source transaction; after inclusion, show the transfer’s progress toward delivery or its route-specific refund outcome.