Devcon Archive logo
Devcon Devconnect Forum Blog
  • Watch
  • Event
    Event: background logo
    • Devcon 7
    • Devcon 6
    • Devcon 5
    • Devcon 4
    • Devcon 3
    • Devcon 2
    • Devcon 1
    • Devcon 0
    • Devconnect ARG
  • Categories
    Categories: background logo
    • Cryptoeconomics
    • Devcon
    • Developer Experience
    • Coordination
    • Core Protocol
    • Layer 2s
    • Real World Ethereum
    • Cypherpunk & Privacy
    • Security
    • Applied Cryptography
    • Usability
  • Playlists

Suggested

Loading results..

View all

About Devcon —

Devcon is the Ethereum conference for developers, researchers, thinkers, and makers.

An intensive introduction for new Ethereum explorers, a global family reunion for those already a part of our ecosystem, and a source of energy and creativity for all.

  • Watch
  • Devcon
  • Devconnect
  • Forum
  • Blog

Get in touch

devcon@ethereum.org

Subscribe to our newsletter

Crafted with passion ❤️ at the Ethereum Foundation

© 2026 — Ethereum Foundation. All Rights Reserved.

devcon8 / dont review the code formal specs ai synthesis and why the verifier is the only thing you trust

  • YouTube
Don't Review the Code: Formal Specs, AI Synthesis, and Why the Verifier Is the Only Thing You Trust preview
  • Details

Don't Review the Code: Formal Specs, AI Synthesis, and Why the Verifier Is the Only Thing You Trust

Duration: NaN:NaN:NaN

Speaker: Dorde Mijovic

Type: Talk

Expertise: Some familiarity with the topic

Event: Devcon

Date: Nov 2026

AI can now produce a plausible implementation of almost anything. That moves the bottleneck from writing code to knowing whether it's right, and the answer isn't more code review — it's making the specification the artifact humans own, and reducing the trusted component to a single deterministic checker. I'll walk through a working pipeline: high-level behavioural specs in Act, AI-generated Yul, and machine-checked refinement between the two. The running example is a fully onchain orderbook, where designing for verifiability changed the architecture itself — custody that proves solvency without trusting its callers, and units chosen so that no division exists anywhere in the protocol. I'll also cover what doesn't work yet: storage-layout abstraction, matching loops, and the uncomfortable fact that a specification can prove instantly because it says nothing at all.

Categories

EVMAISecurityFormal Verification