|2 days ago|
|.github||2 years ago|
|.tx||5 months ago|
|build-aux/m4||3 weeks ago|
|build_msvc||4 days ago|
|ci||2 weeks ago|
|contrib||2 days ago|
|depends||1 week ago|
|doc||2 weeks ago|
|share||2 months ago|
|src||2 days ago|
|test||3 days ago|
|.cirrus.yml||6 days ago|
|.editorconfig||10 months ago|
|.gitattributes||8 years ago|
|.gitignore||3 weeks ago|
|.python-version||2 years ago|
|.style.yapf||3 years ago|
|CONTRIBUTING.md||1 month ago|
|COPYING||6 months ago|
|INSTALL.md||10 months ago|
|Makefile.am||3 weeks ago|
|README.md||4 days ago|
|REVIEWERS||2 months ago|
|SECURITY.md||8 months ago|
|autogen.sh||3 years ago|
|configure.ac||1 week ago|
|libbitcoinconsensus.pc.in||3 years ago|
Bitcoin Core integration/staging tree
For an immediately usable, binary version of the Bitcoin Core software, see https://bitcoincore.org/en/download/.
What is Bitcoin Core?
Bitcoin Core connects to the Bitcoin peer-to-peer network to download and fully validate blocks and transactions. It also includes a wallet and graphical user interface, which can be optionally built.
Further information about Bitcoin Core is available in the doc folder.
master branch is regularly built (see
doc/build-*.md for instructions) and tested, but it is not guaranteed to be
completely stable. Tags are created
regularly from release branches to indicate new official, stable release versions of Bitcoin Core.
The https://github.com/bitcoin-core/gui repository is used exclusively for the development of the GUI. Its master branch is identical in all monotree repositories. Release branches and tags do not exist, so please do not fork that repository unless it is for development reasons.
Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.
Developers are strongly encouraged to write unit tests for new code, and to
submit new unit tests for old code. Unit tests can be compiled and run
(assuming they weren't disabled in configure) with:
make check. Further details on running
and extending unit tests can be found in /src/test/README.md.
The CI (Continuous Integration) systems make sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.
Manual Quality Assurance (QA) Testing
Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.
Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.
Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.
Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.