Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£852.68
EST. MONTHLY
207
DAYS
EST. ROI
This guide explains Bitcoin Core deriveaddresses 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.18.0 deriveaddresses returned addresses corresponding to an output descriptor. Fixed descriptors produced fixed results, while wildcard descriptors required a numeric end or explicit begin-and-end range.
- Why it matters: deriveaddresses makes descriptor policy visible and reproducible, but safe use requires public-only inputs where possible, bounded ranges, explicit network identity and separate address-allocation state.
- 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 deriveaddresses RPC in simple English
Bitcoin Core deriveaddresses RPC: An xpub descriptor reveals a branch and repeated derivation may link activity. Derivation alone does not reserve an address or advance wallet state, so issuance needs its own atomic index.
Simple example
A miner is checking Bitcoin Core deriveaddresses RPC. Examples include pkh, wpkh, sh(multi()) and raw scripts. Parse with the exact node version and do not infer spendability merely because an address can be rendered.
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.
Descriptor semantics
Examples include pkh, wpkh, sh(multi()) and raw scripts. Parse with the exact node version and do not infer spendability merely because an address can be rendered.
Key forms
A key may be fixed hexadecimal or xpub/xprv with path elements; h marks hardened derivation. Keep private extended keys away from general RPC and use public descriptors where possible.
Fixed and ranged
A wildcard makes a descriptor ranged. The range can be one end value or an inclusive begin-and-end pair. Reject negative, inverted, excessive or unexpectedly empty ranges.
Checksums and origins
Use getdescriptorinfo to canonicalise and add checksum, and preserve origin fingerprints and paths. A checksum detects transcription errors but does not authenticate policy.
Network identity
Version bytes and rendered addresses depend on network and script type. Bind the expected network, compare known fixtures and block mainnet output from test environments.
Privacy and address issuance
An xpub descriptor reveals a branch and repeated derivation may link activity. Derivation alone does not reserve an address or advance wallet state, so issuance needs its own atomic index.
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 deriveaddresses RPC?
Bitcoin Core deriveaddresses RPC: An xpub descriptor reveals a branch and repeated derivation may link activity.
For Bitcoin Core deriveaddresses RPC, what should a beginner know about descriptor semantics?
Examples include pkh, wpkh, sh(multi()) and raw scripts. Parse with the exact node version and do not infer spendability merely because an address can be rendered.
For Bitcoin Core deriveaddresses RPC, what should a beginner know about key forms?
A key may be fixed hexadecimal or xpub/xprv with path elements.
For Bitcoin Core deriveaddresses RPC, what should a beginner know about fixed and ranged?
A wildcard makes a descriptor ranged. The range can be one end value or an inclusive begin-and-end pair.
Conclusion
deriveaddresses makes descriptor policy visible and reproducible, but safe use requires public-only inputs where possible, bounded ranges, explicit network identity and separate address-allocation state.
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.