Maintenance playbook

Sync status

During initial block download (IBD), your node catches up with the chain. After IBD, it should track new blocks within a reasonable delay when your internet and hardware are healthy.

Read-only diagnostics — blockchain summary (headers, verification progress, chain tip):

bitcoin-cli getblockchaininfo

Look for whether verification progress is near complete, whether the reported chain matches what you expect from other sources you trust, and whether the node reports being on the main chain. A stalled sync can mean bandwidth limits, disk issues, or an interrupted download—not something a single command fixes by itself.

See also myths and safety notes for expectations about mining, yield, and privacy.

Disk space

Full nodes store block data and chainstate. Pruned nodes use less disk at the cost of not retaining the entire block history locally. Either way, running out of space can stop sync or corrupt data if the system cannot write cleanly.

Read-only diagnostics — free space on mounted volumes (adjust the path to your data directory if you know it):

df -h

Plan headroom before IBD finishes and revisit after major releases or log growth on appliance stacks. This site does not prescribe partition layouts or cleanup commands.

Peers and network health

Your node exchanges blocks and transactions with peers over the Bitcoin P2P network. Too few peers can slow sync; unusual peer patterns can sometimes indicate misconfiguration or network issues worth investigating with official docs.

Read-only diagnostics — connection counts and network services summary:

bitcoin-cli getnetworkinfo

Read-only diagnostics — per-peer details (addresses shown may relate to your privacy posture):

bitcoin-cli getpeerinfo

Treat peer lists as operational data, not as a score to optimize for “anonymity.” Privacy depends on wallet connection, routing, and habits—not peer count alone.

Updates

Bitcoin Core and appliance firmware receive security and consensus-related fixes over time. Staying current is generally wise, but upgrades can require downtime, disk checks, and reading release notes—especially around major versions or consensus changes.

• Read official release notes before upgrading Bitcoin Core or an appliance image.
• Prefer maintenance windows when a brief outage is acceptable.
• Do not assume “latest” on day one fixes a mis-sized disk or weak home internet.

This page intentionally omits install, package-manager, or service-restart commands. Use vendor and Bitcoin Core documentation for upgrade steps on your platform.

Backups (configuration and operations)

Backups for a node are about recovering your setup, not about wallet recovery phrases. This site does not cover seed phrases, wallet.dat password recovery, or custody promises.

Document and protect copies of items such as:

• Node configuration — bitcoin.conf (or equivalent) as you actually run it, stored securely and versioned when you change settings.
• App and stack settings — appliance dashboards, compose files, or automation you rely on, with notes on versions.
• Restore notes — plain-language steps you wrote for yourself: hardware, paths, which software builds you used, and how long a resync might take.
• Optional channel or app data — only where relevant to software you chose (for example Lightning or companion apps). Understand what each backup contains; encrypted channel backups are not generic “node backups.”

Privacy habits (operational)

Maintenance overlaps with privacy-first practices: limit who can reach management interfaces, be cautious about which wallets point at your node, and know what logs your stack keeps. Running a node improves verification; it does not automatically anonymize spending.

• Do not expose Bitcoin Core RPC to the public internet—see myths about public RPC.
• Review what home-router or VPS provider logs might retain if you operate remotely.
• Separate “I run a node” from “I publish services for the world to connect to.”

Simple recurring cadence

Adjust frequency to your setup. The goal is calm observation, not obsessive tuning.