Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£870.20
EST. MONTHLY
203
DAYS
EST. ROI
This guide explains Bitcoin Core importmulti 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 importmulti accepted a batch of scriptPubKeys with required timestamps and optional redeem scripts, public or private keys, internal, watch-only and label flags. It performed one rescan for the batch unless disabled and returned one success or error result per request.
- Why it matters: importmulti makes historical wallet migration efficient but not atomic. Correctness depends on timestamps, per-item flags, partial-result reconciliation, one controlled rescan and a verified new backup.
- Current position: Bitcoin Core 0.16.0 importmulti accepted a batch of scriptPubKeys with required timestamps and optional redeem scripts, public or private keys, internal, watch-only and label flags.
Bitcoin Core importmulti RPC in simple English
Bitcoin Core importmulti RPC: Each object requires a scriptPubKey as hex or address object. Canonicalise and deduplicate destinations before import. Bind each request to a non-secret recovery inventory so the per-item response can be reconciled deterministically.
Simple example
A miner is checking Bitcoin Core importmulti RPC. Use the real earliest creation time when known. Zero scans the full chain and now bypasses historical scanning for never-used material.
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.
Request identity
Each object requires a scriptPubKey as hex or address object. Canonicalise and deduplicate destinations before import. Bind each request to a non-secret recovery inventory so the per-item response can be reconciled deterministically.
Timestamp contract
Use the real earliest creation time when known; zero scans the full chain and now bypasses historical scanning for never-used material. The batch scans from two hours before the earliest timestamp. Over-late timestamps silently miss history, while zero can be expensive.
Scripts and keys
redeemscript is allowed for P2SH; pubkeys and keys must occur in the output or redeem script. Private keys change custody and require a stricter secret-handling path. Never mix production private material into a watch-only batch by convenience.
Internal and watch-only
internal marks matching outputs as non-incoming and prevents labels; watchonly is allowed only with no private keys. Set these deliberately. Incorrect flags can misclassify change, payments or spendability even if the import technically succeeds.
One-shot rescan
The batch’s main advantage is one rescan after all imports. During it, related transactions can remain missing. Disable rescan only with documented historical evidence and a scheduled alternative scan. Gate balances and withdrawals until completion.
Partial result handling
The response array matches request size and each entry can succeed or fail independently. Treat the operation as partially committed, reconcile every index and retry only failed idempotent records. Do not rerun the whole batch blindly.
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 importmulti RPC?
Bitcoin Core importmulti RPC: Each object requires a scriptPubKey as hex or address object. Canonicalise and deduplicate destinations before import.
For Bitcoin Core importmulti RPC, what should a beginner know about request identity?
Each object requires a scriptPubKey as hex or address object. Canonicalise and deduplicate destinations before import.
For Bitcoin Core importmulti RPC, what should a beginner know about timestamp contract?
Use the real earliest creation time when known. Zero scans the full chain and now bypasses historical scanning for never-used material.
For Bitcoin Core importmulti RPC, what should a beginner know about scripts and keys?
redeemscript is allowed for P2SH. Pubkeys and keys must occur in the output or redeem script.
Conclusion
importmulti makes historical wallet migration efficient but not atomic. Correctness depends on timestamps, per-item flags, partial-result reconciliation, one controlled rescan and a verified new backup.
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.