The method works. What stands between it and a proof of the whole chain is compute, independent review, and software that puts proofs to use.
Partner
The first node to sync from a Hazync proof.
Bitcoin Ghost's node, ghostd, is building initial block download from a Hazync proof: load the proven set of unspent coins and carry on from the proven height, instead of downloading and re-checking the history.
It has already done this on mainnet at low height. ghostd adopted a proof, skipped re-checking the blocks it covered, and ended with a set of coins identical to full validation. Bitcoin Ghost hosted hazync.org until it moved to its own server in September 2026, and still relays the proof party coordinator's API at bitcoinghost.org/hazync.
These are the organisations whose help would change what is possible next.
GPU clouds, data centres, and miners with idle cards.
Two jobs need sustained GPU time: proving the history from genesis, and a small committed cluster that proves each new block as it is mined. Both split into independent pieces, so capacity in any region and any quantity is useful.
Sponsored work is credited on the public board block by block, and runs on your hardware are published as measured benchmarks, with the method alongside the number.
Firms and researchers who audit consensus and cryptographic code.
Hazync has had self-review and AI-assisted outside review, but no commissioned audit. The scope is ready: the Utreexo accumulator first, then the bridge that prepares each block's inputs, the node adoption code, and the coordinator under a hostile model.
The review guide sets out each target and why it matters.
Anyone who wants a node to trust less and sync faster.
A Hazync proof can stand in for the assumevalid hash, replacing a chosen checkpoint
with a proven one. The verifier is available as a standalone program, a C library and a
WebAssembly module, so it can be embedded without reimplementing the anchoring rules.
ghostd has shown this works on mainnet at low height. Doing it at scale, and in more node software, is the work ahead.
Proof system builders, GPU prover engineers, and academics.
Hazync is a large, real workload: Bitcoin Core's C++ consensus code running in a RISC-V zkVM with only narrow, reviewed changes, on blocks with thousands of inputs. It exercises the prover, recursion and GPU kernels in ways toy benchmarks do not, and fixes found here are written up for upstream.
For partnerships, write to defenwycke@hazync.org
For technical questions, open an issue or join the discussion on Delving Bitcoin.
Open-source work Hazync depends on. Listed as credit, not endorsement.
ZeroSync charted this ground first, by rewriting the rules. Its work is the reason this project knew where the hard part was.