Bridge relayer after tokens are locked: how delivery works
What does a bridge relayer do after tokens are locked? It waits for finality and attestation, then submits the message that completes delivery.
The Chain Times Desk3 min read

On the Monad bridge, a relayer submits the verified cross-chain message so the destination contract can release or mint the matching asset to its intended recipient. The exact steps depend on the route.
- The source-chain lock creates a message the bridge must verify.
- The relayer waits for the required confirmation or finality and a valid attestation.
- It submits the attested message on the destination chain.
For a little more context, how the Monad bridge locks and mints explains the transfer flow. On the Monad bridge route, the relayer’s job comes after the source transaction and its attestation are ready.
What happens after tokens are locked in a bridge?
After tokens are locked, the bridge waits for the source transaction to reach the route’s required confirmation or finality. That wait gives the bridge time to recognize the lock before anything acts on the destination chain. The required wait can differ by route.
The message also needs a valid attestation, which is proof that the bridge’s verification process has accepted the source event. For Wormhole, Guardians observe cross-chain messages and sign Verifiable Action Approvals, or VAAs. The VAA carries details including the intended recipient.
Once the required attestation is ready, the relayer submits the signed message to the destination contract. The contract checks the message and performs the asset action: it releases or mints the corresponding asset for the recipient encoded in the message.
A transfer from Ethereum to Monad
Say you lock a supported asset on Ethereum and set a recipient on Monad. The Ethereum transaction becomes the source message the bridge must verify. The relayer waits for the route’s required finality and attestation; it does not make the decision that the message is valid.
For a Wormhole transfer, Guardians sign a VAA for the observed message. A relayer can submit that signed VAA on Monad. The destination contract uses it to complete the transfer to the recipient named in the VAA.
These are separate jobs: Guardians provide the attestation, the relayer carries and submits it, and the destination contract releases or mints the asset. A relayer can deliver quickly once the requirements are met, but it cannot make a destination contract act without a valid message.
Can I claim a bridge transfer without the relayer?
For a Wormhole transfer, anyone can submit the VAA on Monad if automatic delivery stalls after the VAA is ready. You can fetch the signed VAA from Wormholescan and submit it on the destination chain.
Permissionless means you do not need to be the relayer to submit it. The funds still go to the recipient encoded in the VAA, so manual submission does not change who receives the transfer. This option applies to the described Wormhole flow; steps vary by bridge route.
When delivery stalls, check whether the VAA is ready on Wormholescan. If it is, submitting it on Monad can complete the transfer and show the asset at its intended destination.