Bitcoin Core Wallet Encryption: Passphrases and Unlock State

This guide explains Bitcoin Core wallet encryption in plain English. It focuses on what the subject is, why it matters and what a beginner should remember.

What encryption covers

Encrypted wallets protect private keys in the wallet database. Addresses, labels, transaction records and other metadata may remain visible. Filesystem permissions, encrypted backups and host security remain necessary. A compromised running process or authenticated RPC client can exploit an unlocked wallet regardless of disk encryption.

Initial encryption transition

Core 0.12 deliberately stopped after encryptwallet and warned that the keypool had been flushed. Plan maintenance, verify shutdown completion, restart under supervision, refill or inspect the keypool as supported and immediately create a new validated backup. Preserve the pre-change backup until recovery is proven.

Timed unlock semantics

walletpassphrase accepted a timeout and an already-unlocked call reset that deadline in the historical behaviour. Concurrent automation can unexpectedly extend or shorten access. Centralise unlock ownership, use the shortest practical window and confirm lock state after the signing operation rather than relying on a timer alone.

RPC and command-line leakage

Passphrases supplied through RPC exist in request parameters and process memory; shell commands may enter history or monitoring. Keep RPC local or encrypted, limit client access, suppress unsafe tracing and never paste secrets into support channels. Review adjacent proxy and web-server logs for request capture.

Keypool and unattended receipt

An encrypted locked legacy wallet could use previously generated keys but could not always replenish them. Exhaustion could disrupt new addresses or historical mining workflows. Monitor keypool size, refill during a controlled unlock and take an updated backup because new keys change recovery coverage.

Passphrase strength and custody

Use a high-entropy unique passphrase stored through an approved secret-custody process. A forgotten passphrase is not recoverable by Core, while a weak one allows offline guessing against a stolen wallet. Define multi-person recovery without placing the passphrase beside every backup.

How specialists test it

Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.

Conclusion

Wallet encryption is one layer protecting keys at rest. Safe operation also controls RPC exposure, timed unlock state, keypool freshness, backup custody and a rehearsed recovery path.