Corrections Policy
Our commitment to accuracy, prompt corrections, and historical integrity in our troubleshooting guides.
Our Commitment to Factual Accuracy
At the XMR Sync Wiki, we strive to ensure that every troubleshooting guide, remote node hostname, block height table, and security checklist is factually accurate, current, and clear. However, due to the rapid development of the Cake Wallet app client (released on the cake wallet github) and changes in the Monero (XMR) network block rates, details can sometimes go out of date.
We believe in full transparency and are committed to correcting any errors promptly. When an error is identified, we will update the content as soon as possible and, if significant, note the revision date at the bottom of the article.
How to Report an Error
If you find a factual inaccuracy, an offline node in our directory, a broken link, or a typographical error, please let us know. You can submit your correction through the following channel:
- Email: Send a message to
editor@cake-wallet.uswith the subject line "Correction Request". - Details: Please specify the page URL, the exact text containing the error, and the suggested correction with supporting references (such as official release notes on the Cake Wallet github or block explorer statistics) where applicable.
For details on communication privacy, please read our Privacy Policy. For secure channels, see our Contact Portal.
Verification Process
Once a correction request is received by our lead editor Daniel Reed:
- Our research desk will verify the report against live software builds of cake wallet ios and cake wallet android, or query the specific monero remote node.
- If the report is verified as an error, we will update the page immediately.
- For major factual errors (such as incorrect block restore height math that could lead to sync failures), we will add a short, dated update notice explaining the change.
Clarifications vs. Corrections
We distinguish between major factual errors and minor clarifications. A correction updates factual content (e.g. an incorrect port number). A clarification improves phrasing, structure, or terminology without changing the underlying fact. Clarifications are applied directly without revision history notes to maintain readability.