Bitcoin Core 0.21 settings.json guide covering wallet autoload state, precedence, GUI and RPC writes, file permissions, recovery and drift detection.
This guide explains Bitcoin Core settings.json in plain English. It focuses on what the subject is, why it matters and what a beginner should remember.
Bitcoin Core settings.json: settings.json stores writable runtime settings in the network data directory. In 0.21 its visible operational role centred on wallet autoload.
A node operator is checking Bitcoin Core settings.json. In 0.21 its visible operational role centred on wallet autoload. It is not a replacement for every bitcoin.conf option.
settings.json stores writable runtime settings in the network data directory. In 0.21 its visible operational role centred on wallet autoload; it is not a replacement for every bitcoin.conf option.
The wallet list augments command-line and bitcoin.conf wallet entries. Duplicate or conflicting sources complicate startup, so inventory the effective result from the running node.
GUI wallet actions and wallet RPC load_on_startup values can modify persistent state. Omitted RPC options leave the list unchanged, preserving backward compatibility.
Stop Core cleanly before offline backup or manual recovery. Protect directory and file permissions, avoid simultaneous writers and never hand-edit production state without a tested, version-matched procedure.
Compare approved wallet inventory with the effective loaded set after every restart. Alert on unplanned additions, removals, malformed JSON, ownership changes and network-directory confusion.
Retain a known-good copy and logs, but do not overwrite a live file. If parsing or startup fails, stop Core, preserve evidence, validate JSON and restore only the smallest confirmed change.
Prefer supported RPC options over direct edits, serialise administrative actions and verify wallet identity, descriptor flag, database format and load-on-startup behaviour across restart. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.
Bitcoin Core settings.json: settings.json stores writable runtime settings in the network data directory.
settings.json stores writable runtime settings in the network data directory. In 0.21 its visible operational role centred on wallet autoload.
The wallet list augments command-line and bitcoin.conf wallet entries. Duplicate or conflicting sources complicate startup, so inventory the effective result from the running node.
GUI wallet actions and wallet RPC load_on_startup values can modify persistent state.
settings.json gave Core a supported place for persistent runtime choices such as wallet autoload. Reliable operations require effective-configuration checks, controlled writers and careful recovery rather than assuming the JSON file acts alone.
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Bitcoin Core 30 data-carrier policy explained: larger OP_RETURN defaults, multiple outputs, aggregate sizing and the boundary between policy and consensus.
Bitcoin Core AssumeUTXO guide covering height 840000 mainnet snapshots, authenticated loading, dual chainstates, background validation, storage and rollback.
Learn how Bitcoin Testnet4 mining works, what it can earn, the costs and security checks, and how a Bitcoin node can support SHA-256 miners.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.