Bitcoin Node

Run your own Bitcoin node at home in Switzerland

7 min read
MH
Written by Mohamed Habbat

I work in the crypto self-custody space, and in 2026 the question Swiss holders ask me once their cold storage works is how to check their coins with their own node running Bitcoin Core 31.1 (release notes).

Your hardware wallet protects your keys, but it does not check the rules. Every wallet that asks a public server for your balance trusts that server's answer and tells it which addresses you hold. A full node removes both problems.

TL;DR

A Raspberry Pi 5, a 2 TB NVMe SSD and Bitcoin Core 31.1 are enough. The blockchain was 774 GB on 9 October 2026 (Blockchain.com). Forward TCP port 8333 if you want inbound peers, add Tor for privacy, and add electrs or Fulcrum if you use Electrum or Sparrow. Even at the full 25 W rating of the Pi 5 power supply, a year of electricity costs about CHF 61 at the 2026 Swiss median tariff (ElCom).

Step 1 Select the hardware

A Raspberry Pi 5 with a 2 TB NVMe SSD is the common low-cost choice. Raspberry Pi specifies a 5 V, 5 A (25 W) USB-C supply for the Pi 5 (Raspberry Pi documentation).

That rating gives an upper bound on cost. ElCom reports a 2026 median household tariff of 27.7 Rp./kWh and 26.5 Rp./kWh for 2027 (ElCom, 8 September 2026):

25 W × 8,760 hours = 219 kWh a year × CHF 0.277 = CHF 60.66 a year at most

Your node will draw well below its supply rating, so your bill will be lower. A plug-in power meter tells you the real figure for your setup. Your own tariff depends on your grid operator; strompreis.elcom.admin.ch lists it by municipality.

A mini PC gives more headroom for an Electrum server or a Lightning node, at a higher power draw. A NAS can run Bitcoin Core in a container, but check that its disks are fast enough for the initial sync.

Step 2 Choose the node software

Bitcoin Core 31.1, published on 8 July 2026, is the current release of the reference implementation (Bitcoin Core 31.1). Download it only from bitcoincore.org and verify the SHA256SUMS file and its signatures before you install, every time.

Bitcoin Knots is a derivative maintained by Luke Dashjr. Its current release is v29.4.2.knots20260508, published on 21 September 2026 (Knots release). The two differ in relay policy, not in consensus rules. Since Bitcoin Core 30.0 the default datacarriersize is 100,000 bytes, which effectively removes the old OP_RETURN limit (Bitcoin Core 30.0). Knots keeps the old 83-byte default (Knots policy.h) and treats data hidden in scripts as the bug CVE-2023-50428; NVD notes that others consider it "not a bug" (NVD). We cover that history in the Bitcoin CVE-2023-50428 post.

Both are free, open source and run on ARM64 (Pi 5) and x86-64. They sit alongside the other open-source node and wallet software you can read, build and verify.

Step 3 Plan storage and bandwidth

The blockchain was 774 GB on 9 October 2026 and grew by about 82 GB in the previous 12 months (Blockchain.com). A 2 TB SSD leaves room for several years plus the index of an Electrum server.

The initial block download (IBD) transfers the whole chain once. How long it takes depends more on the CPU and the SSD than on a fast fibre line; on a Pi 5, plan for days rather than hours.

After IBD, serving old blocks to new nodes is the largest part of your upload traffic. Bitcoin Core's -maxuploadtarget option, set in MiB per day, stops serving blocks older than one week once the target is near (reduce-traffic.md). Check your plan for a data cap before you open port 8333.

A pruned node (prune=550 keeps about 550 MiB of blocks) saves disk, but it cannot serve old blocks or feed electrs or Fulcrum. Steps 6 and 7 assume a full archival node.

Step 4 Open port 8333 on the router

A node without inbound connections still validates every block and transaction. Opening TCP port 8333 lets other nodes connect to yours and download blocks from you.

Give the node a fixed LAN address through a DHCP reservation in your router, so the forwarding rule survives a lease renewal. Then forward TCP port 8333, external and internal, to that address. Swisscom, Sunrise and other providers put this under port forwarding or NAT in the router's admin page; the menu names differ by model.

Never forward the RPC port 8332. It gives full control of the node.

If you want inbound peers only over Tor, skip the port forward and use the onion service from Step 5.

Step 5 Add Tor

Install Tor on the node machine. On Raspberry Pi OS or Ubuntu run sudo apt install tor. Then add this line to bitcoin.conf so outbound peer connections go through Tor:

proxy=127.0.0.1:9050

If Bitcoin Core is listening and can reach the Tor control port, it creates an onion service automatically (doc/tor.md). On most Linux systems that means enabling these lines in /etc/tor/torrc and adding your user to the Tor group:

ControlPort 9051
CookieAuthentication 1
CookieAuthFileGroupReadable 1

After a restart, the onion address appears in debug.log and in bitcoin-cli getnetworkinfo under localaddresses.

With Tor, peers see an onion or Tor exit address instead of your home IP when you broadcast a transaction. Your ISP still sees that you use Tor. If you want only onion peers, add onlynet=onion.

Step 6 Connect bitcoin-cli and your wallet

Bitcoin Core answers JSON-RPC on port 8332. bitcoin-cli on the same machine authenticates with the cookie file Bitcoin Core writes to its data directory. Check the node:

bitcoin-cli getblockchaininfo
bitcoin-cli getnetworkinfo

Sparrow Wallet connects to Bitcoin Core directly (Sparrow guide). On the same machine it reads the cookie file. From another machine on your LAN, add rpcbind and rpcallowip lines for your network and a user and password to bitcoin.conf, then enter them in Sparrow under Server. Sparrow derives your addresses from the extended public key and asks only your node about them. See the Bitcoin self-custody guide for the wallet side.

