Bitcoin Core

The project is the same codebase Satoshi published in January 2009, renamed from Bitcoin-Qt to Bitcoin Core with version 0.9.0 on March 19, 2014, and released under the MIT license ever since. It is free, it has no company behind it, and its maintainers can publish code but cannot make a single person install it. Almost everything you touch when you buy bitcoin, from an exchange's withdrawal system to your wallet's fee estimate, is built on top of it.

How it works

Bitcoin Core is four programs in one download.

There is the validating engine, which does the work described under any definition of a node: connecting to peers, checking every rule, keeping the unspent output set. There is a graphical application and a headless daemon that wrap it. There is a wallet, optional and off to one side, which since version 30.0 must be a descriptor wallet, the older Berkeley DB format having been removed. And there is an interface of remote procedure calls that everything else in the ecosystem talks to, which is why an exchange's back end and a hardware wallet's desktop app both end up speaking the same dialect.

Its odd constitutional position is worth understanding. Bitcoin has no consensus specification separate from working code. There is a pile of improvement proposals, and there are alternative implementations, but when a rule is ambiguous the answer in practice is whatever Bitcoin Core does, including its accidents. The March 2013 chain split happened because a storage library's undocumented limit had quietly been a consensus rule for years, and nobody found out until the software changed.

Releases arrive roughly twice a year, and the numbering lost its leading zero at version 22.0 in 2021. Version 30.0 shipped on October 13, 2025. Merges require review from other contributors, and nobody in the project can push a change to your machine.

Keep policy and consensus apart, because the loudest arguments are always about the first. Consensus rules decide which blocks are valid and are shared by every node on the network. Policy rules decide what an individual node relays and keeps in its mempool, and you can change yours in a configuration file this afternoon without leaving the network.

Why this matters when you buy bitcoin

Bitcoin Core's defaults set the floor under every transaction you will ever make.

Whether your withdrawal propagates at all depends on the minimum relay fee, and version 30.0 lowered that default from 1 satoshi per virtual byte to 0.1, with miners able to accept as little as 0.001. Whether an output is small enough to be refused as dust, whether a stuck payment can be replaced, whether a parent transaction can be rescued by a child: these are Bitcoin Core defaults, not laws of nature. The fee your exchange suggests when you withdraw almost certainly came from its own Core node's estimator.

The same defaults reach into custody. If you keep a wallet in Bitcoin Core itself, version 30.0 removed the old legacy wallet format entirely, so an ancient wallet.dat has to be migrated rather than opened. Anyone with a decade-old backup should test the migration long before they need the coins.

The broader point is one this site keeps returning to. Our exchange reviews cover fees, custody and withdrawal policy, and our country guides cover who may legally serve you, but every platform in both lists is ultimately reporting what a node told it. Buying is a relationship with a company. Verifying is not, and Bitcoin Core is the tool that lets you stop asking.

The OP_RETURN argument and version 30.0

The fight that defined Bitcoin Core's 2025 was about 83 bytes.

For years the default limit on the data an OP_RETURN output could carry was 83 bytes, and nodes would not relay anything larger. Version 30.0 raised that default to 100,000 and allowed several such outputs in one transaction, which in practice removes the cap. The argument for it was that the limit had stopped working: people wanting to store data on the chain were already using witness space and private submission channels to miners, so the rule punished honest users and taught everyone else to route around the public relay network. The argument against was that Bitcoin Core should not make it easier, whatever the workarounds.

What makes the episode instructive is what did not happen. No rule about block validity changed. A node with the old setting and a node with the new one accept exactly the same blocks, disagree only about what they will pass along beforehand, and stay on the same chain. The visible result was a migration: Bitcoin Knots, which keeps a much tighter default, went from a rounding error to roughly a fifth of reachable nodes over the following year. That is what disagreement inside bitcoin looks like when nobody can force anybody.

Bitcoin Core vs Bitcoin Knots

Bitcoin Core and Bitcoin Knots validate identically and relay differently. Knots is built from Core's code with extra patches, keeps stricter defaults about which transactions it will pass on, and adds configuration knobs Core does not ship. Neither creates a separate coin, because relay policy is not a consensus rule. Choosing between them is choosing which transactions your own machine will forward, and how much you value a large review process against a small one that shares your view of what belongs in a block.

Bitcoin Core vs node

Bitcoin Core is a piece of software; a node is the role that software plays on the network. The distinction matters because alternatives exist. Knots, btcd and libbitcoin all speak the same protocol, and a Core installation with its wallet switched off is still a full node. Going the other way, plenty of products described as nodes are wallets with a nice case. When someone says they run one, the useful follow-up question is whether it validates blocks for them or merely holds their keys.