This guide explains Bitcoin Core AssumeUTXO in plain English. It focuses on what the subject is, why it matters and what a beginner should remember.
TL;DR
- What it is: Bitcoin Core 28.0 made AssumeUTXO practical on mainnet by adding parameters for a snapshot at block height 840,000. Loadtxoutset can activate an authenticated UTXO snapshot so the node reaches the current tip quickly while its original chainstate validates historical blocks in the background. The acceleration changes when the node becomes usable, not the requirement to complete full validation.
- Why it matters: AssumeUTXO can shorten a node’s path to a usable mainnet tip without replacing historical verification. Reliable operations keep that distinction visible and require the background chainstate to finish before declaring full validation 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.
Bitcoin Core AssumeUTXO in simple English
Bitcoin Core AssumeUTXO: The snapshot base must match a compiled AssumeUTXO parameter, including the height-840000 mainnet commitment. Version and network must be recorded together.
Simple example
A node operator is checking Bitcoin Core AssumeUTXO. Core verifies the snapshot content against its expected hash, so the download host need not be trusted for correctness.
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.
Supported base
The snapshot base must match a compiled AssumeUTXO parameter, including the height-840000 mainnet commitment. Version and network must be recorded together.
Transport trust
Core verifies the snapshot content against its expected hash, so the download host need not be trusted for correctness. Operators should still hash files and control storage paths.
New dump format
Core 28 changed dumptxoutset and loadtxoutset formats; snapshots from the older format cannot be loaded. Generate and consume with compatible releases.
Dual chainstates
The snapshot-backed chainstate advances to tip while the original chainstate validates from genesis to the snapshot base. Monitor both with getchainstates.
Usable versus validated
A current snapshot chainstate can support services before the background chainstate reports validated. Expose that distinction in readiness and audit evidence.
Resources
Two chainstates require disk, database cache and I/O. Plan pruning and storage headroom, and avoid deleting source data or logs before validation finishes.
Recovery
Retain snapshot identity, source, hash and returned load details. On failure stop cleanly, capture getchainstates and logs and revert through the documented version-specific process. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is the main point of Bitcoin Core AssumeUTXO?
Bitcoin Core AssumeUTXO: The snapshot base must match a compiled AssumeUTXO parameter, including the height-840000 mainnet commitment.
For Bitcoin Core AssumeUTXO, what should a beginner know about supported base?
The snapshot base must match a compiled AssumeUTXO parameter, including the height-840000 mainnet commitment.
For Bitcoin Core AssumeUTXO, what should a beginner know about transport trust?
Core verifies the snapshot content against its expected hash, so the download host need not be trusted for correctness.
For Bitcoin Core AssumeUTXO, what should a beginner know about new dump format?
Core 28 changed dumptxoutset and loadtxoutset formats. Snapshots from the older format cannot be loaded.
Conclusion
AssumeUTXO can shorten a node’s path to a usable mainnet tip without replacing historical verification. Reliable operations keep that distinction visible and require the background chainstate to finish before declaring full validation 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.
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.