Electrum uses its own protocol instead of RPC, so it needs the server from Step 7.

Step 7 Run electrs or Fulcrum

electrs and Fulcrum build an address index from your node and answer Electrum-protocol queries locally.

electrs is written in Rust and has the smaller footprint, which suits a Raspberry Pi. It listens on 127.0.0.1:50001 by default and does not provide SSL (electrs config). For access from another machine, its documentation recommends an SSH tunnel, or an NGINX SSL endpoint on port 50002.

Fulcrum is written in C++ and can serve SSL itself when you give it a certificate (Fulcrum). Its README recommends SSL for production use. It suits a mini PC with more memory, for example next to a Lightning Network home node.

Build the index after IBD completes; on a Pi 5 it takes hours. Then point Electrum, or Sparrow with the Electrum server connection type, at your server. Every balance query and broadcast from your wallet then goes through hardware you own.

Step 8 Back up configuration and any wallet

A node that holds no keys needs little backup. Save bitcoin.conf, torrc and the electrs or Fulcrum configuration to encrypted offline storage. If the machine dies, you rebuild it with the same files and let IBD run again.

If you keep a wallet on the node, note the change in Bitcoin Core 30.0: legacy wallets can no longer be created or loaded, and old wallet.dat files must be converted with the migratewallet RPC (Bitcoin Core 30.0). Back up the descriptor wallet with bitcoin-cli backupwallet, keep the copy encrypted and offline, and test a restore on a second machine before you rely on it.

If you plan to run a miner next to the node, the home Bitcoin mining 2026 guide covers power, cooling and network.

Why it is worth the afternoon

With your own node, the addresses you watch, the transactions you send and the blocks you accept go through hardware you own. Public Electrum servers and block explorers see every address you look up; your node does not report them to anyone.

Your hardware wallet already keeps the keys with you, and the node does the same for your balance lookups.


Bitcoin Core and Knots versions, hardware prices and electricity tariffs change. Check each source before you buy. A home node is a verification and privacy tool, not an investment. This is education, not advice.


New to self-custody? Start with Bitcoin self-custody from zero to cold wallet before setting up a node.

Building a full home Bitcoin stack? The Lightning Network home setup guide covers the next layer on top of a running full node.

Want the full picture? Read all 19 chapters free or order the physical book.

Frequently Asked Questions

Why run a Bitcoin node at home?
A full node checks every block and transaction against the consensus rules itself. When your wallet queries your own node, no outside server learns which addresses you watch. Public Electrum servers and block explorers see every address you look up.
What is the difference between a full node and a pruned node?
Both validate every block. A full archival node keeps the whole blockchain, 774 GB on 9 October 2026 (Blockchain.com chart data). A pruned node deletes old blocks after checking them; prune=550 keeps about 550 MiB. Only an archival node can serve old blocks to peers or feed electrs or Fulcrum.
How much electricity does a Raspberry Pi node use in Switzerland?
Raspberry Pi specifies a 5 V, 5 A (25 W) supply for the Pi 5. At that full rating all year, the board would use 219 kWh, about CHF 61 at ElCom's 2026 median household tariff of 27.7 Rp./kWh, or CHF 58 at the 2027 median of 26.5 Rp./kWh. A node draws well below the supply rating, so the real cost is lower. A plug-in power meter gives your own figure.
Bitcoin Core or Bitcoin Knots?
Both enforce the same consensus rules. Bitcoin Core 31.1 is the reference implementation. Since Core 30.0 the default datacarriersize is 100,000 bytes; Knots, maintained by Luke Dashjr, keeps the 83-byte default. Choose Knots if you want your mempool to reject larger data-carrying outputs; choose Core for the widely reviewed default.
Do I need a static public IP?
No. Forward TCP port 8333 to a fixed LAN address of the node. If your public IP changes, peers find you again under the new address. An onion address from Tor does not depend on your public IP at all.
What does Tor change for a node?
With proxy=127.0.0.1:9050, Bitcoin Core makes its outbound peer connections through Tor, so peers do not see your home IP. If the node listens and can reach the Tor control port, it also publishes an onion address that peers and your own wallets can reach. Your ISP still sees that you use Tor.
What is electrs and why would I need it?
electrs is an Electrum server written in Rust. It indexes your node's blockchain and answers address and UTXO queries from Electrum or Sparrow. Without your own server, those wallets ask public servers run by third parties. electrs serves plain TCP on port 50001 and needs a tunnel or proxy for SSL.
How does Fulcrum compare to electrs?
Fulcrum is an Electrum server written in C++. It can serve SSL itself when you give it a certificate, and its README recommends SSL for production use. electrs has the smaller footprint that suits a Raspberry Pi.
Can Sparrow connect directly to my node?
Yes. Sparrow's Bitcoin Core connection type reads the cookie file on the same machine. From another machine, add rpcbind and rpcallowip lines and a user and password to bitcoin.conf and enter them in Sparrow, as its guide describes.
Do I have to open port 8333?
No. A node with only outbound connections validates everything. Opening the port lets other nodes connect to yours and download blocks from you.
How much upload traffic does a listening node cause?
It depends on how many new nodes download old blocks from you. Bitcoin Core's -maxuploadtarget, set in MiB per day, stops serving blocks older than one week once the target is near. Measure your traffic for a month before you set it, especially on a plan with a data cap.
What happens if my node is offline for a few days?
Nothing is lost. When it comes back, it downloads and checks the blocks it missed, about 144 a day at one block every ten minutes. Your wallet queries work again once it has caught up.