A node of your own
A wallet asks someone what's in the ledger. A node is how you ask yourself.
A node is a computer with a copy of Bitcoin's ledger, which checks every block and every transaction for itself. The most widely used program is Bitcoin Core, free software under the MIT licence. As of November 2026 the current version is 32.1.1
Why
You check the rules. The node rejects a block that doesn't follow them, even if others accept it.2 The 21 million limit isn't something someone else vouches for: your own computer verifies it.
You don't give your addresses away. A wallet without a node asks someone else's server for the balance of its addresses. That server sees the addresses and your IP, and could even hide a transaction from you.3 With your own node the questions stay at home.4 The same goes for explorers: lesson 3 explains how to look things up privately.
You don't depend on third parties. If your wallet's server shuts down, your node keeps reading the ledger.
You don't need one to get started. A wallet is all you need to pay for a coffee. The node is the next step, for anyone who wants to verify.
From the simplest to the most complete
1. A wallet that knows where to ask
The first step costs nothing: a wallet that lets you choose the server. Today you connect it to a public one, tomorrow to your own node, or to the node of someone you trust.
On a computer, Sparrow, under the Apache 2.0 licence, and Electrum, MIT, both do this. Sparrow can also connect straight to Bitcoin Core.5 On a phone, BlueWallet, MIT, accepts an Electrum server of your choice.6
The same goes for a paper wallet made with dice: to check its balance you need the address, and asking your own node gives it away to nobody. Without a node there is ericonto: our server asks in your place.
2. Bitcoin Core on a computer at home
You download it from bitcoincore.org. Today's numbers:
| Bitcoin Core | November 2026 |
|---|---|
| Full ledger | 779 GB as of 28 October 2026,7 growing by 5-10 GB a month1 |
| Memory | 2 GB of RAM at least8 |
| Bandwidth | about 20 GB a month incoming; outgoing can go above 200 GB, but it can be capped8 |
| First sync | a few days at least;8 2-5 days on a Raspberry Pi 5 with an SSD9 |
| Uptime | at least 6 hours a day8 |
Pruned. If the disk is small, the node can keep only the latest blocks: that's pruning. With prune=550 a few GB are enough instead of nearly 800.8 It still verifies everything, but it has to download the lot once, and it can't act as an archive: no transaction index, so no Electrum server and no explorer.
The disk. You need an SSD. For the full ledger, with the indexes, a 1 TB disk is already tight today.
Outgoing bandwidth is your call: Bitcoin Core has options to stop serving blocks to others or to set a daily cap.10
3. A node in a box
There are ready-made systems that install the node and the apps around it in a few clicks, from a web page. Before you pick one, check the licence: it tells you what you can do with that software.
| System | Licence | Free software? |
|---|---|---|
| StartOS, by Start9 | MIT11 | Yes |
| RaspiBlitz | MIT12 | Yes |
| Umbrel | PolyForm Noncommercial 1.0.013 | No: it forbids commercial use |
| myNode | Creative Commons BY-NC-ND, modified14 | No: it forbids commercial use and distributing modified versions |
Under the Open Source Initiative's definition, a licence can't exclude a field of use, commerce included.15 Umbrel and myNode can be used at home, but the code isn't free.
What it costs. A Raspberry Pi 5 draws a few watts at idle,16 a few euros of electricity a year. The 16 GB Pi 5 costs 305 dollars on the maker's site, disk not included.17 A second-hand mini PC or an old computer with a new SSD will do just as well.
4. Your own Electrum server and explorer
The node can answer questions about transactions, but it can't search by address. That's why you run an Electrum server alongside it: that's what answers the wallets from step 1.
- electrs, MIT: the index adds about a tenth to the ledger's size.18
- Fulcrum, GPL 3, heavier: back in 2023 the index was already over 130 GB.19
On top of the Electrum server you can also run an explorer of your own, such as mempool, AGPL 3, which needs the full ledger with the transaction index.20 It's the same explorer as in lesson 3, but your searches never leave home. Until you have your own there is inexp, here on the site: our server does the searching and keeps none of it.
5. A Lightning node
Here the job changes. A Lightning node keeps channels, that is, bitcoin locked into two-party transactions, and it has to stay on: if it's off, you don't get paid. The main programs are free software: LND (MIT), Core Lightning (BSD-MIT), Eclair (Apache 2.0) and LDK (Apache 2.0 or MIT), on which other wallets are built.21
- Every channel costs. Opening and closing one are on-chain transactions, each with its own fee.
- To receive you need room on the other side. A channel you open can pay straight away, but it can only receive once you've spent, or if someone opens a channel to you.22
- Backups are delicate. Copying the disk isn't enough: restoring an old state can cost you your funds. Restoring from LND's static channel backup, for example, closes the channels and brings the bitcoin back on-chain.23 Read the guide for the software you use before you put money into it.
To take payments in a shop, your own node gives you a Lightning address that the till can read only if it answers the question “has it been paid?”. Lesson 5 explains which one.
The phone for those with a Lightning node
These wallets aren't for getting started: you need to know what channels and liquidity are. They are free software, and the keys stay with you.24
| Wallet | Where | What it does |
|---|---|---|
| Zeus | Android, iPhone | Controls a node of your own from your phone, or runs one on the phone: the first payment you receive opens a channel, with a fee of at least 1,000 sats.25 With the phone off, an outside service holds the payment until you open the app again |
| Alby Hub | Windows, Mac, Linux | A real node on a computer that stays on |
| BitBanana | Android | Controls a node of your own, LND or Core Lightning, from your phone |
In our test on 2 November 2026, Zeus and Alby Hub gave the till an address that works; we haven't taken a real payment with them. In Zeus the address, something@zeuspay.com, is in the menu, under “Lightning address”.26 The free one comes with an automatically generated name; to choose your own there's a paid version, which the till doesn't need.27 With Alby Hub and BitBanana, follow the steps in their guides; with a node of your own, the node gives you the address. How to test it at the till: The shop's wallet.
6. BTCPay Server on your node
The last step is the till. BTCPay Server, under the MIT licence, creates invoices and checks them on your own node, with nobody in between. It needs at least 2 GB of RAM and 80 GB of disk with a pruned ledger. You install it with Docker on a rented server, between 10 and 70 dollars a month, or at home, which the documentation itself calls the hard way.28
This site doesn't use BTCPay: the Valley's till requests the invoice from the Lightning address of the merchant's wallet, and doesn't need a node. The software explains how. If you do have a node of your own, though, you can use its Lightning address at the till, as long as it answers “has it been paid?” (LUD-21): how to test it.
In short
| Step | Effort | Cost |
|---|---|---|
| A wallet that lets you choose the server | Minutes | Nothing |
| Bitcoin Core, pruned or not | An afternoon, then days of waiting | An SSD, if you already have the computer |
| Node in a box | An afternoon | A few hundred euros of hardware |
| Electrum server and explorer | A few more hours | More disk |
| Lightning node | Study, and upkeep that never ends | Channel fees |
| BTCPay Server | A day, and a server that's always on | From nothing to a few tens of euros a month |
Looking into the ledger Spark, and what we're keeping an eye on
-
Bitcoin Core, download and 32.1 release notes, 27 October 2026. The code: github.com/bitcoin/bitcoin, MIT licence. ↩↩
-
Bitcoin Wiki, Full node, edited on 12 August 2026. ↩
-
Sparrow, Connect your node; the code on GitHub, Apache 2.0. Electrum on GitHub, MIT. ↩
-
BlueWallet on GitHub, MIT; connecting it to your own server in the Start9 guide. ↩
-
Blockchain.com, blockchain size: blocks and transactions, without indexes. ↩
-
bitcoin.org, Running a full node, read on 3 November 2026. ↩↩↩↩↩
-
RaspiBolt, Bitcoin client, with Bitcoin Core 32.1. ↩
-
RaspiBlitz on GitHub, MIT licence. ↩
-
Umbrel, LICENSE.md and their License FAQ. ↩
-
Open Source Initiative, The Open Source Definition, point 6. ↩
-
Jeff Geerling, 2023: 2 to 3 W at idle, depending on the power supply and the meter. At 3 W that's about 26 kWh a year, under 10 euros at 30 cents per kWh. ↩
-
Raspberry Pi 5, read on 3 November 2026. ↩
-
electrs on GitHub, README. ↩
-
Fulcrum on GitHub, README, figure from August 2023. ↩
-
mempool, Docker instructions; licence in the LICENSE. ↩
-
LND, Core Lightning, Eclair, LDK. ↩
-
Lightning Labs, Disaster recovery; for Core Lightning, Backup. ↩
-
Zeus: AGPL 3, code on GitHub, which also says the keys stay with the user. Alby Hub: Apache 2.0, code on GitHub, which describes it as “self-custodial”. Read on 5 November 2026. BitBanana: open source and free, “fully self-custodial”, according to its page, read on 11 November 2026. ↩
-
From the Zeus code,
views/Receive.tsx(GitHub): on the first payment received, the channel opening fee is at least 1,000 sats; Olympus, Zeus's provider, opens channels with at least 100,000 sats of inbound capacity. Checked on 11 November 2026. ↩ -
Zeus, documentation: Lightning address. We haven't tried the menu on a phone: if it changes in the app, go by the name you find there. ↩
-
Zeus, “New release: ZEUS v0.11.0”: the paid version, ZEUS Pay+, costs 80,000 sats a year and lets you choose the name; anyone who doesn't pay gets one generated automatically. ↩
-
BTCPay Server, deployment FAQ and ways to deploy; the code on GitHub, MIT. ↩