Reference
Incidents
Things that went wrong, what users saw, why it happened and what the app does differently now.
Each entry says what users saw, the cause as far as we know it, and what changed in the app. Live status of the bridge and our services is on Status.
11 Nov 2026 — delayed bridge withdrawal
| What users saw | A withdrawal through the wxmr.io bridge showed a Monero transaction hash, but that hash wasn't on the Monero network. The XMR arrived about 35 minutes later under a different transaction hash. |
| Cause | The bridge relayer recorded the withdrawal as completed on Solana (with a hash and tx key) before the Monero transaction was actually on the network; the payment that finally went out had a different hash. The relayer is run by the wxmr.io team, not by us. |
| Funds | No funds were lost — the full amount arrived. |
What the app does differently now
- It no longer trusts the bridge's "completed" record alone: the hash is checked against several public Monero nodes, and a withdrawal counts as done only at 10 confirmations.
- If the hash isn't on the network 15 minutes later, the withdrawal is marked not on the network yet, with the hash, the tx key and a ready-made report for the bridge team — and a reminder to check your Monero wallet first, because the payment can still arrive under a different hash.
- Bridge health counts such withdrawals across all users; while it's degraded the bridge is no longer the default withdrawal route and the operator gets an alert.
- A background check resolves old withdrawals that were delivered after all, so a stale "waiting" banner doesn't stay on screen.