mirrors/bitcoin
Watch
1
0
Fork
You've already forked bitcoin
 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2026-09-11 09:11:46 +00:00
Code Issues Projects Releases Packages Wiki Activity
Bitcoin Core integration/staging tree https://bitcoincore.org/en/download
50,535 commits 5 branches 366 tags 2.5 GiB
  • C++ 62.8%
  • Python 18.7%
  • C 15%
  • CMake 1.1%
  • Shell 0.9%
  • Other 1.2%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
merge-script 1a4e034ddb
 Merge bitcoin/bitcoin#36209: guix: cache GUI depends separately 
1fe87c2505 guix: cache GUI depends separately (will)

Pull request description:

  Alternative to #35929

  The GUI and non-GUI Guix profiles produce different depends build IDs. However, depends deletes the existing per-package cache directory when storing a new build. Sharing a cache root therefore causes each profile to evict the other's packages, forcing rebuilds on subsequent runs.

  This PR keeps these packages in separate `GUIX/BUILD` and `GUIX/GUI` directories under the cache root. This also keeps them separate from ordinary developer builds when BASE_CACHE is being used there.

  #35929 replaces `GUIX_ENVIRONMENT` in package ID generation with a hash of selected Guix inputs. Its current implementation covers the manifests, patches, pinned Guix revision and additional flags, but that list needs to stay aligned with how we construct the environment and may therefore be brittle to future changes.

  In this version I prefer keeping the resolved environment in the cache key and simply keeping the caches separate.

  #### Tradeoffs vs #35929

  This PR means building and storing some dependencies twice, which I consider a reasonable cost for simpler cache tracking/invalidation. This is likely going to be the case for Linux anyway i.e after a change like #36193 or #25573.

ACKs for top commit:
  achow101:
    ACK 1fe87c2505
  hebasto:
    ACK 1fe87c2505, tested on Ubuntu 26.04 by doing several consecutive Guix builds interleaved with branch switches and observing the cache behavior.
  sedited:
    ACK 1fe87c2505

Tree-SHA512: 33d8926fd8cc81338dd2d2c389a0ae9388256da5b1fdebabf05308f057535d1240d6e8bc0fc30a11a80cd3677c39067b0a5c3cc87272d162d8dbe727d8e1cc7c
2026-09-11 10:19:02 +02:00
.github test: get_previous_releases.py use PREVIOUS_RELEASES_DIR 2026-09-09 10:16:16 -07:00
.tx translation: Switch to Qt TS source file 2026-03-16 12:20:58 +00:00
ci Merge bitcoin/bitcoin#36195: test: get_previous_releases.py use PREVIOUS_RELEASES_DIR 2026-09-10 11:33:10 +01:00
cmake build: avoid pipe2 on Darwin (for now) 2026-09-10 12:22:30 +01:00
contrib guix: cache GUI depends separately 2026-09-10 11:44:54 +01:00
depends Merge bitcoin/bitcoin#35796: depends: fix IPC listeners on macOS dying when accepting a dead socket 2026-09-09 09:42:18 +01:00
doc doc: Correct upstream-pull reference 2026-09-10 06:02:48 +09:00
share Merge bitcoin/bitcoin#34808: cmake, translation: Use native Qt TS file as source for translations on Transifex 2026-07-23 14:55:30 +02:00
src Merge bitcoin/bitcoin#36150: indexes: set prune lock to genesis before first block 2026-09-11 09:59:12 +02:00
test Merge bitcoin/bitcoin#36150: indexes: set prune lock to genesis before first block 2026-09-11 09:59:12 +02:00
.editorconfig doc: remove reference to cirrus 2026-05-29 08:59:43 +01:00
.gitattributes cmake: Skip using git when building from source tarball or as subproject 2026-05-14 13:32:27 +01:00
.gitignore iwyu: Add patch to prefer angled brackets over quotes for includes 2025-12-17 20:28:42 +00:00
.python-version Don't pin Python patch version 2026-04-29 21:50:13 +01:00
.style.yapf Update .style.yapf 2023-06-01 23:35:10 +05:30
CMakeLists.txt build: Remove cmake/script/CoverageFuzz.cmake 2026-09-03 15:40:34 +01:00
CMakePresets.json build: Bump VS minimum supported version to 18.3 2026-02-10 23:30:23 +00:00
CONTRIBUTING.md doc: clarify test placement guidance 2026-07-22 08:36:39 -07:00
COPYING doc: update copyright year 2025-12-29 17:50:43 +00:00
CTestConfig.cmake cmake: Set CTEST_NIGHTLY_START_TIME for CDash Nightly pipelines 2026-05-08 11:09:06 +02:00
INSTALL.md lint: Check for missing trailing newline 2025-05-13 15:50:02 +02:00
libbitcoinkernel.pc.in kernel: create monolithic kernel static library 2025-07-28 10:37:42 +01:00
README.md doc: fix transifex 404s 2025-06-19 11:22:14 +01:00
ruff.toml lint: remove E731 Ruff ignore 2026-07-16 10:29:58 +01:00
SECURITY.md Remove myself as security contact 2026-07-09 16:44:50 -04:00
vcpkg.json build, msvc: Disable default features of the sqlite3 package 2026-08-10 23:26:01 +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/license/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 during the generation of the build system) with: ctest. 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: build/test/functional/test_runner.py (assuming build is your build directory).

The CI (Continuous Integration) systems make sure that every pull request is tested on Windows, Linux, and macOS. The CI must pass on all commits before merge to avoid unrelated CI failures on new pull requests.

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.