Bitcoin Core integration/staging tree
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.
 
 
 
 
 
 
MarcoFalke 9313c4e6aa
Merge bitcoin/bitcoin#21874: fuzz: Add WRITE_ALL_FUZZ_TARGETS_AND_ABORT
12 hours ago
.github doc: Remove label from good first issue template 8 months ago
.tx qt: Bump transifex slug for 22.x 2 weeks ago
build-aux/m4 build: Use XLIFF file to provide more context to Transifex translators 2 weeks ago
build_msvc Merge bitcoin/bitcoin#21817: refactor: Replace &foo[0] with foo.data() 2 days ago
ci ci: Properly pass msan cflags 2 days ago
contrib Merge bitcoin/bitcoin#21740: test: add new python linter to check file names and permissions 2 days ago
depends Merge bitcoin/bitcoin#21427: depends: Fix id_string invocations 2 days ago
doc Merge bitcoin/bitcoin#21856: doc: add OSS-Fuzz section to fuzzing.md doc 2 days ago
share Merge bitcoin/bitcoin#21709: doc: update reduce-memory.md and bitcoin.conf -maxconnections info 2 days ago
src fuzz: Add WRITE_ALL_FUZZ_TARGETS_AND_ABORT 17 hours ago
test Merge bitcoin/bitcoin#21873: test: minor fixes & improvements for files linter test 18 hours ago
.appveyor.yml Update msvc build to use Qt5.12.10 binaries. 2 weeks ago
.cirrus.yml ci: Clarify that previous_releases task is using DEBUG 6 days ago
.editorconfig Add EditorConfig file. 2 months ago
.fuzzbuzz.yml ci: remove boost thread installation 3 months ago
.gitattributes Separate protocol versioning from clientversion 6 years ago
.gitignore Ignore guix builds 4 weeks ago
.python-version Bump minimum python version to 3.6 5 months ago
.style.yapf test: .style.yapf: Set column_limit=160 2 years ago
CONTRIBUTING.md doc: Clarify that squashing should happen before review 2 months ago
COPYING doc: Update license year range to 2021 4 months ago
INSTALL.md Update INSTALL landing redirection notice for build instructions. 4 years ago
Makefile.am build: Remove spaces from variable-printing rules 1 month ago
README.md doc: Rework internal and external links 2 months ago
REVIEWERS script: update REVIEWERS 4 days ago
SECURITY.md doc: Remove explicit mention of version from SECURITY.md 1 year ago
autogen.sh scripted-diff: Bump copyright of files changed in 2019 1 year ago
configure.ac Merge bitcoin/bitcoin#21629: build: fix configuring when building depends with NO_BDB=1 2 days ago
libbitcoinconsensus.pc.in build: remove libcrypto as internal dependency in libbitcoinconsensus.pc 1 year ago

README.md

Bitcoin Core integration/staging tree

https://bitcoincore.org

For an immediately usable, binary version of the Bitcoin Core software, see https://bitcoincore.org/en/download/.

Further information about Bitcoin Core is available in the doc folder.

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 read the original Bitcoin 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 (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.

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. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

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.

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.