Canton Wallet Not Working — Troubleshooting Guide
Common Errors, Fixes, and Where to Get Help
Symptom: Wallet won't connect
Cause: network connectivity, Canton domain outage, or wallet's cached endpoint stale.
Fix: check internet, restart the wallet, switch Canton domain in wallet settings if available, retry. Most outages on Canton are single-domain and resolve within minutes.
Symptom: Transaction stuck pending
Cause: waiting for the current Canton reward round to close. Most transactions clear in sub-second once the round closes.
Fix: wait for the round to close (typically sub-hourly). If pending exceeds 30 minutes, the transaction is probably going to be rejected — check the wallet's transaction detail screen for the error code.
Symptom: Balance not updating
Cause: wallet's local cache out of sync with the ledger.
Fix: hard refresh the wallet (pull to refresh on mobile, full reload on web). Verify the source transaction confirmed in the sending wallet first. If still wrong after 10 minutes, contact wallet support.
Symptom: Passkey lost, no recovery phrase
Cause: self-custodial wallet without backup.
Fix: there is no fix. Self-custodial means no central reset. The takeaway: always back up the recovery phrase the moment you create a new wallet. See Canton Wallet Recovery for inheritance and multi-factor backup options.
Symptom: Transaction rejected
Cause: insufficient balance (forgot to account for holding fee), invalid destination address, or expired signature.
Fix: retry with the wallet's suggested fix from the error message. If the same operation keeps rejecting, contact wallet support with the transaction ID and timestamp.
When to contact wallet support
Contact support if: a transaction stays pending more than 30 minutes, balance is incorrect after multiple refreshes, the same error keeps repeating across retries, or anything looks suspicious (unfamiliar transactions, unexpected approval prompts).
Each wallet has its own support channel. Bron, C8, Zoro, 5N Loop, and Console all publish support contact details in their app help screens. Provide the transaction ID, timestamp, wallet version, and a clear description of the symptom.
FAQ
My Canton wallet won't connect to the network. What do I do?
Check your internet connection first. If the wallet shows 'Cannot reach Canton ledger' or similar, try restarting the wallet. If still failing, the wallet may be pinned to a specific Canton domain that's currently down — switch to a different domain in wallet settings if available, or wait and retry. Canton's Global Synchronizer has multiple domains; outages are rarely network-wide.
My transaction is stuck pending. How long should I wait?
Canton transactions usually confirm within sub-second once the round closes. Pending status persists during the round; once the round closes, status updates to confirmed or rejected. If a transaction stays pending for more than 5 minutes, check the round status in your wallet — there may be a temporary validator issue. Truly stuck transactions (over 30 minutes) usually mean signature mismatch, in which case the transaction will eventually be rejected, not silently lost.
Balance not updating after a deposit. Why?
First, check the transaction in the sending wallet — confirm it actually broadcast and confirmed. Second, force-refresh the receiving wallet (pull-to-refresh on mobile, hard reload on web). Third, verify you sent to the correct address. If all three pass and balance still doesn't update after 10 minutes, contact the wallet's support — there may be a sync issue with the wallet's local cache.
Lost my passkey and don't have a recovery phrase. Anything I can do?
Unfortunately, no. Self-custodial wallets without a backed-up recovery phrase are unrecoverable when the passkey is lost. This is the explicit security trade-off — no central authority can reset access. Going forward, every wallet you set up should have its recovery phrase written on paper and stored in a fireproof location. See Canton Wallet Recovery for more on inheritance and backup planning.
Wallet says 'transaction rejected' — what now?
Common causes: insufficient balance (account for the holding fee on top of the amount), expired signature (re-sign and broadcast), invalid party-id (check the destination address format), or temporary network issue (retry). The wallet usually surfaces the specific error code. If the error keeps repeating with the same operation, contact the wallet's support with the transaction ID and timestamp.