← → Print all
03 — Auditing · Assurance guide

Cryptographic review of the protocol and proof system

Cryptography review

In one paragraph

Cryptographic review of the protocol and proof system: Cryptography review. Layer: Proof system. Characteristic finds: Weak Fiat–Shamir, unsound composition and recursion boundaries, wrong concrete security parameters. Blind to: Implementation defects in the circuit above it; deployment and integration issues. Coverage claim: None — argument-based. Cost profile: High; cryptographers, not circuit engineers. Choose it when: Mandatory if you implement, modify or newly compose a proof system, add recursion or aggregation, change the transcript, or pick non-standard parameters. Reducible — not eliminable — if you use a mainstream library unmodified at a pinned, audited version.

By MarketComp Updated v1.3 About the authors Changelog
Layer
Proof system
Characteristic finds
Weak Fiat–Shamir, unsound composition and recursion boundaries, wrong concrete security parameters
Blind to
Implementation defects in the circuit above it; deployment and integration issues
Coverage claim
None — argument-based
Cost profile
High; cryptographers, not circuit engineers
Assurance matrix · see the row in context

What it is

Review of the argument system itself and everything below the arithmetisation: the soundness argument and its assumptions, what the Fiat–Shamir transcript absorbs, commitment instantiation, hash and sponge parameterisation, curve and subgroup structure, recursion composition, and the concrete bit-security the chosen parameters actually imply. This layer produces the highest-impact failures because they are construction-wide rather than deployment-specific.

Strengths and tradeoffs

Strengths
  • The only layer that can catch construction-level soundness breaks
  • Findings are reusable across the ecosystem and often warrant CVEs and coordinated disclosure
  • Supported by shared artefacts: the ZKProof Community Reference, ZKDocs, soundness calculators
Tradeoffs
  • Requires cryptographers rather than circuit engineers — a different and scarcer skill set
  • Hardest layer to scope and schedule; results are not predictable per reviewer-week
  • Frequently skipped because the upstream library is assumed 'already audited' — which is how weak Fiat–Shamir spread across many implementations
  • Concrete-security arguments for newer hash-based systems still rest on unproven assumptions

Choose it whenMandatory if you implement, modify or newly compose a proof system, add recursion or aggregation, change the transcript, or pick non-standard parameters. Reducible — not eliminable — if you use a mainstream library unmodified at a pinned, audited version.

Maintained implementations

Not recorded for this entry.

Maturity: Established discipline · License: Service · eprint.iacr.org ↗

How to decide
Other assurance guides in §03
ZK security consultanciesManual circuit and constraint reviewAutomated underconstraint detectionFormal verification of ZK circuitsDifferential and fuzz testingVerifier and integration reviewAudit contestsBug bountiesLLM-assisted review

Sources cited on this page · 3

  1. zkSecurity — ZK security audits and cryptographic engineeringprovider
  2. Veridise — security proofs for cryptographic protocolsprovider
  3. Weak Fiat–Shamir Attacks on Modern Proof Systems (Dao, Miller, Wright, Grubbs)paper

All 48 sources for §03 are listed on the section page →

Cite this page 
MarketComp (2026). Cryptographic review of the protocol and proof system. The ZK Field Manual (Version 1.3). MarketComp. https://zkpick.com/audit/cryptographic-review/
@misc{zkfieldmanual-cryptographic-review-of-the-protocol-and,
  title        = {Cryptographic review of the protocol and proof system — The ZK Field Manual},
  author       = {MarketComp},
  year         = {2026},
  version      = {1.3},
  howpublished = {\url{https://zkpick.com/audit/cryptographic-review/}},
  note         = {Accessed: YYYY-MM-DD}
}