Skip to content

Hazync v0.5.0 — minimal pure-Core guest

Choose a tag to compare

@defenwycke defenwycke released this 19 Jul 08:36

Hazync v0.5.0 — minimal pure-Core guest

The zkVM guest is now Bitcoin Core + the Utreexo accumulator, nothing else. The dormant k256 EC-acceleration experiment and an unreachable legacy mode — dead code that was still compiled into the guest — are gone. No alternative crypto implementation is linked in; an auditor reasons only about real Core.

Canonical METHOD_ID: c029cee4be0a0478af667b03d95112304e574beb93e23ffd97afb93d66742059 (was d1fc4065). Reproducible — docker build -f reproduce/Dockerfile . yields exactly this on any machine (verified local == CI). Soundness unchanged: regress + adversarial + BIP30 all pass on the stripped guest.

Install — no build

Linux x86-64, glibc 2.39+ (Ubuntu 24.04+). These URLs always point to the latest release:

Verify a proof (any box, no GPU):

curl -L -o host https://github.com/bitcoin-ghost/hazync/releases/latest/download/hazync-host-x86_64-linux-gnu && chmod +x host
curl https://bitcoinghost.org/hazync/api/proof/1 -o proof.bin && ./host verify-any proof.bin   # → RANGE-OK

Prove / contribute (NVIDIA GPU + CUDA 12.6): hazync-host-x86_64-linux-gnu-cuda. See CONTRIBUTING.md.

Both are the canonical guest, so proofs verify and submissions are accepted. Each ships with a .sha256.

What changed

  • Guest minimised: removed k256_ecdsa_verify + the k256/crypto-bigint deps + [patch.crates-io] entries, the HAZYNC_ECDSA_BENCH branch, ecdsa_vec.h, patches/0003, and the unreachable legacy() mode (the dispatch now fail-closes on an unknown mode). The sound guest never used any of it — ECDSA runs through the real, compiled libsecp256k1.
  • New canonical METHOD_ID c029cee4; reproduce/METHOD_ID updated, the reproducible-image-id CI job asserts it.
  • Version-less binary names — the download URL no longer changes across releases.
  • Docs (SECURITY, PROVING, ACCELERATION, HAZYNC_ARCHITECTURE) updated to reflect the removal — "it's Core, nothing else" is now literally true.

Note on the board

The board proofs are being re-proven on this minimal guest; a v0.5.0 binary verifies them to RANGE-OK.