Making sense of crypto.
NBTCNEWS

Bitcoin developer verifies 164 million unspent coins in 72 seconds

A Bitcoin developer reports that a STARK proof verified a 9.39 GB snapshot of about 164.5 million unspent outputs in 72 seconds on a low-memory computer, suggesting proof-backed snapshots could make node setup faster and less resource-intensive. The experiment relied on a trusted earlier snapshot and omitted script and signature checks, so it does not match full-node verification; the project remains experimental, unaudited, and unsupported by Bitcoin Core.

By NBTC3 min read
Bitcoin developer verifies 164 million unspent coins in 72 seconds

A Bitcoin developer has demonstrated how a 9.39 GB blockchain snapshot can be verified in 72 seconds, potentially making it easier and faster to run Bitcoin nodes.

The developer, identified as l-henri, described the experiment in a Nov. 13 post on Delving Bitcoin. The system uses cryptographic proofs to check Bitcoin's existing transaction records without independently processing the full history.

The experiment used 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 spent, and form the database nodes use to determine whether coins are available for transactions.

Using an arm64 computer with approximately 0.5 GB of memory, the developer checked that the snapshot matched records established by a cryptographic proof.

The process took approximately 72 seconds, nearly all of which was spent reading the 9.39 GB file. In a separate demonstration, the developer verified a compact 1.6 MB proof in a web browser in about half a second.

The achievement could help address a practical challenge in running Bitcoin infrastructure: the time and computing resources needed to verify historical blockchain activity before a node is 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 requires downloading and processing $BTC's historical transactions to reconstruct the current database of spendable coins.

Bitcoin Core already provides a shortcut called assumeUTXO, which lets nodes begin operating from a snapshot of the blockchain's transaction state. However, the software continues to verify 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 allow new nodes to accept a verified snapshot without repeating extensive historical calculations, potentially reducing setup time and resource needs.

The developer's system uses STARK proofs, which let computers verify specified calculations without repeating every step. In this experiment, the proof covered $BTC's block headers from the beginning and checked changes to unspent coins between blocks 935,001 and 972,500.

However, the calculations began with an existing trusted Bitcoin Core snapshot at block 935,000, rather than rebuilding the full transaction history. The system also omitted checks of transaction scripts and signatures, so it does not yet offer 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 allow Bitcoin Core to accept proof-backed snapshots and skip its existing background validation.

This would differ from Bitcoin Core's current approach, which independently checks historical records even after loading a snapshot.

The project is experimental and has not received an external security review. Bitcoin Core does not currently support the proposed integration.

The next step is to test whether the proof system can provide enough verification guarantees to replace historical checks without weakening the security assumptions $BTC nodes rely on.

share preview

Sharing is disabled in this private preview. Nothing has been sent.

Sources