github
/
bitcoin
mirror of https://github.com/bitcoin/bitcoin
1
Fork 0
Code Releases Activity
35,574 Commits 5 Branches 309 Tags 4.8 GiB
C++ 64.2%
Python 20%
C 11.7%
M4 1.2%
Shell 1%
Other 1.8%
Go to file
fanquake d3a3522560
Merge bitcoin/bitcoin#28668: [24.2] Final Changes 
b01a5bea7d doc: update release notes for 24.2 (fanquake)
1343f43518 doc: update manual pages for 24.2 (fanquake)
db244c6342 build: bump version to 24.2 final (fanquake)

Pull request description:

  Final changes for v24.2.
  PR for bitcoincore.org is here: https://github.com/bitcoin-core/bitcoincore.org/pull/993.

  24.2rc1 tag: https://github.com/bitcoin/bitcoin/releases/tag/v24.2rc1
  rc1 bins available for ~1 week: https://bitcoincore.org/bin/bitcoin-core-24.2/test.rc1/.

ACKs for top commit:
  josibake:
    ACK b01a5bea7d
  stickies-v:
    ACK b01a5bea7d

Tree-SHA512: 339466ace2d3401a690e1bbd7f7636a9905f379870a06a38151a745d0df4f1c9a532acecd38cade608e417343c6ac20563e42eae5fbd42128cb81802e3212340
 		2023-10-23 10:26:40 +01:00
.github doc: Remove label from good first issue template 2020-08-24 09:31:24 +02:00
.tx Adjust `.tx/config` for new Transifex CLI 2022-10-28 17:49:27 +08:00
build-aux/m4 build: sync ax_boost_base from upstream 2022-09-04 10:10:16 +01:00
build_msvc fs: work around u8path deprecated-declaration warnings with libc++ 2022-08-19 08:58:56 +01:00
ci ci: Use podman stop over podman kill 2023-09-26 16:26:55 +01:00
contrib contrib: Fix capture_output in getcoins.py 2022-10-11 09:19:58 +08:00
depends depends: fix unusable memory_resource in macos qt build 2023-10-03 15:57:10 +01:00
doc doc: update release notes for 24.2 2023-10-17 16:49:43 +01:00
share doc: Generate example bitcoin conf for 24.0rc2 2022-10-14 10:28:34 +08:00
src tx fees, policy: read stale fee estimates with a regtest-only option 2023-09-26 16:26:55 +01:00
test test: ensure old fee_estimate.dat not read on restart and flushed 2023-09-26 16:26:55 +01:00
.cirrus.yml ci: Switch to `amd64` container in "ARM" task 2023-10-02 16:49:14 +01:00
.editorconfig ci: Drop AppVeyor CI integration 2021-09-07 06:12:53 +03:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore refactor: cleanups post unsubtree'ing univalue 2022-06-15 12:56:44 +01:00
.python-version Bump minimum python version to 3.6 2020-11-09 17:53:47 +10:00
.style.yapf test: .style.yapf: Set column_limit=160 2019-03-04 18:28:13 -05:00
CONTRIBUTING.md doc: Explain squashing with merge commits 2022-05-24 08:17:41 +02:00
COPYING doc: Update license year range to 2022 2022-01-03 04:48:41 +08:00
INSTALL.md doc: Added hyperlink for doc/build 2021-09-09 19:53:12 +05:30
Makefile.am build: package test_bitcoin in Windows installer 2022-08-09 09:13:23 +01:00
README.md doc: Explain Bitcoin Core in README.md 2022-05-10 07:49:09 +02:00
REVIEWERS doc: empty REVIEWERS file 2022-07-30 09:05:07 +01:00
SECURITY.md doc: Add my key to SECURITY.md 2022-08-23 16:57:46 -04:00
autogen.sh scripted-diff: Bump copyright of files changed in 2019 2019-12-30 10:42:20 +13:00
configure.ac build: bump version to 24.2 final 2023-10-17 16:46:36 +01:00
libbitcoinconsensus.pc.in build: remove libcrypto as internal dependency in libbitcoinconsensus.pc 2019-11-19 15:03:44 +01:00

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.