Bitcoin Core integration/staging tree https://bitcoincore.org/en/download
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
fanquake 8b67698420
Merge #17974: [0.18] net: Log to net category for exceptions in ProcessMessages
3 years ago
.github Get more info about GUI-related issue on Linux 4 years ago
.travis qa: Add test/fuzz/test_runner.py 4 years ago
.tx qt: Pre-0.18 split-off translations update 4 years ago
build-aux/m4 build: update boost macros to latest upstream 3 years ago
build_msvc qt: pre-rc1 translations update 3 years ago
contrib doc: Fix typos in COPYRIGHT 3 years ago
depends depends: add patch to common dependencies 3 years ago
doc build: Factor out qt translations from build system 3 years ago
share build: Stop translating PACKAGE_NAME 3 years ago
src net: Log to net category for exceptions in ProcessMessages 3 years ago
test Test that joinpsbts randomly shuffles the inputs 3 years ago
.appveyor.yml appveyor: Don't build debug libraries instead of "build and delete" 4 years ago
.gitattributes Separate protocol versioning from clientversion 8 years ago
.gitignore gitignore: add *.plist (clang-check) 3 years ago
.python-version .python-version: Bump to 3.5.6 3 years ago
.travis.yml travis: Bump timeout from 50 minutes to 90 3 years ago
CONTRIBUTING.md Botbot.me (IRC logs) not available anymore 4 years ago
COPYING [Trivial] Update license year range to 2019 4 years ago
INSTALL.md Update INSTALL landing redirection notice for build instructions. 6 years ago
Makefile.am Merge #15295: fuzz: Add test/fuzz/test_runner.py and run it in travis 4 years ago
README.md [doc] conf: Remove deprecated options from docs, Other cleanup 4 years ago
autogen.sh Add "export LC_ALL=C" to all shell scripts 4 years ago
configure.ac build: set CLIENT_VERSION_RC to 0 pre-final 3 years ago
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes 7 years ago

README.md

Bitcoin Core integration/staging tree

Build Status

https://bitcoincore.org

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 currency.

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.

License

Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

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

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.

Automated Testing

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.

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: test/functional/test_runner.py

The Travis CI system makes 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.

Translations

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.

Translators should also subscribe to the mailing list.