Bitcoin Core

Bitcoin Core is the reference implementation of the Bitcoin protocol. It's the direct descendant of the client Satoshi released under the name "Bitcoin", renamed in 2014 to reduce confusion between Bitcoin-the-network and Bitcoin-the-software. It runs on about five of every six publicly reachable full nodes (October 2026), with most of the rest on Bitcoin Knots, and is what most other wallets and libraries quietly defer to.

The codebase lives at github.com/bitcoin/bitcoin, maintained by a rotating cast of contributors with no formal governance structure. Changes go through:

1. A BIP and extensive mailing-list discussion for anything that changes consensus rules.
2. A pull request to the codebase, reviewed by anyone who wants to (and many serious reviewers do).
3. Integration by maintainers - a small group with merge access. They don't set the rules; they merge what passes review.
4. A release, cut by the maintainers, who also run the release cycle.
5. Adoption is voluntary. Every node operator chooses whether to upgrade. A consensus change takes hold only when enough operators run the new version that the network has effectively migrated.

The combination of open review and voluntary adoption is what makes Bitcoin's protocol genuinely hard to change. A hostile maintainer can't sneak in a change; reviewers will spot it. A hostile group can't fork the rules; nodes won't run their version. The system optimizes for not making mistakes, even at the cost of slow evolution.

Bitcoin Core aims for a major release every six months, each with incremental improvements to mempool policy, networking, and validation performance. Consensus changes ship first in maintenance releases rather than major versions: SegWit's mainnet parameters came in 0.13.1 and Taproot's activation parameters in 0.21.1. It's the de facto standard for "what Bitcoin actually is."

The codebase has its quirks too. The GUI's "Mask Values" toggle, which hides balances and amounts from anyone looking over your shoulder, was merged in 2020; during review someone compared it to Wasabi Wallet's version of the same idea, known as Lurking Wife Mode - a small reminder that real humans write this software.

See Full Node for what running it means, and Sovereignty Journey for why you might want to.

For why changes near validation are treated so conservatively, see The 2013 Chain Fork, the night a database swap turned out to be a consensus change.