joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-27 01:36:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
dash-docs/en/bitcoin-core/contribute/issues.md
David A. Harding 706c791e92
New Bitcoin Core subsite 
This commit contains a large number of contributions from Saïvann
Carignan.
2015-09-14 06:02:58 -04:00

2.5 KiB
Executable file
Raw Blame History

layout id columns lang title breadcrumbs
base-core bitcoin-core-contribute-issues 1 en Issues - Contribute to Bitcoin Core
bitcoin
bcc
bcc contribute
Issues

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][bcc help] page instead.

{% translate disclosure development %}

bitcoin-security@lists.sourceforge.net

{% translate disclosuretxt development %}

{% include bitcoin-core/core-committers.html %}

Public Issue Tracking

For non-security problems with Bitcoin Core, please [search for similar issues][bcc issues] and, if you don't find any, [open a new issue][bcc 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][0bin]. 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.


**Previous**
[Contribute overview][bcc contribute] **Next**
[Code][bcc contribute code]

{% include references.md %}