This guide explains Bitcoin Core importprunedfunds 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 importprunedfunds imported wallet funding history without a rescan by combining a raw transaction with a gettxoutproof Merkle proof. The corresponding address or script had to be present in the wallet already.
- Why it matters: importprunedfunds can reconstruct selected wallet history without old blocks, but it transfers completeness responsibility to the operator. Every funding proof must be followed through subsequent spends and active-chain reconciliation.
- Current position: Bitcoin Core 0.16.0 importprunedfunds imported wallet funding history without a rescan by combining a raw transaction with a gettxoutproof Merkle proof.
Bitcoin Core importprunedfunds RPC in simple English
Bitcoin Core importprunedfunds RPC: The txoutproof must include the transaction in a block. Verify proof bytes, reconstructed root, header proof of work, active-chain ancestry and suitable depth.
Simple example
A miner is checking Bitcoin Core importprunedfunds RPC. After every import, compare wallet outpoints with an independently validating node at the same tip. Reject excess size, malformed serialisation and unexpected inputs or outputs before wallet mutation.
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.
Prerequisite wallet script
Import the destination address, public key or script first and verify the wallet recognises it with correct watch-only or spendable status. The funding transaction cannot establish wallet ownership on its own.
Raw transaction validation
Decode the supplied transaction independently, recompute txid and witness identity, and verify the exact output script and satoshi value. Reject excess size, malformed serialisation and unexpected inputs or outputs before wallet mutation.
Merkle proof validation
The txoutproof must include the transaction in a block. Verify proof bytes, reconstructed root, header proof of work, active-chain ancestry and suitable depth. Inclusion in a side-chain header is not settled active-chain receipt.
Pruned-node rationale
The method avoids requiring old block data locally, but another trusted process must supply and verify the evidence. Record block hash, height, chainwork and source. Do not accept arbitrary proofs from a customer-facing endpoint.
Later-spend responsibility
The documentation explicitly assigns responsibility for importing subsequent spends or rescanning from the inclusion point. Without them, the wallet may show outputs already spent. Build a chronological chain of funding and spending transactions.
Reconciliation and backup
After every import, compare wallet outpoints with an independently validating node at the same tip. Freeze spending until later spends are accounted for, then create and restore-test a new wallet backup containing the imported history.
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 importprunedfunds RPC?
Bitcoin Core importprunedfunds RPC: The txoutproof must include the transaction in a block. Verify proof bytes, reconstructed root, header proof of work, active-chain ancestry and suitable depth.
For Bitcoin Core importprunedfunds RPC, what should a beginner know about prerequisite wallet script?
Import the destination address, public key or script first and verify the wallet recognises it with correct watch-only or spendable status.
For Bitcoin Core importprunedfunds RPC, what should a beginner know about raw transaction validation?
Decode the supplied transaction independently, recompute txid and witness identity, and verify the exact output script and satoshi value.
For Bitcoin Core importprunedfunds RPC, what should a beginner know about merkle proof validation?
The txoutproof must include the transaction in a block. Verify proof bytes, reconstructed root, header proof of work, active-chain ancestry and suitable depth.
Conclusion
importprunedfunds can reconstruct selected wallet history without old blocks, but it transfers completeness responsibility to the operator. Every funding proof must be followed through subsequent spends and active-chain reconciliation.
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.