How do you report a reproducible Monero software bug?
Identifying and reporting software bugs is essential for the ongoing security and reliability of the Monero ecosystem.
Quick Answer
For general functional bugs, open an issue on the official Monero GitHub repository with detailed environment information and steps to reproduce. If you discover a security-sensitive vulnerability, follow the project's Vulnerability Response Process to report findings privately. Never disclose security-sensitive bugs publicly, as this could facilitate exploitation before a patch is developed.
Standard Bug Reporting
If you discover a functional bug, the standard procedure is to create a report on GitHub. A high-quality report includes environment details, error logs, and a step-by-step guide to reproduce the behavior consistently. This allows maintainers to verify the bug and develop a targeted fix.
Security-Sensitive Issues
Issues that could compromise security should never be posted publicly. Instead, follow the project's Vulnerability Response Process. The project maintains a presence on HackerOne, providing a private channel for researchers to report sensitive findings responsibly.
Sources
Related reading
Key takeaways
- Use GitHub issues for reporting non-security bugs.
- Follow the Vulnerability Response Process for security flaws.
- Include clear, reproducible steps in every bug report.
