Bitcoin Core integration/staging tree
|Architecture:||Intel & AppleSilicon(ARM)|
|Minimum OS:||macOS 10.15.0|
|Vendor Name:||Bitcoin Foundation|
Version History 23.0
You can find release notes for this version here: [bitcoincore.org]
BITCOIN CORE INTEGRATION/STAGING TREE
What is Bitcoin?
Bitcoin is an experimental digital currency that enables instant
payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer
technology to operate with no central authority: managing transactions
and issuing money are carried out collectively by the network. Bitcoin
Core is the name of open source software which enables the use of this
For more information, as well as an immediately useable, binary version
of the Bitcoin Core software, see https://bitcoincore.org/en/download/,
or read the original whitepaper.
Bitcoin Core is released under the terms of the MIT license. See COPYING
for more information or see https://opensource.org/licenses/MIT.
The master branch is regularly built and tested, but is not guaranteed
to be completely stable. Tags are created regularly to indicate new
official, stable release versions of Bitcoin Core.
The contribution workflow is described in CONTRIBUTING.md and useful
hints for developers can be found in doc/developer-notes.md.
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
There are also regression and integration tests, written in Python, that
are run automatically on the build server. These tests can be run (if
the test dependencies are installed) with:
The Travis CI system makes sure that every pull request is built for
Windows, Linux, and macOS, and that unit/sanity tests are run
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
IMPORTANT: We do not accept translation changes as GitHub pull requests
because the next pull from Transifex would automatically overwrite them
Translators should also subscribe to the mailing list.