This guide explains Bitcoin Core unloadwallet 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.17.0 unloadwallet removed a wallet from the running process. A wallet-specific endpoint unloaded its wallet without a name argument; a general endpoint could accept wallet_name.
- Why it matters: unloadwallet is runtime custody availability, not deletion. Safe use selects unambiguously, drains dependants, proves absence and preserves a tested warning-aware reload path.
- 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 unloadwallet RPC in simple English
Bitcoin Core unloadwallet RPC: Use either wallet endpoint with no name or general endpoint with wallet_name, never both. Resolve URL encoding and canonical identity.
Simple example
A miner is checking Bitcoin Core unloadwallet RPC. Block service until warnings, scan, tip, key mode and routing pass after reload. Pause deposits, address issuance, transaction creation, signing, rescans and reporting and let in-flight work checkpoint.
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.
Selection modes
Use either wallet endpoint with no name or general endpoint with wallet_name, never both. Resolve URL encoding and canonical identity.
Drain services
Pause deposits, address issuance, transaction creation, signing, rescans and reporting and let in-flight work checkpoint.
Evidence
Capture loaded inventory, lock state, best block, rescan status and protected backup reference. Ensure no temporary signing session remains.
Storage
Unloading detaches runtime state; it does not delete files or reverse upgrades and rescans. Protect the path and avoid ad hoc copying.
Verify absence
Confirm listwallets absence and expected wallet-RPC failure while unrelated wallets and chain processing remain healthy.
Reload
Record exact loadwallet path and startup options. Block service until warnings, scan, tip, key mode and routing pass after reload.
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 unloadwallet RPC?
Bitcoin Core unloadwallet RPC: Use either wallet endpoint with no name or general endpoint with wallet_name, never both.
For Bitcoin Core unloadwallet RPC, what should a beginner know about selection modes?
Use either wallet endpoint with no name or general endpoint with wallet_name, never both.
For Bitcoin Core unloadwallet RPC, what should a beginner know about drain services?
Pause deposits, address issuance, transaction creation, signing, rescans and reporting and let in-flight work checkpoint.
For Bitcoin Core unloadwallet RPC, what should a beginner know about evidence?
Capture loaded inventory, lock state, best block, rescan status and protected backup reference.
Conclusion
unloadwallet is runtime custody availability, not deletion. Safe use selects unambiguously, drains dependants, proves absence and preserves a tested warning-aware reload path.
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.