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.
 
 
 
 
 
 
Go to file
Jon Atack e21212f01b
wallet: remove unneeded WALLET_BTC_KB_TO_SAT_B constant
4 years ago
.github doc: Remove label from good first issue template 4 years ago
.tx tx: Update transifex slug for 0.21 4 years ago
build-aux/m4 Squashed 'src/secp256k1/' changes from c6b6b8f1bb..3967d96bf1 4 years ago
build_msvc Merge #19953: Implement BIP 340-342 validation (Schnorr/taproot/tapscript) 4 years ago
ci Merge #20292: test: Fix intermittent feature_taproot issue 4 years ago
contrib Merge #20318: build: Ensure source tarball has leading directory name 4 years ago
depends Merge #20195: build: fix mutex detection when building bdb on macOS 4 years ago
doc doc: fix getchaintxstats fields in release-process.md 4 years ago
share
src wallet: remove unneeded WALLET_BTC_KB_TO_SAT_B constant 4 years ago
test wallet: fix bug in RPC send options 4 years ago
.appveyor.yml Bump vcpkg commit ID to get new msys mirror list 4 years ago
.cirrus.yml ci: Remove redundant valgrind fuzz task 4 years ago
.fuzzbuzz.yml
.gitattributes
.gitignore .gitignore: ignore qa-assets/ folder 4 years ago
.python-version
.style.yapf
.travis.yml ci: Run windows ci config on cirrus 4 years ago
CODEOWNERS doc: Add comments and additional reviewers to CODEOWNERS file 4 years ago
CONTRIBUTING.md
COPYING
INSTALL.md
Makefile.am build: use DIR_FUZZ_SEED_CORPUS if specified for cov_fuzz target 4 years ago
README.md Squashed 'src/secp256k1/' changes from c6b6b8f1bb..3967d96bf1 4 years ago
SECURITY.md
autogen.sh
configure.ac Squashed 'src/secp256k1/' changes from c6b6b8f1bb..3967d96bf1 4 years ago
libbitcoinconsensus.pc.in

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