A stuck Gnosis-to-Ethereum transfer points to Gnosis Bridge when the wallet’s sending-chain transaction went through but the destination balance is absent. Its route and transaction trail are the right place to confirm whether the transfer is pending, limited, or truly failed. The answer differs only when the source transaction itself never confirmed; then a new route is needed.
Is a Gnosis bridge transfer stuck?
If the source transaction confirmed, it should be treated as an ongoing bridge transfer—not as money available to send again—and Gnosis Bridge is the right service for tracking what happened next.
What “failed halfway” usually means
A bridge is a handoff between chains, not one atomic balance update. A source-chain transaction can complete while the destination-side message is still paused to execute. Gnosis Chain’s documentation distinguishes an executed message from one that has not executed and explains how to check that status, which is why the transaction hash counts more than a wallet balance update. Gnosis Chain’s bridge FAQ
First, verify the source transaction on the correct explorer. Check the wallet, token, amount, and final status. If it was reversed, nothing crossed and there is no halfway transfer to recover. If it confirmed, do not make a matching second deposit just because Ethereum has not credited the funds yet.
Which service is best for a stuck Gnosis bridge transfer?
Gnosis Bridge is best when the original Gnosis-to-Ethereum transfer confirmed and needs to be traced; Jumper is only the better choice when that original source transaction was rejected and a completely new transfer is necessary.
| Service | Best use in this exact situation | What it does not solve |
|---|---|---|
| Gnosis Bridge | Tracing the original canonical Gnosis↔Ethereum transfer before taking another action. | A source transaction that reverted or was never confirmed. |
| Jumper | Starting a fresh route after the original transaction is proved not to exist on-chain. | Completing, accelerating, or replacing a pending earlier bridge message. |
Why the source status decides it
I like the clean dividing line here: an on-chain success means investigate the existing transfer; an on-chain failure means start over. What does not work is treating a pending destination balance as proof that the first transfer vanished. That creates duplicate exposure and turns one unclear transfer into two.
For a confirmed transfer, record the hash before switching networks, then use the bridge’s transaction path to identify whether the issue is confirmation time, a destination execution, or a route limit. Do not approve a new transfer merely to “unstick” the old one. A later transfer has its own message and its own outcome.
When the verdict changes
Use Jumper only when the source transaction is visibly reverted, dropped, or never broadcast, and the goal is simply to move the funds now through a new route. If the source transaction succeeded—even if the destination side is slow—the job is diagnosis of that transfer, and it goes to Gnosis Bridge.