hazync

Explorer

The proof of Bitcoin's history as it stands right now, the work in progress, and who is doing it.

The genesis proof

…

One proof that every block from the genesis block to here is valid under Bitcoin Core's own consensus code.

Unspent coins after the last block
…
Total work, from genesis
…
Proof size
…
Last extended
…

Hash of the last block

…

Progress

Unbroken from block 1 to
…
Chain tip
…
In the genesis proof
…
Being proven now
…
Provers
…

From proven blocks to one proofEach stage is measured against the one before it

Proven…

Anchored…

The genesis proof…

Being proven now

Blocks a prover has claimed and not yet submitted a proof for.

ProverBlocksLowestOldest claim
Loading…

Recent work

The latest proofs the coordinator has checked and accepted.

What was doneProverWhen
Loading…

Provers

The eight with the most blocks proven. Each prover signs its work with its own key, and the coordinator checks every proof before it counts. Select a name to see everything that prover has done.

Top eight by blocks proven
ProverKeyVersionBlocks provenFoldsAnchors
Loading…

Check a proof yourself

In this browser, or on your own machine. Either way nothing about the check depends on us.

In this browser

The verifier from the latest Hazync release, compiled to WebAssembly. The proof is checked on this device and nothing is sent anywhere. It confirms the proof was made by the published prover program, that it starts at the genesis block, and reads out where the chain stood at its last block.

On the command line

A 1.7 MB verifier from the latest release, for Linux on x86-64. No node, no chain data, no GPU.

curl -fLO https://github.com/hazync/hazync/releases/latest/download/hazync-verify-x86_64-linux-gnu
chmod +x hazync-verify-x86_64-linux-gnu
curl -fLOJ https://hazync.org/api/spine/proof
./hazync-verify-x86_64-linux-gnu hazync-spine-1-*.hzk

A good proof prints SNARK RANGE PROOF [1..N] VERIFIED — genesis-anchored. The verifier accepts only proofs that start at genesis; a single block's proof is reported as a valid segment instead. An aarch64 build is in the same release. The program IDs every proof is checked against, and the API behind this page, are on the developers page.