A Gnosis bridge moves assets between Ethereum and Gnosis Chain through the native xDAI Bridge or OmniBridge route. The catch is simple: a confirmed source-chain transfer cannot be recalled. The sender can still stop or change an unconfirmed transaction, revoke an unused token approval, and investigate a delayed destination delivery without sending again.
Choose the exact asset that needs to arrive
The problem is that a familiar ticker is not enough. GNO, USDC, DAI, WETH, and xDAI can represent different contracts or different outcomes on Gnosis Chain. The cause is the bridge mechanism: it locks or burns the source asset and releases or mints the destination-side version.
Use the dedicated xDAI route when the goal is native xDAI for Gnosis gas. Use OmniBridge only when the receiving wallet or application accepts its bridged ERC-20 output. Bridging Ethereum DAI through OmniBridge does not create native xDAI; Ethereum USDC may arrive as USDC.e. Check the receiving application’s full token contract address, not its logo or ticker.
Verify the route before granting the approval
Before I sign, I make sure the page shows Ethereum as chain ID 1 and Gnosis Chain as chain ID 100, the chosen token and destination address are correct, and the wallet request matches the intended amount. For a live route screen that shows those choices and the available asset path, use gnosis bridge.
An ERC-20 approval is not the bridge transfer. If approval has been granted but the relay transaction has not been submitted, the allowance can be revoked or reduced later. A signature request that creates no transaction also changes nothing on-chain. Neither action recovers gas already spent on a completed approval transaction.
Stop only while the transaction is genuinely pending
| Stage | What can still change |
|---|---|
| Not submitted | Everything: token, sum, route, and recipient. |
| Pending in the wallet | A replacement or an attempt to cancel using the same nonce may work before confirmation; it is not guaranteed. |
| Reverted | The asset failed to bridge, but network gas may be spent. |
| Confirmed | The source transfer cannot be cancelled or reversed by the bridge interface. |
After confirmation, wait for the bridge message to be done. A short wait can come from network checks, validator work, caps, or a stopped route; it does not mean the original transaction should be sent again. Keep the source transaction hash and check its status on the bridge. If assets were moved to the wrong self-custody address or through the wrong asset route, there is usually no way to undo it—only steps to get them back available to whoever controls that destination address.