This guide explains Bitcoin Core walletpassphrase RPC in plain English. It shows what the command does, what its result means and what it cannot prove.
TL;DR
- What it is: Bitcoin Core 0.16.0 walletpassphrase accepted a wallet passphrase and timeout, storing the wallet decryption key in memory for that many seconds. The timeout was capped at 2^30 seconds, and a call while already unlocked replaced the previous unlock time.
- Why it matters: walletpassphrase creates a time-bounded private-key capability. Safe use protects the secret, serializes overrides, narrows RPC access and proves immediate relock after the one approved operation.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Bitcoin Core walletpassphrase RPC in simple English
Bitcoin Core walletpassphrase RPC: Calling walletpassphrase while already unlocked sets a new unlock time and overrides the old one. Concurrent jobs can therefore unexpectedly shorten or extend each other’s authority.
Simple example
A miner is checking Bitcoin Core walletpassphrase RPC. Alert when a wallet remains unlocked beyond its approved window or when unlock state changes outside the custody orchestrator.
Key terms in plain English
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Passphrase transport
Never place the passphrase in shell history, process listings, tickets or general application logs. Use a protected interactive or secret-injection path over authenticated local RPC. Limit memory lifetime in the calling process and prevent debugging tools from recording request bodies.
Timeout semantics
The timeout is required seconds and values above 2^30 are clamped to that maximum. Choose a short operational window rather than the interface maximum. Display and record the intended expiry and reject negative, fractional, unbounded or unit-confused values before the call.
Override behaviour
Calling walletpassphrase while already unlocked sets a new unlock time and overrides the old one. Concurrent jobs can therefore unexpectedly shorten or extend each other’s authority. Serialize unlock state and reject a new request unless it belongs to the active approved custody operation.
Scope of capability
An unlocked encryption key permits methods that require private keys, including spending and signing. It is not limited to the next requested transaction. Restrict RPC access for the entire window, pause unrelated automations and bind human approval to a decoded transaction intent.
Explicit relock
Call walletlock immediately after the approved operation, including error and cancellation paths. Do not wait for timeout when work finishes early. Confirm the denial state before closing the audit record or allowing the next custody operation to begin.
Monitoring without exposure
Record wallet identifier, operator, ticket, requested duration, actual lock time and outcome, never the passphrase. Alert when a wallet remains unlocked beyond its approved window or when unlock state changes outside the custody orchestrator.
How specialists test it
Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.
Frequently asked questions
What is the main point of Bitcoin Core walletpassphrase RPC?
Bitcoin Core walletpassphrase RPC: Calling walletpassphrase while already unlocked sets a new unlock time and overrides the old one.
For Bitcoin Core walletpassphrase RPC, what should a beginner know about passphrase transport?
Never place the passphrase in shell history, process listings, tickets or general application logs.
For Bitcoin Core walletpassphrase RPC, what should a beginner know about timeout semantics?
The timeout is required seconds and values above 2^30 are clamped to that maximum.
For Bitcoin Core walletpassphrase RPC, what should a beginner know about override behaviour?
Calling walletpassphrase while already unlocked sets a new unlock time and overrides the old one.
Conclusion
walletpassphrase creates a time-bounded private-key capability. Safe use protects the secret, serializes overrides, narrows RPC access and proves immediate relock after the one approved operation.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
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.