Skip to content

/ bitcoin

Bitcoin Core integration/staging tree
bitcoin c-plus-plus p2p cryptocurrency cryptography
C++ Python C M4 Shell Makefile Other
  1. C++ 69.2%
  2. Python 17.3%
  3. C 7.2%
  4. M4 1.9%
  5. Shell 1.4%
  6. Makefile 1.0%
  7. Other 2.0%
Branch: master
Find file
Clone or download

Clone with HTTPS

Use Git or checkout with SVN using the web URL.

Open in Desktop Download ZIP

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio

If nothing happens, download the GitHub extension for Visual Studio and try again.

Latest commit

@MarcoFalke
MarcoFalke Merge #18571: fuzz: Disable debug log file 
fa69f88 fuzz: Disable debug log file (MarcoFalke)
fa0cbd4 test: Add optional extra_args to testing setup (MarcoFalke)
fad4fa7 node: Add args alias for gArgs global (MarcoFalke)

Pull request description:

  There are several issues with writing to a debug log file when fuzzing:

  * Disk access is slow, but fuzzing should be fast (Note: I could not verify this claim with data)
  * Disks have a limited size and will eventually run out of space, but fuzzing should run continuous

  Fix both issues by disabling the debug log file for fuzz tests

ACKs for top commit:
  practicalswift:
    ACK fa69f88 -- patch looks correct

Tree-SHA512: f61beb6c94a9ab664deb191685fcad601e228b77bb1c43db6ec40616ae393c9dd35c51474f1b0759ac0bc29b5ca8456a329906a3695bd0f18fa4372210c8b54a
Latest commit 5447097 Apr 15, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Remove GitHub Actions CI workflow. Jan 30, 2020
.tx tx: Bump transifex slug to 020x Mar 16, 2020
build-aux/m4 build: Update ax_boost_mase.m4 to the latest serial Apr 8, 2020
build_msvc Merge #18504: build: Drop bitcoin-tx and bitcoin-wallet dependencies … Apr 10, 2020
ci ci: Print ccache statistics summary Apr 10, 2020
contrib Merge #18619: gitian: add jonatack gpg key fingerprint Apr 15, 2020
depends Revert "Merge #16367: Multiprocess build support" Apr 10, 2020
doc Merge #18645: [doc] Update thread information in developer docs Apr 15, 2020
share guix: Make x86_64-w64-mingw32 builds reproducible Apr 2, 2020
src fuzz: Disable debug log file Apr 15, 2020
test Merge #18628: test: Add various low-level p2p tests Apr 15, 2020
.appveyor.yml Merge #18640: appveyor: Remove clcache Apr 15, 2020
.cirrus.yml appveyor: Disable functional tests for now Apr 14, 2020
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore Revert "Merge #16367: Multiprocess build support" Apr 10, 2020
.python-version .python-version: Specify full version 3.5.6 Mar 2, 2019
.style.yapf test: .style.yapf: Set column_limit=160 Mar 4, 2019
.travis.yml ci: Add pip cache Apr 10, 2020
CONTRIBUTING.md Merge #18283: doc: Explain rebase policy in CONTRIBUTING.md Mar 11, 2020
COPYING doc: Update license year range to 2020 Dec 26, 2019
INSTALL.md Update INSTALL landing redirection notice for build instructions. Oct 5, 2016
Makefile.am Merge #18107: build: Add cov_fuzz target Mar 27, 2020
README.md doc: Fix some misspellings Nov 4, 2019
SECURITY.md doc: Remove explicit mention of version from SECURITY.md Jun 14, 2019
autogen.sh scripted-diff: Bump copyright of files changed in 2019 Dec 29, 2019
configure.ac Revert "Merge #16367: Multiprocess build support" Apr 10, 2020
libbitcoinconsensus.pc.in build: remove libcrypto as internal dependency in libbitcoinconsensus.pc Nov 19, 2019

README.md

Bitcoin Core integration/staging tree

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 usable, 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.

You can’t perform that action at this time.