Date versus block height
A date is a human estimate; a block height is a specific chain position. Both aim to start scanning before wallet activity.
Quick answer
- Date is user-friendly approximation.
- Block height is a chain position.
- Earlier is safer but slower.
Safe checklist
Use approximate wallet creation date if exact height is unknown.
Choose earlier when unsure.
Never reveal seed for this guidance.
Why this risky moment matters
When to use approximate date
Use it when you know when the wallet was created but not the exact block.
Why earlier is safer
Earlier scanning is slower but reduces the chance of missing older activity.
Why later can miss history
Starting after wallet activity can make funds invisible until a rescan.
No seed needed
A helper can explain date versus height without seeing recovery words.
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
Which is better?
The safer choice depends on what you know; earlier is often safer when uncertain.
Is a date exact?
No, it is an approximation.
Can later miss funds?
It can miss older activity.
Does this expose privacy?
Approximate dates reveal less than wallet secrets but still share only what is needed.
Do I need my seed?
No.
Can I rescan?
Follow official wallet guidance for rescanning.
Changelog
- 2026-06-24: Expanded with safety checks, source cards, internal links, and no-seed boundaries.