Direct answer · §03 Auditing

When should the audit happen?

Short answer

Engage early enough that findings can still change the design, and late enough that the code is stable — in practice, when the circuits and protocol are feature-complete and the specification is written, not when the launch date is three weeks away. The specification is the binding constraint: an auditor cannot tell you a circuit is underconstrained without a statement of what it was supposed to constrain. Budget separate time for a fix-review round. See Section 03.

Cite this page
MarketComp (2026). When should the audit happen?. The ZK Field Manual (Version 1.3). MarketComp. https://zkpick.com/faq/when-should-the-audit-happen/
@misc{zkfieldmanual-when-should-the-audit-happen,
  title        = {When should the audit happen? — The ZK Field Manual},
  author       = {MarketComp},
  year         = {2026},
  version      = {1.3},
  howpublished = {\url{https://zkpick.com/faq/when-should-the-audit-happen/}},
  note         = {Accessed: YYYY-MM-DD}
}