Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
Bitcoin Core loadtxoutset RPC: AssumeUTXO Loading Guide
Bitcoin Core 26 loadtxoutset guide covering snapshot paths, hash validation, dual chainstates, usable-versus-validated state, pruning and monitoring.
This guide explains Bitcoin Core loadtxoutset 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 26.0 introduced loadtxoutset for loading a serialized UTXO snapshot into a second chainstate. The snapshot-backed state can synchronise rapidly to the network tip while the original chainstate validates historical blocks in the background.
- Why it matters: loadtxoutset shortens time to a usable tip without skipping eventual historical validation. Operators should expose that distinction in monitoring and keep the background chainstate intact until validation is complete.
- 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.
What this means in simple English
An RPC is a command sent to one Bitcoin Core node. It can ask that node for information or request a local action. A successful reply describes that node; it does not automatically prove what happened across the Bitcoin network.
Beginners can focus on the input, the result and the limit of that result. Operators should test the command on the exact Bitcoin Core version they run before relying on it.
Simple example
Think of the proposal as giving each transaction a limited allowance of computer work. Simple operations use a little of that allowance and expensive operations use more. If a script uses the whole allowance, validation stops.
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.
- UTXO:
- An unspent transaction output: a piece of bitcoin that can be used as an input to a later transaction.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Snapshot path
A relative path is resolved under datadir; an absolute path is used directly. Stage files in a restricted location and prevent traversal or symlink substitution.
Supported base
Core checks snapshot contents by hash against supported assumeUTXO bases. A third-party transport source need not be trusted, but the exact Core build and expected base still matter.
Returned evidence
coins_loaded, tip_hash, base_height and absolute path identify what entered the second chainstate. Preserve them with the file hash and source record.
Dual chainstates
The snapshot state advances toward the network tip while the original chainstate performs full initial block download to the snapshot base. Both consume disk and cache resources.
Usable versus validated
Services can become current quickly, but that does not mean the snapshot has been justified by full history. Require getchainstates validated true under the documented completion policy.
Pruning
With pruning, two chainstates can exceed a small budget and Core 26 notes a practical minimum interaction. Reserve storage and monitor block and chainstate directories.
Failure recovery
Do not discard the snapshot, logs or original validation data prematurely. On failure, stop cleanly, record chainstate output and follow version-specific recovery documentation. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is Bitcoin Core loadtxoutset RPC?
Bitcoin Core 26.0 introduced loadtxoutset for loading a serialized UTXO snapshot into a second chainstate. The snapshot-backed state can synchronise rapidly to the network tip while the original chainstate validates historical blocks in the background.
Is Bitcoin Core loadtxoutset RPC active or supported today?
Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Why does Bitcoin Core loadtxoutset RPC matter?
loadtxoutset shortens time to a usable tip without skipping eventual historical validation. Operators should expose that distinction in monitoring and keep the background chainstate intact until validation is complete.
Do beginners need to use the technical details?
No. The command is mainly for people who operate Bitcoin Core or software connected to it. Other readers can use the article to understand what an operator or service is measuring.
Conclusion
loadtxoutset shortens time to a usable tip without skipping eventual historical validation. Operators should expose that distinction in monitoring and keep the background chainstate intact until validation is complete.
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.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 explained in detail: its seven consensus restrictions, 55% signalling threshold, chain-split risk and August 2026 closure.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.