Bitcoin Core 31.1 validates the chain and keeps the wallet optional
Bitcoin Core v31.1 connects to Bitcoin's peer-to-peer network and independently checks blocks and transactions. The wallet and Qt interface are optional, so a server can run only bitcoind while a desktop user can choose the graphical application. That distinction matters: a full node is useful even when it holds no private keys. Applications can query the node through JSON-RPC instead of trusting a hosted chain API for their view of network state.
The repository's master branch is an integration and staging tree, not the version an operator should casually deploy. The README says it is regularly built and tested but not guaranteed completely stable. Official tags identify stable releases, and the v31.1 release page directs users to Bitcoin Core's own deterministic, signed downloads instead of GitHub assets. For production, the release channel and signature-verification process are part of setup, not optional ceremony.
The 804,553-line checkout is not a Python package
Our measured checkout had about 804,553 source lines across 3,061 files and occupied 51 MB before dependencies. Bitcoin Core is primarily C++, with CMake build files, a compiled unit-test suite, Python functional tests, fuzz targets, and platform-specific tooling. The repository also contains small Python environments for CI work. An automated project detector can land on one of those helpers, which is exactly what happened in our lab.
The official Unix build starts with CMake and requires a compiler, Python, and Boost. Optional components add separate dependencies: SQLite for wallets, Cap'n Proto for IPC, ZeroMQ for notifications, and Qt plus libqrencode for the GUI. The guide recommends at least 1.5 GB of memory for compilation and documents lower-memory compiler flags. A five-second Python package build says nothing about whether that C++ dependency set is present.
What happened when we ran it
Our sandbox installed the ci/lint Python environment in 18 seconds, adding 43 packages and occupying 105 MB. Its build step succeeded in 5 seconds. We used commit 4c9d55a in an unprivileged Python 3.12 Bookworm container with 3 CPUs, 8 GB of RAM, and no secrets. Those numbers describe the lint helper selected by the harness. They are not Bitcoin Core compilation or initial-sync timings.
Pytest then exited with code 5 after 6 seconds because it collected no tests. The log said no tests ran in 0.00s, giving 0 passed and 0 failed out of 0. Pip-audit reported 0 known vulnerabilities in the 43 installed Python packages. The checkout had one CI workflow, no Dockerfile, and a tests directory. None of those results executes the C++ unit tests or Python functional suite documented by Bitcoin Core.
Version 31.1 supports three named operating-system baselines
Bitcoin Core v31.1 is supported on Linux kernel 3.17 or newer, macOS 14 or newer, and Windows 10 version 1903 or newer. Other Unix-like systems may work but receive less testing. Prebuilt binaries are the shortest route for most operators. Source builders can omit the wallet, GUI, IPC, or other optional pieces, which cuts dependencies and narrows the process they must secure and maintain.
Running the node still means validating network data and choosing a resource policy. The memory guide sets the default UTXO cache to 1,024 MiB on larger systems and the default mempool limit to 300 MB. Lower settings save memory but can slow initial sync or evict unconfirmed transactions earlier. blocksonly reduces mempool use but changes relay and privacy behavior. These switches solve different constraints, so copying a low-memory configuration without understanding it is risky.
Two RPC endpoints can control the node and spend wallet funds
Bitcoin Core exposes 2 JSON-RPC endpoints: the root path and a wallet-specific path. The daemon enables RPC by default, while the GUI does not unless server mode is turned on. Local cookie authentication is the preferred default. Static credentials exist for programs that need them, and command whitelists can reduce access, but the guide warns that valid RPC users may control the node and filesystem resources available to its process.
Public RPC exposure is a hard stop. The interface has authentication but no transport encryption, and the project says it has not been hardened for arbitrary Internet traffic. A secure private network, SSH tunnel, VPN, or equivalent boundary is required for remote clients. Wallet operators face another layer: wallets are not encrypted by default, a forgotten encryption passphrase is unrecoverable, and backups need to be remade after encryption changes the wallet seed.
90,129 stars come with same-day review activity
GitHub reported 90,129 stars, 731 combined issues and pull requests, and a last push on September 9, 2026. The recently updated queue included consensus work, wallet write handling, peer selection, indexes, RPC behavior, tests, and platform build changes. That is current technical activity across the node rather than a popularity number standing alone. The large combined count reflects an unusually busy review pipeline and must not be read as 731 confirmed bugs.
Bitcoin Core 31.1 was released on July 8, 2026. Its notes include a fix for an IP-address leak where -privatebroadcast could connect over clearnet under some conditions, along with wallet, validation, network, build, and test changes. Operators should read those notes before upgrading and wait for clean shutdown, as the upgrade instructions say. The project earns trust through explicit release and security procedures, but running it safely still depends on the operator following them.