Safe Mode (Bitcoin Core)

"Safe mode" was an older Bitcoin Core feature that disabled certain RPC calls automatically when the node detected something unusual in the chain state - typically a deep reorg, a long chain with invalid blocks, or other consensus anomalies. The idea was to fail closed: better to refuse to broadcast transactions than to inadvertently operate on a compromised or forked chain.

The feature was removed in Bitcoin Core 0.16 (2018). Why it was retired:

• High false-positive rate. Network conditions that triggered safe mode were often benign (a temporary fork that resolved on its own, a peer feeding bogus block data) but the lockout was disruptive.
• Unreliable signal. The conditions that should genuinely halt operations are hard to define automatically. Safe mode either triggered too readily (annoying) or not on actual problems (useless).
• Better alternatives. Modern Bitcoin Core surfaces warning conditions through getblockchaininfo and getnetworkinfo (the warnings field). Operators can monitor these directly without an automated lockout that may misfire.

What replaced safe mode:

• Explicit warning fields. getblockchaininfo's warnings field reports unusual chain state to anyone querying. Wallets and downstream tools can react however they choose.
• GUI warnings. Bitcoin Core's Qt UI shows a yellow banner if the node sees something concerning, but doesn't disable functionality.
• Operator vigilance. The decision to halt operations during a contentious fork or suspected attack moves from "the node decides for you" to "you decide based on the data the node surfaces."

The concept survives in the broader principle: when something unusual happens at the consensus layer, conservative operators stop operating until the situation is understood. The automation is gone; the discipline isn't.