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.
 
 
 
 
 
 
MacroFake 53b1a2426c
Merge bitcoin/bitcoin#25471: rpc: Disallow gettxoutsetinfo queries for a specific block with `use_index=false`
2 days ago
.github doc: Remove label from good first issue template 2 years ago
.tx qt: Update transifex resource blob to 23.0 5 months ago
build-aux/m4 Squashed 'src/secp256k1/' changes from 8746600ee..44c2452fd 3 weeks ago
build_msvc build: Clean up `build_msvc/libsecp256k1_config.h` 4 days ago
ci ci: Improve naming related to "macOS 12 native x86_64" task 2 weeks ago
contrib Merge bitcoin/bitcoin#25508: guix: use elfesteem 2eb1e5384ff7a220fd1afacd4a0170acff54fe56 2 days ago
depends build: suppress array-bounds errors in libxkbcommon 1 week ago
doc Merge bitcoin/bitcoin#25414: doc: Update Arch Linux build example 2 weeks ago
share doc: replace bitcoin.conf with placeholder file 2 months ago
src Merge bitcoin/bitcoin#25471: rpc: Disallow gettxoutsetinfo queries for a specific block with `use_index=false` 2 days ago
test Merge bitcoin/bitcoin#25364: test: remove wallet dependency from feature_nulldummy.py 3 days ago
.cirrus.yml Revert "ci: Increase CPU number for "Win64 native" task" 6 days ago
.editorconfig ci: Drop AppVeyor CI integration 10 months ago
.gitattributes Separate protocol versioning from clientversion 8 years ago
.gitignore refactor: cleanups post unsubtree'ing univalue 3 weeks ago
.python-version Bump minimum python version to 3.6 2 years ago
.style.yapf test: .style.yapf: Set column_limit=160 3 years ago
CONTRIBUTING.md doc: Explain squashing with merge commits 1 month ago
COPYING doc: Update license year range to 2022 6 months ago
INSTALL.md doc: Added hyperlink for doc/build 10 months ago
Makefile.am refactor: cleanups post unsubtree'ing univalue 3 weeks ago
README.md Squashed 'src/minisketch/' changes from 7eeb778fef..47f0a2d26f 4 days ago
REVIEWERS test: port 'lint-shell.sh' to python 2 months ago
SECURITY.md doc: Suggest `keys.openpgp.org` as keyserver in SECURITY.md 8 months ago
autogen.sh scripted-diff: Bump copyright of files changed in 2019 3 years ago
configure.ac build: use BOOST_NO_CXX98_FUNCTION_BASE to suppress warnings 1 week ago
libbitcoinconsensus.pc.in build: remove libcrypto as internal dependency in libbitcoinconsensus.pc 3 years 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/.

What is Bitcoin Core?

Bitcoin Core connects to the Bitcoin peer-to-peer network to download and fully validate blocks and transactions. It also includes a wallet and graphical user interface, which can be optionally built.

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

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.