A Bitcoin developer has shown how to verify a 9.39 GB blockchain snapshot in just 72 seconds, potentially making it easier and faster to run Bitcoin nodes.
The developer, identified as l-henri, disclosed the experiment in a Nov. 13 Delving Bitcoin post, describing a system that uses cryptographic proofs to check Bitcoin’s existing transaction records without independently processing its entire history.
The experiment involved a snapshot containing approximately 164.5 million unspent transaction outputs (UTXOs) at Bitcoin block 972,500. These outputs represent Bitcoin that has been received but not yet spent, forming the database nodes use to determine whether coins remain available for transactions.
Using an arm64 computer with approximately 0.5 GB of memory, the developer checked that the snapshot matched the records established by a cryptographic proof.
The process took approximately 72 seconds, with nearly all that time spent reading the 9.39 GB file. Separately, the developer demonstrated that a compact 1.6 MB proof could be verified in a web browser in about half a second.
The achievement could help address a practical challenge of running Bitcoin infrastructure: the time and computing resources required to verify historical blockchain activity before a node becomes fully operational.
How cryptographic proofs could speed up Bitcoin node setup
Bitcoin nodes help secure the network by independently checking transactions and enforcing its rules.
Traditionally, setting up a fully validating node involves downloading and processing BTC’s historical transactions to reconstruct the current database of spendable coins.
Bitcoin Core already offers a shortcut through a feature called assumeUTXO, which lets nodes start operating using a snapshot of the blockchain’s transaction state. However, the software continues verifying historical transactions in the background to confirm that the snapshot accurately reflects Bitcoin’s records.
L-henri’s experiment proposes replacing that additional verification work with a cryptographic proof. This approach could let new nodes accept a verified snapshot without repeating extensive historical calculations, potentially reducing setup time and resource requirements.
The developer’s system uses STARK proofs, which allow computers to verify specified calculations without repeating every step themselves. In this experiment, the proof covered BTC’s block headers from its beginning and checked changes to unspent coins between blocks 935,001 and 972,500.
Choose the check
The author reports a 72-second check of the 9.39 GB snapshot against the proof’s commitments.
The author reports checking the 1.6 MB proof in about half a second, separately from the snapshot-file benchmark.
Checking the file against a proof retains the trusted starting snapshot and the omission of scripts and signatures.
Benchmarks are author-reported and have not been independently reproduced here. The replay starts from Core’s trusted snapshot at block 935,000, omits scripts and signatures, and has no external review. Neither measurement establishes total node setup time.
However, the calculations started from an existing trusted Bitcoin Core snapshot at block 935,000 rather than rebuilding the entire transaction history. The system also excluded checks of transaction scripts and signatures, meaning it does not yet provide the same verification guarantees as a fully validating BTC node.
These limitations remain important as the developer considers integrating the technology into Bitcoin Core.
In the November disclosure, l-henri proposed testing a modification that would let Bitcoin Core accept proof-backed snapshots and skip its existing background validation process.
That would mark a departure from Bitcoin Core’s current approach, which independently checks historical records even after loading a snapshot.
The project remains experimental and has not undergone an external security review. Bitcoin Core also does not currently support the proposed integration.
The next step is to test whether the proof system can provide sufficient verification guarantees to replace historical checks without weakening the security assumptions BTC nodes rely on.
