Bitcoin Core Review 2026: Who Should Actually Run a Node
How we reviewed this: from the project’s own documentation, published audits and independent security research.
No company, no fees, no spread and nothing to sell you — the only software here with no business model. It also wants 756GB of disk and several days to start, and for most Canadians it is the wrong first wallet.
By the CryptoNorth Team
Two Things in One Program
Bitcoin Core is the original Bitcoin software, and it does two jobs that people constantly conflate. It is a full node, which downloads and independently verifies every Bitcoin transaction ever made. It is also a wallet, which holds keys and sends coins. You can use either without caring much about the other.
Nearly everything interesting about Bitcoin Core is the node half. As a wallet it is spartan: Bitcoin only, no price charts, no swaps, no phone app, no help if you get stuck. As a node it is the only way to hold Bitcoin without asking somebody else whether your money is real.
What It Actually Requires
Figures from Coin Bureau's 2026 node guide[1]. Initial block download must pull the full 756GB even if you intend to prune afterwards.
Pruned or Archival?
This is the decision that determines whether running a node is realistic on the computer you already own.
Downloads and verifies every block, then deletes the old ones. Technically possible from 550 MiB; 20–100GB is sensible[1]. You get identical verification — nothing is trusted on your behalf — you just cannot serve old blocks to other nodes or rescan deep history.
Keeps the entire 756GB chain and serves it to peers syncing for the first time. Needs a 2TB SSD. This is a contribution to the network rather than a benefit to you personally.
The important point, widely misunderstood: a pruned node is a full node. It validates every rule against every block. Pruning discards history after checking it, not instead of checking it.
What You Get, and What You Do Not
- You verify your own balance rather than trusting a server
- A private backend for your wallet, so you are not broadcasting your addresses to a third party[1]
- You enforce Bitcoin's rules yourself
- No company can change, price or withdraw it
If somebody tells you running a node pays, they are describing something else. The return is sovereignty and privacy, not yield.
Upgrading From an Old Version? Migrate Your Wallet First
The current release is 31.1. The change that matters here arrived in v30, released 10 October 2025[3], contains a change that can lock existing users out of their own wallet file if they upgrade carelessly.
v30 drops Berkeley DB legacy wallets. If you use Bitcoin Core's own built-in wallet, you need to run the migratewallet RPC to convert it to a descriptor wallet. The tool ships inside v30 and later, so you can migrate after upgrading as well as before — but back up your wallet file either way[2]. Anyone using Core purely as a node behind Sparrow, Electrum or a hardware wallet is unaffected. Back up your wallet file first regardless.
v30 also raised the OP_RETURN data limit — previously 80 bytes, now up to 100,000 bytes with multiple outputs permitted[2][3]. Supporters argued it aligns node defaults with what miners already accepted and reduces UTXO bloat (the growing set of unspent coins every node must track). Critics including Luke Dashjr and Nick Szabo warned about blockchain bloat, higher node costs and permanently stored illicit data[3].
Objectors moved to Bitcoin Knots, a more conservative client with stricter defaults, which grew from low single digits to over 21% of all Bitcoin nodes[3]. It is worth being clear that both clients validate the same blockchain — this is a disagreement about relay policy, not consensus, and there is no chain split[2]. Your coins are unaffected whichever you run.
The Best Way to Use It
Most people who run Bitcoin Core well do not use its wallet. They run it as a node and point better software at it:
That combination is the strongest self-custody setup available to a Canadian, and it costs the price of one hardware wallet plus some patience. The official full node guide[4] is the place to start.
Pros and Cons
Frequently Asked Questions
Not permanently. The initial block download pulls the whole chain because every block must be verified, but a pruned node then deletes old blocks and settles at anywhere from 550 MiB upward - 20 to 100GB is the practical range. A pruned node is still a full node: it checks every rule against every block, it just does not keep the history afterwards.
No. Nodes verify transactions; miners produce blocks and collect rewards. Running a node costs you electricity, bandwidth and disk and pays nothing. What you get instead is the ability to verify your own balance without trusting anyone else, and a private backend so your wallet is not telling a third-party server which addresses are yours.
It improves your privacy but does not make transactions private. Bitcoin is a public ledger and always will be. What a node stops is the leak that happens when a light wallet asks somebody else’s server about your addresses - that server learns which addresses belong to you. Running your own removes that particular exposure and nothing more.
Only after migrating. v30 removed Berkeley DB legacy wallet support entirely, so run the migratewallet RPC to convert to a descriptor wallet before you upgrade, and back up your wallet file first. If you only use Core as a node behind Sparrow, Electrum or a hardware wallet, this does not affect you.
For most Canadians, no. It holds only Bitcoin, has no mobile app, no swaps, no recovery help and expects you to know what you are doing. The better pattern is to run Bitcoin Core as your node, keep your keys on a hardware wallet, and use something like Sparrow as the interface between them. That gives you private verification and offline keys without relying on Core’s own wallet at all.
This review is for informational purposes only and is not financial or security advice. Blockchain size, sync times and hardware requirements change continuously — the figures here are from mid-2026 reporting. Always download Bitcoin Core from bitcoincore.org and verify the release signatures. Back up any wallet file before upgrading.
Download from bitcoincore.org and verify the release signatures before running it.