Corrections Policy
We strive for absolute precision in our guides. When errors occur, we correct them swiftly and transparently. Read our guidelines below to see how we handle updates and corrections.
1. Our Commitment to Accuracy
Monero wallet restore heights, node ports, and fee structures change as the software evolves. We check our technical guidelines against official releases. If we make a technical error or print outdated instructions, we correction-patch it as soon as it is flagged and verified.
2. How to Report an Error
If you find an error, typo, or outdated information on our website, please email us:
📧 Email: research@example.com
Please include the following in your email:
- The URL of the page containing the error.
- The specific sentence or instruction that is incorrect.
- The corrected information or block height, along with a link to official documentation (e.g., GitHub issue or release notes) if applicable.
3. Correction Log (Sample Updates)
Below is a log of updates we have made to ensure our educational resources remain accurate:
| Date | Page affected | Correction made |
|---|---|---|
| May 20, 2026 | /monero-seed-phrase/ | Clarified that seed phrases on modern Cake Wallet installs are 25-word mnemonics, while polyseed setups utilize 16 words. Added descriptions for both. |
| April 12, 2026 | /glossary/ | Updated definitions for stealth addresses to include reference to private view keys and view-only wallets. |
Review Cycle
In addition to user reports, we review all pages in our core clusters every six months to ensure links to official repositories are functioning correctly.