0x2a799d9b2a79…2a799d98
Bitcoin Developer Verifies 164 Million Coins in 72 Seconds With STARK Proof
A Bitcoin developer verified 164 million unspent coins in 72 seconds using STARK proofs, a result that could reshape how new nodes bootstrap without replaying history.

Outputs
Developer l-henri verified a snapshot of 164 million unspent coins in about 72 seconds on an arm64 machine with roughly 0.5 GB of memory.
The verification read a 9.39 GB file, while a separate 1.6 MB STARK proof was verified in a web browser in about half a second.
The proof covered Bitcoin block headers from the start and unspent coin changes between blocks 935,001 and 972,500.
The experiment excluded script and signature checks and has not undergone external security review.
Bitcoin Core does not currently support the proposed proof-backed snapshot integration.
A Bitcoin developer has verified a snapshot of 164 million unspent coins in roughly 72 seconds, using a machine with about 0.5 GB of memory. The developer, who goes by l-henri, ran the check in November on an arm64 computer, confirming the snapshot matched records established by a cryptographic proof.
Nearly all of the 72 seconds went to reading the 9.39 GB file. Separately, l-henri showed that a compact 1.6 MB proof can be verified in a web browser in about half a second. The numbers point at a stubborn practical problem: running Bitcoin infrastructure takes time and computing power before a node becomes fully operational.
What does this change for node operators?
Bitcoin nodes secure the network by independently checking transactions and enforcing the protocol's rules. Traditionally, setting up a fully validating node means downloading and processing Bitcoin's entire transaction history to reconstruct the current database of spendable coins.
Bitcoin Core already offers a shortcut. A feature called assumeUTXO lets nodes start operating from a snapshot of the blockchain's transaction state. But the software keeps verifying historical transactions in the background to confirm the snapshot reflects Bitcoin's records faithfully.
L-henri's experiment proposes replacing that background work with a cryptographic proof. New nodes could accept a verified snapshot without repeating extensive historical calculations, cutting both setup time and resource requirements.
How the proof system works
The system relies on STARK proofs. These let computers verify specified calculations without repeating every step themselves. In this experiment, the proof covered Bitcoin's block headers from the genesis of the chain and tracked changes to unspent coins between blocks 935,001 and 972,500.
There are caveats, and they matter. The calculations started from an existing trusted Bitcoin Core snapshot at block 935,000, not from a rebuild of the full transaction history. The system also excluded checks of transaction scripts and signatures. That means it does not yet match the verification guarantees of a fully validating Bitcoin node, a gap any integration into Bitcoin Core would have to close.
What happens next?
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 entirely. That would be a real departure from current practice, where the software independently rechecks historical records even after loading a snapshot.
The project remains experimental. It has not undergone an external security review, and Bitcoin Core does not currently support the proposed integration.
The next step is a hard one: testing whether the proof system can deliver verification guarantees strong enough to replace historical checks without weakening the security assumptions Bitcoin nodes rely on. Until that question is answered, the 72-second result stands as a promising benchmark rather than a shipping feature.
via cryptonews.net (Source)
More from Marcus Bennett
Show full bio
Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,456 articles