Recipient address
Confirm the address from a trusted channel and watch for last-minute replacement.
Quick answer
- Verify address carefully.
- Use a small test when appropriate.
- Watch clipboard malware risk.
- Do not invite support DMs during the send.
Safe checklist
Compare recipient address through a trusted channel.
Paste then re-check beginning and end.
Consider a small test.
Confirm device and sync state.
Why this risky moment matters
Small test transaction
A small test can reveal process errors before meaningful funds move.
Clipboard malware
Malware can replace copied addresses; always re-check after paste.
Network and sync context
Understand current app sync and fee context before sending.
Screenshots and support
Do not post transaction screenshots or accept private support during a high-stress send.
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
- Did anyone ask for recovery words? Stop and leave the flow.
- Are you inside verified wallet software? If not, verify the source path first.
- Is the issue a sync or restore-height question? Check sync status before seeking help.
- Do you need support? Use non-sensitive details only.
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
Should I send a test first?
For meaningful amounts, a small test can reduce process risk.
Can clipboard malware change addresses?
Yes.
Should I screenshot the send screen?
Avoid screenshots that reveal balances or addresses.
What if support DMs me mid-transaction?
Stop and verify independently.
Can transactions be reversed?
Do not assume reversibility.
What should I record?
Non-sensitive process notes, not seeds or private keys.
Changelog
- 2026-06-24: Expanded with safety checks, source cards, internal links, and no-seed boundaries.