zava

On-chain ZK evidence · Stellar Protocol 26

Proof Log

Every UltraHonk verification performed by any of Zava's fivehonk_verifiercontracts, streamed live from Stellar testnet. Real cryptographic checks, not byte-length stubs: valid proofs pass, tampered proofs are rejected — visible to anyone with an RPC connection.

Verifications shown

0

Last ~24 h of Soroban RPC event history.

Accepted (completeness)

0

Real bb prove output verified on chain.

Rejected (soundness)

0

Tampered / malformed proofs correctly refused.

Recent honk-verified events

Emitted by every honk_verifiercontract as(symbol "honk", symbol "verified", bool)after real UltraHonk Sumcheck + Shplemini checks. Newest first.

How to read this page

  • verified true means the on-chain verifier ran full Sumcheck + Shplemini and the proof passed. It was generated by a real prover (browser @aztec/bb.js@0.87.0 or CLI bb 0.87.0) against a real Noir circuit.
  • verified falsemeans the same verifier ran, but the proof failed cryptographic checks. Byte-length was fine — the math wasn't. This is what soundness looks like.
  • Verification runs on Stellar Protocol 26's native BN254 host functions (CAP-74, live May 2026). No off-chain trust, no rollup, no bridge.