BTC $62,060.00 ▼ 1.69% ETH $1,753.38 ▼ 1.60% BNB $578.04 ▼ 0.94% XRP $0.9603 ▼ 0.75% SOL $72.86 ▼ 1.07% TRX $0.3102 ▼ 0.11% FIGR_HELOC $1.02 ▼ 0.63% HYPE $66.49 ▼ 0.86% ZEC $888.81 ▼ 3.00% XMR $500.55 ▼ 1.19% DOGE $0.0580 ▼ 1.58% LEO $9.21 ▼ 1.12% WBT $60.19 ▼ 1.59% LINK $9.00 ▼ 1.21%
12 Extreme Fear

Preventing Underconstrained Circuit Bugs: Devcon Workshop

Original title: Training for Constraining: How to Prevent Circuit-Level Bugs

Ethereum Foundation 53:46 0 views on YouTube ZEC −3.0% ZK −3.4% ETH −1.6%

Watch on YouTube Play loads the privacy-enhanced YouTube player. The link opens YouTube in a new tab.

Summary

An Ethereum Foundation Devcon security workshop with Levi Katyal Sledd and Vijay Singh covers how to prevent circuit-level bugs in SNARK-based systems. The description states that at least four significant underconstrained-circuit bugs surfaced in 2026: a missing Halo2 copy constraint in Zcash's Orchard pool, a pairing check bug in OpenVM, Scroll's ecPairing precompile, and three criticals in ZKsync Airbender caught by formal verification. Unit testing is described as insufficient to catch underconstrained circuits, because true witnesses always pass verification. The workshop introduces arithmetic circuits and how they are used in modern SNARK-based systems, then discusses real examples of underconstrained circuits and what a false proof means in context. Participants see an example of an underconstrained circuit and how to identify it by inspection. The session also demonstrates on an example circuit how fuzzing and formal verification can find a missing constraint, and discusses how AI tools may assist in the search for circuit-level vulnerabilities.

This AI summary uses the title, description and tags. It may miss context from the full video. How summaries are checked

Key points

  1. The description says at least four significant underconstrained-circuit bugs surfaced in 2026.
  2. Named examples include a missing Halo2 copy constraint in Zcash's Orchard pool and a pairing check bug in OpenVM.
  3. Further examples are Scroll's ecPairing precompile and three criticals in ZKsync Airbender found by formal verification.
  4. Unit testing is called insufficient for underconstrained circuits because true witnesses always pass verification.
  5. The workshop demonstrates fuzzing and formal verification finding a missing constraint in an example circuit, and covers how AI tools may assist the search.

Questions

Who leads the workshop and on which track?
Levi Katyal Sledd and Vijay Singh lead the session, listed on the Security track.
Why does the source say unit testing is not enough?
Because true witnesses always pass verification, so unit testing cannot catch an underconstrained circuit.

Related briefs

A video appearing here is not an endorsement. Crypto assets can lose value. This page provides information, not investment advice.