Bitcoin developer verifies 164 million unspent coins in just 72 seconds

By: cryptoslate.com|11/17/2026 20:00:40

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.

A fast check with a trusted starting point

The experiment replays a bounded range from a trusted snapshot. Its two reported timing figures measure different checks.
Transaction replay starts from a trusted snapshot at block 935000 and ends at 972500 THE REPLAY BOUNDARYEarlier history935,000Trusted snapshot935,001 to 972,500Blocks replayedTransactionsnot replayedTrust enters hereFinal coin setScripts and signatures omittedResearch preview; no external reviewSchematic, not a block scale
Trusted starting snapshot and bounded replay, with scripts and signatures omitted THE 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 check 72 sReported by the project9.39 GBsnapshot fileProof commitmentsFile matchesseal commitmentsChecks base block, count, amount and hash0.5 GB memory; arm64 machine
Snapshot-file check 72 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 check
Browser 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.
Sources and evidence

Sources

  1. l-henri's experiment report
  2. Proven Bitcoin project demo

Supporting facts

  • Reported statement In a November 13 Delving Bitcoin post, developer l-henri reported that chainproof verify-snapshot checked a 9.39 GB Bitcoin Core snapshot at block 972,500 containing 164,539,066 coins in 72 seconds, using 0.5 GB memory on an arm64 machine. [1]
  • Reported statement l-henri says verify-snapshot checks a Core dumptxoutset file's base block, coin count, total amount and hash_serialized against the proof's seal. [1]
  • Reported statement The author separately reports that a browser verifies the 1.6 MB proof in about half a second, a different operation from the reported 72-second snapshot-file check. [1] [2]
  • Reported statement According to the report, the demonstration replays blocks 935,001 through 972,500 from a trusted Core assumeUTXO snapshot at block 935,000; it does not replay the earlier blocks' transactions. [1] [2]
  • Reported statement The project explicitly excludes script and signature checks, despite checking block data, structural rules, amounts and coin-set changes over its replay range of blocks 935,001 through 972,500. [1] [2]
  • Reported statement The developer report and demonstration page state that the system has not received external review, and the page labels it a research preview that is not ready for production. [1] [2]

Method

Source-bound process diagrams from the project's reported measurements and limitations. The replay path is schematic, not proportional to block count or time. Panel selection compares two different verification jobs; it is not a speedup calculation.

Scope

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.
Infographic by CryptoSlate

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.

-- Price

--
--
--

This content is provided for general informational purposes only and doesn't constitute financial, investment, legal, or tax advice. Any events, rewards, online promotions, or related information mentioned herein should not be considered a recommendation, solicitation, or invitation to purchase, sell, trade, or otherwise deal in any crypto assets. Crypto assets are highly volatile and may result in loss. The availability of WEEX services, products, and related events may vary by region. You are responsible for ensuring that your participation is in accordance with applicable local laws and regulations.

You may also like

iconiconiconiconiconiconiconiconicon
Customer Support:@weikecs
Business Cooperation:@weikecs
Quant Trading & MM:bd@weex.com
VIP Program:support@weex.com