Contribute Bug Reports

If you discover a bug or other problem with Bitcoin Core, please report it. The are two different processes, responsible disclosure for security bugs and public issue tracking for all other bugs.

Please don’t open an issue to ask for support. See the Get Help page instead.

Responsible disclosure

bitcoin-security@lists.sourceforge.net

If you find a vulnerability related to Bitcoin, non-critical vulnerabilities can be emailed in English to any of the core developers or sent to the private bitcoin-security mailing list listed above. An example of a non-critical vulnerability would be an expensive-to-carry-out denial of service attack. Critical vulnerabilities that are too sensitive for unencrypted email should be sent to one or more of the core developers, encrypted with their PGP key(s).

Wladimir J. van der Laan
Gavin Andresen
Jeff Garzik
Gregory Maxwell
Pieter Wuille
Jonas Schnelli

Public Issue Tracking

For non-security problems with Bitcoin Core, please search for similar issues and, if you don’t find any, open a new issue providing the information listed below.

  1. A clear description of the problem. If possible, please describe how to reproduce the problem. (For general guidelines on writing steps to reproduce, see Mozilla’s bug reporting documentation.)

  2. What version of Bitcoin Core you use (if you downloaded from Bitcoin.org) or what commit you built using (git log -1) plus any extra patches you applied.

  3. Any relevant entries from your debug.log file. Note, this file can contain private information, so review it before posting or ask in the issue to email it directly to a developer rather than posting publicly. You can publicly post logs on a 0bin service. By default, the debug.log can be found at the following locations:

    • Windows: %APPDATA%\Bitcoin\debug.log

    • OS X: $HOME/Library/Application Support/Bitcoin/debug.log

    • Linux: $HOME/.bitcoin/debug.log

The best strategy to get your issue fixed quickly is to make it as easy as possible for the development team to track down the problem and write a fix. Providing more information and organizing it well helps significantly.