Do not share seed
The first rule is not technical. It is behavioral: do not send recovery words to a website, bot, helper, or “recovery specialist” because the wallet looks empty.
Quick answer
- Do not share seed while troubleshooting.
- Incomplete sync is common.
- Restore height may be too late.
- Wrong seed, wallet type, or node context can also explain the result.
Safe checklist
Confirm you restored inside verified wallet software.
Wait for sync completion.
Review restore height and approximate wallet creation date.
Check network/node status.
Prepare a non-sensitive help request only if needed.
Why this risky moment matters
Sync may be incomplete
Monero scanning can take time. A wallet may show incomplete or confusing information until the scan catches up. Let sync finish before assuming funds are gone.
Restore height may be too late
If scanning starts after old wallet activity, earlier transactions may not appear. Rescanning from an earlier date or height can be safer, though slower.
Wrong seed or wallet type
A different backup, copied word error, wrong wallet type, or old wallet context can also create mismatch. Check calmly without exposing the phrase to others.
Safe troubleshooting order
Verify source, check sync, check restore height, check network/node context, confirm the backup context, then seek official non-sensitive help if needed.
Red flags
A website asks for recovery words.A support account asks for private chat secrecy.A helper promises guaranteed recovery.A download page pressures you with urgency.
Safe / unsafe behavior
Safer behavior
Verify the source path before acting.
Stop immediately if...
Treat ads, copied links, and DMs as final proof.
Safer behavior
Keep recovery words inside trusted wallet software only.
Stop immediately if...
Paste a seed phrase into a website or support form.
Safer behavior
Share only non-sensitive app version, device type, sync status, and exact error wording.
Stop immediately if...
Share wallet files, screenshots of secrets, or remote-control access.
What to do now
- Is sync complete? If no, wait or fix connection.
- Was restore height later than wallet creation? Rescan earlier.
- Are you certain this seed belongs to the expected wallet? Check offline notes only.
- Did someone ask for seed during troubleshooting? Stop.
Action checklist
- Slow down before funds move.
- Write down the non-sensitive facts: device type, app version, sync status, source path, and exact error wording.
- Return through official public source paths instead of links from ads or private messages.
- If sensitive material was exposed, treat the wallet as compromised and work from a clean device.
What not to share
- seed phrase or recovery words
- private keys or spend keys
- wallet files
- screenshots that reveal balances, addresses, seeds, keys, QR codes, or error context
- remote-control access or screen-sharing during recovery
Source trail
Use the public Cake Wallet website as the first source path for product, download, documentation, and support routes.
Use public documentation to understand wallet behavior without exposing recovery material.
Use the Monero project site for protocol-level context and wallet terminology.
This site is maintained as people-first safety content with visible practical value.
How this guide is reviewed
XMRTrust wallet-safety reviewer
Reviewed for wallet-safety boundaries, non-affiliation disclosure, no-seed handling, realistic privacy language, source-path clarity, sponsored-link disclosure, and practical next steps. We do not provide financial advice, official support, wallet recovery services, or security/privacy guarantees.
Related guides
FAQ
Does empty mean funds are gone?
Not necessarily. Sync or restore height can explain it.
Should I ask support to check my seed?
No.
Can restore height be changed later?
Follow official app guidance for rescanning earlier.
Could a node issue cause confusion?
Network or node problems can affect sync visibility.
What can I share?
App version, device type, sync status, source path, and error wording.
What should I not share?
Seed, keys, wallet files, screenshots of secrets, and remote access.
Changelog
- 2026-06-24: Expanded with safety checks, source cards, internal links, and no-seed boundaries.