Skip to content

v0.7.1 — BIP30 bridge handling (METHOD_ID unchanged)

Choose a tag to compare

View all tags
@defenwycke defenwycke released this 24 Jul 23:50
v0.7.1
b439d57
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.7.1 — BIP30 bridge handling (host-side, METHOD_ID unchanged)

METHOD_ID = 36a0415d5763ed62e71c44915d36caa34ae840cfd1051587bce1de27be0dd7f5 (unchanged from v0.7.0). This is a host-side release, so v0.7.0 proofs remain valid — v0.7.1 only adds handling for the two BIP30 blocks.

What changed

  • BIP30 bridge fix (#6/#2). The archive-node bridge now emits the BIP30 duplicate-coinbase overwrite witness for blocks 91842 (dup of 91812) and 91880 (dup of 91722), so those grandfathered blocks are provable via the bridge. Without it the guest — which mandates the overwrite at those two hashes — sets all_ok=false and the prove panics, hard-stopping any full-chain run at 91842.
  • Validated end-to-end: the bridge replayed to 91842, emitted witness.bip30 = OVERWRITE(old_height=91812, dels=1), and prove-range-bridge 91842 proved + verify-any returned RANGE-OK lo=91842 hi=91842 out_tip=eccae000… (block 91842's real hash). Block 91880 uses the identical path.

Assets (both at 36a0415d)

  • hazync-host-x86_64-linux-gnu — CPU (glibc 2.39 / Ubuntu 24.04+).
  • hazync-host-x86_64-linux-gnu-cuda — CUDA (L40S / CUDA 12.6).

Verify

SHA256SUMS.txt is PGP-signed by the maintainer key (777FE81F8CC077FD3D08055E852C2B3190F5B928).

Assets 6
Loading