ZK/SEC Research notes from zkSecurity
All posts
zkao · Part 3 of 3

zkao 2.0 is here

Today we're releasing zkao 2.0, the biggest update to zkao since we launched it earlier this year. If you're new here: zkao is the automated bug-finding tool we created to find bugs in cryptography applications, and it has already caught critical bugs in the production code of many of our clients. With 2.0 we're opening it up to many more users who want to scan their own code, and at a fraction of the cost of an audit, trying it is a no-brainer. This release comes with a new pricing model, a complete redesign, and a ton of improvements under the hood.

Pay as you go, no more subscriptions

The change we're most excited about: zkao is now pay-as-you-go. We're dropping subscriptions entirely.

Since day one, zkao has been built around the idea that AI security research works like fuzzing: a single scan is a coin flip, and coverage comes from running it again and again. But a monthly subscription never quite matched how people actually use a tool like that. Some weeks you're shipping a new circuit and want to hammer it with scans, other weeks nothing changes and you shouldn't be paying for idle time.

So now you simply buy credits and spend them on scans, whenever you want, at whatever tier you want (including our most thorough tier, "zkao max"). No recurring charge, no seat count, no lock-in. Your credits don't expire, and your scan history, findings, and reports stay with you.

Note

Existing subscribers If you're on a subscription today, you don't need to do anything: your remaining subscription time is automatically converted into credits.

A new design

zkao 2.0 also ships with a complete redesign of the app. Connecting a repository, kicking off a scan, and triaging findings now take fewer clicks, and the interface got a full visual overhaul to match.

The best way to appreciate the difference is to look at where we came from. Back in June we recorded a deep-dive walkthrough of zkao 1.2.0, and it's now a nice time capsule of the old design:

Everything shown in that video is still there, just faster and better looking: tiered AI-powered scans, collaborative agents that learn from your feedback to cut down on false positives, tooling to triage real bugs like proof forgeries, and public security reports you can share with your users.

And tons of improvements

Beyond pricing and design, 2.0 rolls up months of shipping across the whole product: smarter scanning agents informed by our latest audits, better deduplication of findings across runs, and countless quality-of-life fixes in triaging and reporting. It also builds on the ecosystem work we've been doing recently, like bringing Aleo and Leo into zkao.

Tip

Try it Head over to zkao, connect a repo, and run your first scan. With pay-as-you-go there's no commitment: buy a few credits and see what it finds.

The goal hasn't changed since launch: bridge the gap between expensive one-shot manual audits and continuous security that compounds over time. zkao 2.0 just makes that a lot easier to use, and a lot easier to pay for.

Keep reading
Recommended

zkao: Security That Compounds

Today we're launching zkao, a product by zkSecurity that makes AI security research work the way fuzzing works: not as a one-shot event, but as something you run continuously until coverage compounds.

ZK/SEC · February 07, 2026

Bringing Aleo and Leo into zkao

We recently brought Leo and Aleo support to zkao, our AI-powered bug-detection tool, and put it to work on a real engagement with HumanityLink. Getting an LLM to audit a young ecosystem like Aleo turned out to be less about the model and more about what we fed it - custom prompts or skills so it actually recognizes Aleo bug patterns, a harness called cheatVM that turns findings into real end-to-end proofs of concept instead of code that just looks right, and a clear threat model that significantly cut down our false positives.

zk/sec · July 20, 2026

Bug Hunt: Zero-Knowledge, Full-Paranoia, and the AI That Stares Back

Over the past year, we've been diving into whether AI can effectively identify bugs in zero-knowledge circuits and applications, sparking questions about the future of auditing. This led us to develop SnarkSentinel, an AI-powered auditing tool. We'll share what worked, what didn’t, and how our journey with AI could impact auditing. From early challenges with Circom to innovative methods like retrieval-augmented generation and agent-led probing, we'll give you a peek into our findings, including both successes and setbacks with bug detection. Discover how AI might enhance or change the landscape of auditing and what this means for developers and security pros alike.

ZK/SEC · July 03, 2025
More to explore

Do in secret. Assert in public. Don't under-constrain your prover's witness computation in ZK programs

Curious about diving into zero-knowledge (ZK) application development? Our blog post is here to guide you through the common security pitfalls and mindset shifts essential for tackling ZK programming. We reflect on our journey from the early days of Mina Protocol to the dynamic space today, filled with tools like SnarkyJS and newer approaches to split the prover and verifier roles effectively. Discover the errors to avoid, like under-constraining data and letting divisors slip through unchecked, and learn how a solid review and audit process can save your ZK applications from disastrous security issues. Dive in to get the insights you need to navigate the ZK landscape confidently!

Brandon Kase · June 01, 2023

Lean4 formalization of "A Simplified Round-by-round Soundness Proof of FRI"

A Lean4 formalization of the paper "A Simplified Round-by-round Soundness Proof of FRI" by Albert Garreta, Nicolas Mohnblatt, and Benedikt Wagner, completed using Harmonic's Aristotle agent and Claude Code. Welcome to the strange world of machine-led formalization of cryptography.

Yoichi Hirai · January 26, 2026

Public report of Darkfi circuits and crypto audit

In February 2024, we dived into a security audit of Darkfi's built-in contracts and circuits, putting them under the microscope to ensure everything checks out. Curious to know what we discovered while navigating the public Darkfi repository? Check out our full report for insights and findings.

ZK/SEC · February 27, 2024