A Bitcoin developer has demonstrated a method for validating a 9.39 GB blockchain snapshot in roughly 72 seconds, a technique that could make running Bitcoin nodes faster and less demanding on hardware.
The developer, who goes by l-henri, outlined the experiment in a Nov. 13 post on Delving Bitcoin. The system relies on cryptographic proofs to confirm Bitcoin’s existing transaction records without independently processing the blockchain’s entire history.
The test used a snapshot of 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, and they form the dataset nodes consult to determine whether coins remain available to spend.
Running the check on an arm64 computer with about 0.5 GB of memory, the developer confirmed that the snapshot matched the records defined by a cryptographic proof. The process took around 72 seconds, nearly all of it consumed by reading the 9.39 GB file.
Separately, l-henri showed that a compact 1.6 MB proof could be verified in a web browser in about half a second.
The work could ease a persistent challenge in operating Bitcoin infrastructure: the time and computing power needed to validate historical blockchain activity before a node is ready to operate.
How cryptographic proofs could accelerate Bitcoin node setup
Bitcoin nodes help secure the network by independently checking transactions and enforcing its rules. Setting up a full validating node has traditionally meant downloading and processing the blockchain’s historical transactions to rebuild the current set of spendable coins.
Bitcoin Core already offers a shortcut through a feature called assumeUTXO, which lets a node begin operating from a snapshot of the blockchain’s transaction state. Even so, the software continues verifying historical transactions in the background to confirm that the snapshot accurately reflects Bitcoin’s records.
L-henri’s approach proposes replacing that background verification with a cryptographic proof. In principle, this would let new nodes accept a verified snapshot without repeating the extensive historical calculations, reducing both setup time and resource demands.
The system uses STARK proofs, which allow a computer to confirm that specific calculations were performed correctly without redoing every step. For this experiment, the proof covered Bitcoin’s block headers from the network’s origin and validated the changes to unspent coins between blocks 935,001 and 972,500.
Trusted starting snapshot and bounded replay, with scripts and signatures omittedTHE REPLAY BOUNDARYEarlier transactionsare not replayed935,000Trusted starting snapshot935,001 to 972,500Blocks replayedFinal coin setScripts and signatures omittedResearch preview; no external reviewSchematic, not a block scale
Choose the check
Choose the checkSnapshot fileBrowser proof
The author reports a 72-second check of the 9.39 GB snapshot against the proof’s commitments.
Snapshot-file check72 sReported by the project9.39 GBsnapshot fileProof commitmentsFile matchesseal commitmentsChecks base block, count, amount and hash0.5 GB memory; arm64 machineSnapshot-file check72 sReported by the project9.39 GBsnapshot fileMatch to sealFile matches seal commitmentsBase block, count, amount and hash0.5 GB memory; arm64 machine
The author reports checking the 1.6 MB proof in about half a second, separately from the snapshot-file benchmark.
Browser proof check~0.5 sReported by the project1.6 MBproofProof verifierProof statementis checkedChecks the compact proofSeparate from the snapshot-file checkBrowser proof check~0.5 sReported by the project1.6 MBproofVerify proofProof statement is checkedA different job from checking the fileBoth checks retain the trust limits above
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.
The calculations did not begin from scratch, however; they started from an existing trusted Bitcoin Core snapshot at block 935,000 rather than rebuilding the entire transaction history. The system also skipped checks of transaction scripts and signatures, so it does not yet offer the same guarantees as a fully validating Bitcoin node.
Those caveats matter as l-henri weighs integrating the technology into Bitcoin Core. In the November disclosure, the developer proposed testing a modification that would let Bitcoin Core accept proof-backed snapshots and drop its existing background validation.
Such a change would depart from Bitcoin Core’s current design, which continues to check historical records independently even after loading a snapshot.
For now, 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 will be to test whether the proof system can offer enough assurance to replace historical checks without weakening the security assumptions Bitcoin nodes rely on.
Also Read
- MAS and Bundesbank Achieve Wholesale CBDC Interoperability via Zero-Knowledge Proofs
- Coinbase Brings ChatGPT Plugin Into Bitcoin, Stock and Derivatives Trading
- Wells Fargo More Than Doubles Bitcoin ETF Stake to $2.35 Billion, Leading Institutional Holders
- XRP Slides to a 10-Year RSI Low, Reigniting the Debate Over Its Market Bottom

