Bitcoin Core

Bitcoin Core is the reference implementation of the Bitcoin protocol and a direct descendant of the original client released by Satoshi Nakamoto in 2009, renamed from "Bitcoin-Qt" to Bitcoin Core in 2014 to distinguish the software from the network. Maintained as an open-source project under the MIT license, it combines full-node software that independently validates the entire blockchain with an integrated wallet, letting a user verify every consensus rule for themselves rather than trusting a third party.

What it does

When run as a full node, Bitcoin Core downloads and checks every block and transaction in history against the network's consensus rules, rejecting anything invalid — the process that begins with the initial block download and continues for every new block thereafter. This is the practical meaning of "don't trust, verify": a node operator does not rely on anyone else to confirm that coins are real, that no hidden inflation has occurred, or that the rules have not quietly changed. Beyond validation, the node maintains its own mempool of unconfirmed transactions, relays valid blocks and transactions to peers, tracks the UTXO set that defines who can spend what, and serves data to the wallets, explorers, and Lightning nodes stacked on top of it. Operators with limited disk can run a pruned node that discards old raw blocks after validating them, keeping full security on modest hardware.

The wallet and sovereign workflows

The integrated wallet is more capable than its austere reputation suggests: it supports output descriptors, watch-only configurations that track cold keys without holding them, hardware-wallet signing via the PSBT (partially signed Bitcoin transaction) standard, multisig, and full coin control for choosing exactly which UTXOs a payment spends. For a self-custody practice, the pattern of a Core node validating the chain while keys live on dedicated signing hardware is the backbone of most serious setups — and for a home miner, your own node is what makes true solo mining possible, since it is your node, not a pool operator, that builds and validates the block template you work on.

Role in the network

Because most other Bitcoin software depends on the consensus behavior Bitcoin Core defines, it occupies a central but deliberately conservative position. Development is public and community-driven — anyone can contribute code, review, testing, or documentation — with a small set of maintainers merging changes after extensive peer review, and consensus-affecting changes facing the highest bar of all. Yet no single party controls which rules the network enforces: operators choose what software to run, and that collective, revocable choice is what gives the rules their force. The developers propose; the node runners dispose. That inversion — users holding final authority over money's rules by each verifying them independently — is the entire point, and it only works if enough people actually run the software.

What it takes to run

The requirements are more modest than the software's importance suggests. A full archival node stores the entire block history — hundreds of gigabytes and growing — while a pruned node validates everything identically but keeps only recent blocks, fitting in a few gigabytes. The heavy lift is the initial block download, which taxes CPU, disk, and bandwidth for hours to days depending on hardware; an SSD and a generous database cache shorten it dramatically. After sync, steady-state demands are light enough for a single-board computer, which is exactly what the popular node-in-a-box distributions run on. There is no reward for running a node except the only one that matters: verification you own.

Running a node pairs naturally with everything else on the sovereignty path: self-custody, home mining, and self-hosted services. See full node for the general concept and initial block download for the first hurdle, and our coverage of node-bundling operating systems for plug-and-play setups.

Find node software in the sovereign self-hosting catalog.