Notes from the Ethereum Basis’s Protocol Safety crew on working coordinated AI brokers towards actual protocol code, together with how we set up the work, what holds up beneath scrutiny, and what consumer groups and safety researchers can take from it. This put up stands by itself; later posts will go deeper on particular person purchasers.
What we have been working, and what stunned us
On the Ethereum Basis’s Protocol Safety crew, we have been working coordinated AI brokers towards the sorts of programs the community relies on, like programs software program, cryptographic code, and contracts that need to be proper. The brokers discovered actual bugs. One is now public: a remotely-triggerable panic in libp2p’s gossipsub, a core a part of the peer-to-peer layer Ethereum consensus purchasers run on, mounted and disclosed as CVE-2026-34219 with credit score to the crew.
Brokers discovering bugs wasn’t the shock. The shock was how little of the work went into discovering them, and the way a lot went into telling the actual bugs from those that simply appeared actual.
This put up is for consumer groups and safety researchers who need to do the identical factor. It covers how we set up the brokers, the bar a candidate has to clear earlier than it counts as a discovering, and the habits that preserve the outcomes reliable.
Groups elsewhere are converging on the identical recipe. Anthropic’s Frontier Purple Staff constructed an agent that writes property-based checks and located actual bugs throughout the Python ecosystem. Cloudflare ran a frontier mannequin via a security-research harness towards their very own programs. Everybody lands on the identical loop: level a succesful mannequin at a codebase, let it search, and triage what comes again. So the actual query is how to do that with out drowning in confident-sounding noise.
One caveat up entrance: tooling for agent-driven audits strikes quick, and any particular setup is old-fashioned in a couple of weeks. So this put up is intentionally concerning the strategies, that are persistent, quite than the tooling. Disclosure is its personal matter and can most likely be its personal put up.
An agent pointed at a codebase is a search instrument, rather a lot like a fuzzer. The distinction is what comes again. A fuzzer palms you a crash and a stack hint. An agent palms you much more, together with a write-up (name chain, impression declare, advised severity) and the artifacts to again it, like a proof-of-concept you’ll be able to run towards the actual code.
All of that makes the outcome straightforward to learn and straightforward to belief, the working proof-of-concept most of all. So do not depend what number of candidates an agent produces. Rely what number of become actual.
How the work is organized
We run many brokers in parallel towards one goal. They coordinate via the repository itself, with shared state in model management and no central course of handing out work. An agent writes down a declare the place the others can see it, does the work, and commits.
We received this strategy from Anthropic’s writeup on constructing a C compiler with a fleet of brokers, which coordinates the identical means. There isn’t any central coordinator to construct or preserve, and fewer that may go incorrect.
The roles are generated by the work that is found:
Recon turns an assault floor into concrete, testable hypotheses. Not “audit the decoder” however “this discipline is trusted previous this level; this is the property it ought to preserve, the way in which it’d break, and the proof that might settle it.”Searching takes one speculation, traces the code path, and tries to construct a reproducer.Hole-filling seems to be at what was accepted and what was rejected, writes the subsequent batch of hypotheses, and tracks protection so the brokers do not preserve going over the identical floor.Validation re-checks every candidate independently, removes duplicates, and decides.
We did not invent this pipeline. Cloudflare describes the identical levels, recon, parallel searching, unbiased validation, deduplication, reporting, and their writeup helped form ours.
This is what a candidate seems to be like earlier than it counts as a discovering:
invariant: the property that should maintain
mechanism: the precise means it may be made to break
success: observable proof: a panic, a stall, an accepted-invalid enter
reproducer: a self-contained artifact that runs towards the actual code
dedup: a key, so two brokers do not chase the identical factor
The schema is there for a motive. It forces a particular, testable declare and a transparent definition of completed. An agent that has to jot down down an observable proof cannot fall again on “this seems to be dangerous.”
Reproducible or it did not occur
One rule issues greater than every other. A candidate is not a discovering till there is a self-contained artifact that reproduces the failure towards the actual code, and that runs for somebody who did not write it.
The reproducer would not learn the write-up, and it would not care how assured the mannequin sounded. It both runs or it would not.
Most of its worth is within the false positives it catches. Three of them come up time and again, and each is the agent getting a cross for the incorrect motive:
A panic that solely occurs in a debug construct. Compile and run it the way in which the software program really ships, and the worth simply wraps round. Nothing crashes. It seems to be like a crash, however it is not one.A reproducer that builds some inner worth by hand, one no actual enter may ever produce, as a result of each path an attacker controls rejects it earlier. The bug solely “reproduces” towards a operate that nothing reachable calls that means.In formal-verification work, a proof that goes via however doesn’t suggest what you needed. The assertion is trivially true no matter what the code does, or it is weaker than the property you meant to seize. The verifier is glad, however the theorem would not constrain the habits you really cared about.
None of that is new. It is the identical factor as a check that passes as a result of it would not really verify something. What’s new is the quantity. An agent writes the ineffective model as quick as the actual one, and simply as confidently. So the verify must be computerized. You possibly can’t depend on the agent to catch itself.
Sign-to-noise is many of the work
Most candidates are incorrect, duplicate, or out of scope. That is not an issue with the strategy; that is the way it works. The aim is to reject the incorrect ones quick and again the actual ones with proof that is laborious to argue with.
Each candidate that survives will get two unbiased checks. Can an actual attacker really attain it in a standard configuration? And what does it value the attacker to drag off, in comparison with what it prices the community if it really works? A bug that any single peer can set off could be very completely different from one which wants particular entry or an enormous quantity of assets.
Every thing will get checked towards a working listing of what is already recognized, mounted, or rejected. With out that, the brokers preserve rediscovering the identical closed problem and reporting it time and again.
Acceptance charges fluctuate rather a lot from goal to focus on, and that variation is beneficial by itself. Run this towards mature, closely audited code and virtually nothing survives, which continues to be price realizing. “We appeared laborious and located nothing” is an actual outcome. Run it towards less-explored code, or towards formally verified code, the place a machine-checked proof covers a mannequin and the deployed bytecode is barely assumed to match it, and extra will get via.
We’re not the one ones who discovered that the triage is the laborious half. Cloudflare’s major takeaway was {that a} slim scope beats broad scanning. Anthropic’s property-based-testing agent generated one thing like a thousand candidate stories, then used rating and knowledgeable evaluate to get all the way down to a high tier that held up about 86 p.c of the time. The technology was the simple half. I am not going to publish our personal numbers right here; tied to a particular goal, they’d say extra concerning the goal than concerning the methodology.
What the brokers are good at, and the place they mislead
There’s hype in each instructions, so this is a plain listing of what the brokers do effectively and the place they mislead.
The break up is not even regular from one job to the subsequent. Stanislav Fort, testing a variety of fashions on actual vulnerabilities, calls this a jagged frontier, or a mannequin that recovers a full exploit chain on one codebase can fail fundamental data-flow tracing on one other. You possibly can’t assume one good outcome means the subsequent will maintain up, which is one more reason each candidate will get checked by itself.
The final row is the essential one. A single agent session is sweet at one-shot reasoning and dangerous at bugs that span a sequence of steps, the place every step is legitimate and solely the order is incorrect. For these, the agent is not the search instrument. Its job is to recommend which sequences are price working via a stateful check harness. Used that means, it really works effectively. Used as a alternative for the harness, it misses the most costly bugs there are, those that solely present up throughout a sequence.
Preserving it trustworthy
A couple of habits do many of the work of constructing agent findings reliable, and none of them are difficult.
Provenance on each artifact: what produced it, with what context, towards which revision. A discovering must be one thing you’ll be able to re-run months later.Determinism the place it counts: one surroundings, one method to construct and run, so “reproduces” means the identical factor on each machine, not simply the one the place it was discovered.Norms, not scripts: inform brokers what issues, the invariants and the bar for an actual discovering, as a substitute of a numbered process. Over-scripted brokers break the identical means over-specified checks do, they preserve following the steps after the steps cease making sense. A research of repository context information discovered the identical factor: the additional necessities lowered job success and raised value by over 20%, and the authors advocate holding context to the minimal necessities.An individual makes the ultimate name: brokers recommend. They do not resolve what’s actual, what’s a replica of a recognized problem, or what will get disclosed and when.
The bottleneck moved
AI did not substitute the safety researcher. It moved the work. The time that used to enter arising with and chasing down hypotheses now goes into judging them at scale, together with constructing the oracle, working the triage, holding the listing of recognized points, and dealing with disclosure.
The bottleneck did not go away. It moved from discovering bugs to trusting the outcomes, which is a greater place for it, as a result of that is the place human judgment really issues. Nevertheless it’s nonetheless a bottleneck, and ignoring that’s how you find yourself transport a incorrect “it is effective.”
The practices that make this work aren’t new. Reproducible failures, actual oracles, and cautious triage are the identical practices that turned fuzzing from a analysis matter into customary observe over the past fifteen years. The instruments are new. The practices aren’t.
How briskly the instruments preserve altering is an open query. Nicholas Carlini, cautious and as soon as a skeptic himself, argues the exponential case is price taking severely, even whereas he retains extensive error bars on it. If the technology aspect climbs that quick, the judgment aspect has to climb with it, or the hole between what will get produced and what really will get verified solely widens.
For the programs Ethereum relies on, that is the half that issues. Brokers allow us to cowl way more floor than we may by hand. In change, they ask for extra cautious judgment, throughout a a lot larger pile of confident-sounding claims. That is a commerce price making, so long as you do not forget that the judgment is the actual product.
