Skip to content

v0.1.2.2

Choose a tag to compare

View all tags
@djh58 djh58 released this 07 Jul 15:11
v0.1.2.2
This tag was signed with the committer’s verified signature.
djh58 Dan Hepworth
GPG key ID: 87012E62F6CC1393
Verified
Learn about vigilant mode.
dec0f25
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release date: 2026-07-07

Highlights

  • Fixed a PRISM audit verifier regression that could reject valid live-chain block candidates with invalid type: floating point ..., expected u128 when audit bundles contained testnet-scale difficulty and share-weight integers.
  • Restored legacy/full audit bundle verification and canonicalization by deserializing full bundles directly into the typed AuditBundle model instead of routing them through serde_json::Value.
  • Preserved compact body-ref and qbit.prism.audit-bundle.v2 reconstruction for external audit-body storage while enabling arbitrary-precision JSON numbers for large u128 fields.
  • Added live-scale regression coverage for qbit-prism-audit-verify and qbit-prism-audit-canonicalize across both legacy full bundles and compact body-ref bundles.
  • Verified the fix on the deployed testnet4 PRISM pool image with a synthetic live-scale audit bundle; verification now reaches the expected coinbase comparison instead of failing JSON parsing.

Operator Notes

  • This release is recommended for all PRISM operators on v0.1.2.1, especially pools using direct PRISM Stratum against public testnet or any chain where scaled difficulty values exceed u64::MAX.
  • No configuration or database migration is required.
  • Upgrade before relying on PRISM block candidate acceptance from v0.1.2.1; the previous release could accept shares but reject found block candidates before persistence or submitblock.
  • After upgrading, run make prism-self-check and monitor qbit_prism_blocks_accepted_total, qbit_prism_persisted_blocks, and coordinator logs for qbit-prism-audit-verify failed.
  • Existing public dashboard API responses, direct coinbase settlement artifacts, compact audit body refs, and CTV fanout storage remain compatible.
Assets 2
Loading