This guide explains Bitcoin Core sethdseed 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 sethdseed set or generated a new HD seed for an existing HD wallet; it did not upgrade a non-HD wallet. Newkeypool defaulted true and flushed unused receive and change addresses. False retained the old keypool until depletion.
- Why it matters: sethdseed rotates future key generation and may reshape the keypool. Safe use requires explicit transition policy, immediate new backup and tested recovery across both seed eras.
- 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 sethdseed RPC in simple English
Bitcoin Core sethdseed RPC: Create and test a new protected wallet backup immediately. Older backups may still cover older keys but cannot recover keys later derived from the new seed.
Simple example
A miner is checking Bitcoin Core sethdseed RPC. Confirm the exact loaded wallet is HD and rotation is authorised under dual control. Omitting seed generates one.
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.
Eligibility
Confirm the exact loaded wallet is HD and rotation is authorised under dual control. Pause address issuance, signing and deposits. Non-HD wallets remain non-HD.
Seed choice
Omitting seed generates one; supplying seed uses a WIF private key. Treat supplied WIF as full custody material and keep it away from shells, logs and general middleware.
New keypool true
The default flushes unused receive and change addresses. Inventory issued but unpaid addresses first; a local flush does not notify customers or invalidate distributed addresses.
New keypool false
False uses existing pool entries until depleted, creating a mixed seed transition. Record depth, boundary and issued addresses so recovery covers both eras.
Mandatory backup
Create and test a new protected wallet backup immediately. Older backups may still cover older keys but cannot recover keys later derived from the new seed.
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.
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 sethdseed RPC?
Bitcoin Core sethdseed RPC: Create and test a new protected wallet backup immediately. Older backups may still cover older keys but cannot recover keys later derived from the new seed.
For Bitcoin Core sethdseed RPC, what should a beginner know about eligibility?
Confirm the exact loaded wallet is HD and rotation is authorised under dual control.
For Bitcoin Core sethdseed RPC, what should a beginner know about seed choice?
Omitting seed generates one. Supplying seed uses a WIF private key. Treat supplied WIF as full custody material and keep it away from shells, logs and general middleware.
For Bitcoin Core sethdseed RPC, what should a beginner know about new keypool true?
The default flushes unused receive and change addresses. Inventory issued but unpaid addresses first.
Conclusion
sethdseed rotates future key generation and may reshape the keypool. Safe use requires explicit transition policy, immediate new backup and tested recovery across both seed eras.
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.