In a Monad bridge transfer on a route that requires manual claiming, a claim is the destination-chain transaction that completes delivery after the cross-chain message becomes eligible. A confirmed source transaction shows that the transfer began on the sending chain. It does not, by itself, show that the recipient can use the asset on Monad. Some routes handle destination execution automatically; a claim instruction matters only when the selected route says someone must submit that transaction.
What does the claim transaction do?
The claim supplies the destination execution that a manual route leaves to a user or another permitted caller. A cross-chain bridge to Monad carries information about a transfer between chains, but a message that can be acted on is different from an executed delivery. When the claim transaction runs, the destination contract applies the route’s rules to the eligible message, records that it has been claimed, and delivers the destination asset to the designated recipient.
That record matters because the same transfer must not be delivered twice. The exact delivery method depends on the route: it may release an asset held for transfers or issue a destination representation. For a first-time user, the practical distinction is simpler. Before execution, the route may know what the recipient is owed; after successful execution and credit, the recipient has the destination asset.
When is a transfer ready to claim?
A transfer is ready to claim when the route has made its cross-chain message eligible for destination execution. A Monad bridge route may wait for the source transaction to meet its confirmation requirement and for the message or its proof to become available. The next stage relies on that information: the destination contract needs enough verified transfer data to identify the asset, amount, recipient, and claim under the route’s rules.
-
Source confirmed: The sending-chain transaction has reached the route’s required confirmation state. This establishes the source-side action, not destination delivery.
-
Claim ready: The route reports that its message can be submitted for destination execution. The recipient may still have no transferable destination tokens.
-
Destination credited: The destination transaction has executed and the designated recipient has received the asset. This is the state to look for when deciding whether delivery finished.
Read the status against the selected route’s instructions. “Ready” is useful only if it refers to the correct transfer and destination chain; a source transaction hash alone cannot establish that a destination claim is available. If the route exposes a message identifier or claim action, match it to the transfer before submitting anything.
Who submits the claim, and who pays?
The route’s rules decide who may submit a claim and how destination execution is paid for. A manual route may allow the recipient, the sender, or another caller to execute the eligible message. If the user submits a destination transaction, that wallet generally needs the destination chain’s native token for gas. If a route uses an executor or relayer, its fee arrangement may cover that transaction instead. The claim instruction should identify the required caller and payment method.
Consider two transfers with the same source chain, destination, asset, amount, recipient, and eligible message. The decisive difference between Monad bridge routes is whether destination execution is automatic or manual. On an automatic cross-chain bridge to Monad, an executor submits the destination transaction under that route’s process. On a manual route, an authorised caller must submit the claim. Both transfers can reach message readiness, but only the second asks the user to take a claim step; neither is complete merely because a ready label appears.
How can you tell the transfer is complete?
Completion is established by the documented destination transaction and the recipient’s asset credit. Find the destination transaction associated with the transfer, confirm it succeeded under the route’s instructions, and verify the asset reached the designated address. A claim-ready status describes permission to attempt execution. Even a submitted claim is only pending until the destination chain records its result.
If a claim instruction arrives through an unsolicited message, use the selected route’s own transfer details to locate the required action. A request for a recovery phrase has no role in claiming. For future transfers, keep the source transaction, message identifier if provided, and destination transaction together. That short record makes it easier to tell which stage you have reached without mistaking source confirmation for spendable funds.