How to set up a Bitcoin node on Raspberry Pi? (Solo Mining)

Hardware Requirements and Preparation

1. A Raspberry Pi 4 Model B with at least 4GB RAM is strongly recommended for stable operation.

2. A high-endurance microSD card of minimum 128GB capacity is required to store the full blockchain, which exceeds 600GB and grows continuously.

3. An external USB 3.0 SSD connected via a powered USB hub ensures reliable I/O performance and prevents SD card corruption during intensive sync operations.

4. A heatsink-fan combo must be installed to maintain CPU temperature below 70°C under sustained load; thermal throttling severely impacts block validation speed.

5. A stable power supply delivering 5.1V/3A is non-negotiable—voltage drops cause filesystem corruption and node crashes.

Operating System and Base Configuration

1. Raspberry Pi OS Lite (64-bit) is the only officially supported and tested distribution for Bitcoin Core on ARM64 architecture.

2. Disable swap file using sudo dphys-swapfile swapoff && sudo dphys-swapfile uninstall to prevent disk wear and latency spikes.

3. Enable cgroups v2 and set kernel parameters in /boot/cmdline.txt: cgroup_enable=cpuset cgroup_enable=memory cgroup_memory=1.

4. Configure static IP and disable Bluetooth/WiFi if wired Ethernet is available—network stability directly affects peer connectivity and block relay timing.

5. Update system packages and install dependencies: sudo apt update && sudo apt install build-essential libtool autotools-dev automake pkg-config bsdmainutils python3 libssl-dev libevent-dev libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-test-dev libboost-thread-dev.

Compiling Bitcoin Core from Source

1. Download the latest stable Bitcoin Core release tarball from bitcoincore.org and verify its SHA256 hash against the signed manifest.

2. Extract source and enter directory: tar -xzf bitcoin-25.1.tar.gz && cd bitcoin-25.1.

3. Configure build with ARM64 optimizations and disable GUI components: ./configure --disable-gui --disable-tests --disable-bench --with-incompatible-bdb --enable-hardening --enable-suppress-external-bindings.

4. Compile using exactly four threads to avoid overheating: make -j4. Expect compilation time exceeding 90 minutes on stock clocks.

5. Install binaries globally: sudo make install, then verify with bitcoind --version.

Node Initialization and Blockchain Sync

1. Create dedicated user and data directory: sudo adduser --disabled-password --gecos '' bitcoin && sudo mkdir -p /mnt/ssd/bitcoin && sudo chown bitcoin:bitcoin /mnt/ssd/bitcoin.

2. Initialize configuration file ~/.bitcoin/bitcoin.conf with: server=1\nrpcbind=127.0.0.1\nrpcport=8332\nrpcallowip=127.0.0.1\nzmqpubrawblock=tcp://127.0.0.1:28332\nzmqpubrawtx=tcp://127.0.0.1:28333\nprune=0\ndbcache=1000\nmaxconnections=40\nbind=0.0.0.0:8333.

3. Launch daemon as background service: sudo -u bitcoin bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf -datadir=/mnt/ssd/bitcoin.

4. Monitor sync progress via bitcoin-cli getblockchaininfo | jq '.blocks,.headers,.verificationprogress'—expect 10–14 days for full sync on SSD.

5. Confirm active inbound/outbound peers using bitcoin-cli getpeerinfo | jq '[.[] | select(.direction == 'in') | .addr] | length' and ensure value exceeds 5.

Frequently Asked Questions

Q: Can I mine Bitcoin blocks profitably using only a Raspberry Pi?A: No. Solo mining on Raspberry Pi is technically possible but economically irrelevant—the device lacks computational throughput to solve proof-of-work puzzles within the 10-minute block interval. Hashrate remains below 0.001 MH/s while network difficulty demands exahash-scale infrastructure.

Q: Is pruning enabled by default in Bitcoin Core on Raspberry Pi?A: Pruning is disabled unless explicitly configured. The default setting stores full blocks indefinitely, requiring over 600GB of persistent storage space.

Q: Why does bitcoind crash after several hours of operation?A: Most crashes stem from thermal throttling or insufficient RAM. Monitor temperature with vcgencmd measure_temp and memory pressure with free -h; sustained >90% usage triggers OOM killer termination.

Q: Can I run Electrum personal server alongside bitcoind on the same Pi?A: Yes, but it increases memory footprint and disk I/O contention. Electrum Server requires additional indexing and doubles write amplification on SSD—only deploy if RPC calls are strictly necessary for wallet integration.