Fu et al. proposed the zkCraft framework in their paper, combining deterministic localization with proof search to detect semantic inconsistencies in ZK circuits, using LLM-guided mutation templates to improve edge-case coverage and reduce solver interaction costs. Fu等人在论文中提出了zkCraft框架,结合确定性定位与证明搜索来检测ZK电路语义不一致,利用LLM引导突变模板提升边缘案例覆盖,减少求解器交互成本。
Notes
ZK circuits are tricky due to tight witness-constraint coupling, causing subtle bugs.
zkCraft uses R1CS-aware localization and proof search to catch under/over-constrained issues.
Row-Vortex polynomials encode edits; Violation IOP replaces repeated solver checks with a proof.
Why are semantic bugs in ZK circuits hard to detect with conventional testing? 为什么 ZK 电路中的语义错误很难通过普通测试发现?
In ZK circuits, witness computation is tightly coupled with constraints, so many bugs do not immediately violate constraints. Instead, they silently widen or restrict the solution space. Standard testing covers limited inputs and often misses such under- or over-constrained cases. ZK 电路中见证计算与约束系统高度耦合,很多错误不会直接导致约束不满足,而是悄然放宽或收紧可行解空间。普通测试往往只覆盖少量输入,难以触及这些隐藏的欠约束或过约束情况。
What key bottleneck does the Row-Vortex polynomial address in zkCraft? Row-Vortex 多项式在 zkCraft 中解决了什么关键瓶颈?
The Row-Vortex polynomial encodes many candidate constraint edits into a single algebraic object. This allows zkCraft to check many potential violations at once, avoiding per-edit solver calls and greatly improving search efficiency. Row-Vortex 多项式将候选约束修改统一编码,使大量潜在违规可以被一次性代数化检查。这避免了对每个候选编辑单独调用求解器的问题,显著提升了搜索阶段的效率。
How does the Violation IOP replace repeated satisfiability checks in zkCraft? Violation IOP 在 zkCraft 中如何替代多次可满足性检查?
The Violation IOP turns constraint violations into succinct algebraic proofs. A verifier checks a single proof to confirm the existence of a bug, replacing interactive and repeated satisfiability queries with one proof verification. Violation IOP 将约束违规转化为可验证的代数证明,使验证者只需检查一个简洁证明即可确认错误存在。这将交互式、反复的可满足性查询转化为一次性证明验证。