Assumeutxo is a feature that allows fast bootstrapping of a validating bitcoind instance.
There is currently no canonical source for snapshots, but any downloaded snapshot will be checked against a hash that's been hardcoded in source code.
Once you've obtained the snapshot, you can use the RPC command loadtxoutset to
load it.
A pruned node can load a snapshot. To save space, it's possible to delete the
snapshot file as soon as loadtxoutset finishes.
The minimum -prune setting is 550 MiB, but this functionality ignores that
minimum and uses at least 1100 MiB.
As the background sync continues there will be temporarily two chainstate directories, each multiple gigabytes in size (likely growing larger than the downloaded snapshot).
Indexes work but don't take advantage of this feature. They always start building from the genesis block. Once the background validation reaches the snapshot block, indexes will continue to build all the way to the tip.
For indexes that support pruning, note that no pruning will take place between the snapshot and the tip, until the background sync has completed - after which everything is pruned. Depending on how old the snapshot is, this may temporarily use a significant amount of disk space.
The RPC command dumptxoutset can be used to generate a snapshot. This can be used
to create a snapshot on one node that you wish to load on another node.
It can also be used to verify the hardcoded snapshot hash in the source code.
The utility script
./contrib/devtools/utxo_snapshot.sh may be of use.
-
The concept of UTXO snapshots is treated as an implementation detail that lives behind the ChainstateManager interface. The external presentation of the changes required to facilitate the use of UTXO snapshots is the understanding that there are now certain regions of the chain that can be temporarily assumed to be valid. In certain cases, e.g. wallet rescanning, this is very similar to dealing with a pruned chain.
Logic outside ChainstateManager should try not to know about snapshots, instead preferring to work in terms of more general states like assumed-valid.
Chainstate within the system goes through a number of phases when UTXO snapshots are
used, as managed by ChainstateManager. At various points there can be multiple
Chainstate objects in existence to facilitate both maintaining the network tip and
performing historical validation of the assumed-valid chain.
It is worth noting that though there are multiple separate chainstates, those
chainstates share use of a common block index (i.e. they hold the same BlockManager
reference).
The subheadings below outline the phases and the corresponding changes to chainstate data.
ChainstateManager manages a single Chainstate object, for which
m_snapshot_blockhash is null. This chainstate is (maybe obviously)
considered active. This is the "traditional" mode of operation for bitcoind.
| number of chainstates | 1 |
| active chainstate | ibd |
ChainstateManager initializes a new chainstate (see ActivateSnapshot()) to load the
snapshot contents into. During snapshot load and validation (see
PopulateAndValidateSnapshot()), the new chainstate is not considered active and the
original chainstate remains in use as active.
| number of chainstates | 2 |
| active chainstate | ibd |
Once the snapshot chainstate is loaded and validated, it is promoted to active
chainstate and a sync to tip begins. A new chainstate directory is created in the
datadir for the snapshot chainstate called chainstate_snapshot.
When this directory is present in the datadir, the snapshot chainstate will be detected
and loaded as active on node startup (via DetectSnapshotChainstate()).
A special file is created within that directory, base_blockhash, which contains the
serialized uint256 of the base block of the snapshot. This is used to reinitialize
the snapshot chainstate on subsequent inits. Otherwise, the directory is a normal
leveldb database.
| number of chainstates | 2 |
| active chainstate | snapshot |
The snapshot begins to sync to tip from its base block, technically in parallel with
the original chainstate, but it is given priority during block download and is
allocated most of the cache (see MaybeRebalanceCaches() and usages) as our chief
goal is getting to network tip.
Failure consideration: if shutdown happens at any point during this phase, both chainstates will be detected during the next init and the process will resume.
Once the snapshot chainstate leaves IBD, caches are rebalanced
(via MaybeRebalanceCaches() in ActivateBestChain()) and more cache is given
to the background chainstate, which is responsible for doing full validation of the
assumed-valid parts of the chain.
Note: at this point, ValidationInterface callbacks will be coming in from both chainstates. Considerations here must be made for indexing, which may no longer be happening sequentially.
Once the tip of the background chainstate hits the base block of the snapshot
chainstate, we stop use of the background chainstate by setting m_disabled, in
MaybeCompleteSnapshotValidation(), which is checked in ActivateBestChain()). We hash the
background chainstate's UTXO set contents and ensure it matches the compiled value in
CMainParams::m_assumeutxo_data.
| number of chainstates | 2 (ibd has m_disabled=true) |
| active chainstate | snapshot |
The background chainstate data lingers on disk until the program is restarted.
After a shutdown and subsequent restart, LoadChainstate() cleans up the background
chainstate with ValidatedSnapshotCleanup(), which renames the chainstate_snapshot
datadir as chainstate and removes the now unnecessary background chainstate data.
| number of chainstates | 1 |
| active chainstate | ibd (was snapshot, but is now fully validated) |
What began as the snapshot chainstate is now indistinguishable from a chainstate that has been built from the traditional IBD process, and will be initialized as such.
A file will be left in chainstate/base_blockhash, which indicates that the
chainstate, even though now fully validated, was originally started from a snapshot
with the corresponding base blockhash.