A production node is part of a service with users and responsibilities. Start by defining what depends on it, who operates it and what an interruption would mean.
01 / Specify the workload
Identify the applications using the node, required indexes and storage needs. Record the software version and configuration. Capacity planning should allow room for growth and maintenance.
02 / Restrict administration
Keep RPC and management interfaces private. Separate application credentials from administrative access, and grant only the permissions the integration needs. Review firewall rules before exposing the service.
03 / Observe useful signals
Check synchronization, peer connectivity, disk capacity and application errors. Bitcoin Core RPC methods such as getblockchaininfo and getnetworkinfo can support health checks; interpret them in the context of your deployment.
04 / Own the recovery process
Document configuration backups, maintenance windows and restoration ownership. If Lightning is involved, use the recovery procedure for that implementation; node state and channel recovery need special care.
Planning guidance. Confirm procedures against your software version’s documentation and seek qualified support for your environment. Reviewed October 31, 2026.