zkSecurity retweeted
Cybersecurity professionals:

1990s: "all the software is broken"
2000s: "all the software is broken"
2010s: "all the software is broken"
2020s: "all the software is broken"

Fall 2026, the collective internet:
"OMG, all the software is broken and vuln".
1
4
9
405
zkSecurity retweeted
look for projects that are audited by zkao, security shouldn't be an after thought
1
2
6
530
zkSecurity retweeted
๐Ÿ‡บ๐Ÿ‡ธ ๐—™๐—ผ๐—ฟ๐—บ๐—ฎ๐—น ๐—ฉ๐—ฒ๐—ฟ๐—ถ๐—ณ๐—ถ๐—ฐ๐—ฎ๐˜๐—ถ๐—ผ๐—ป ๐—ถ๐—ป ๐—–๐—ฟ๐˜†๐—ฝ๐˜๐—ผ๐—ด๐—ฟ๐—ฎ๐—ฝ๐—ต๐˜† ๐—ณ๐˜. @archetypevc

๐—ฆ๐—ฒ๐˜€๐˜€๐—ถ๐—ผ๐—ป ๐—ก๐—ผ๐˜๐—ฒ๐˜€: (๐Ÿญ) DyLean, a tool that proves protocols secure, re-checks only what you change, also let you define your own threat model. (๐Ÿฎ) On better.codes, ty proof from 53 to 68 bits in 25 days. (๐Ÿฏ) Lean checks AI proofs instead of AI specs. [๐—ค๐˜‚๐—ฒ๐˜€๐˜๐—ถ๐—ผ๐—ป]: If AI writes both the proof and the description of what it should prove, who checks that weโ€™re proving the right thing?

๐—ฆ๐—ผ๐˜‚๐—ฟ๐—ฐ๐—ฒ -ย ๐——๐˜†๐—Ÿ๐—ฒ๐—ฎ๐—ป, ๐—ฎ ๐—ณ๐—ฟ๐—ฎ๐—บ๐—ฒ๐˜„๐—ผ๐—ฟ๐—ธ ๐—ณ๐—ผ๐—ฟ ๐˜๐—ต๐—ฒ ๐˜€๐˜†๐—บ๐—ฏ๐—ผ๐—น๐—ถ๐—ฐ ๐—ฎ๐—ป๐—ฎ๐—น๐˜†๐˜€๐—ถ๐˜€ ๐—ผ๐—ณ ๐—ฐ๐—ฟ๐˜†๐—ฝ๐˜๐—ผ๐—ด๐—ฟ๐—ฎ๐—ฝ๐—ต๐—ถ๐—ฐ ๐—ฝ๐—ฟ๐—ผ๐˜๐—ผ๐—ฐ๐—ผ๐—น๐˜€
github.com/BobDyLean/dyleโ€ฆ

None of it would have happened without our session guides @kobigurk (@zksecurityXYZ) and Abhi Shah [@Columbia] and venue partner @archetypevc ๐Ÿซถ๐Ÿป
1
2
5
241
zkSecurity retweeted
Was really fun to work on this report with @frogmonkee

It's free - let us know what you think!
Introducing the definitive guide to ZK in 2026.

The yearโ€™s biggest questions pointed to ZK: Can we trust AI? Will quantum break encryption? Can private money live on public rails? How do we know whatโ€™s real online?

Read how in the 2026 ZK Industry Report with @zeroknowledgefm.
1
2
24
1,476
latest zk report mentions our work on zk.golf and better.codes!
Introducing the definitive guide to ZK in 2026.

The yearโ€™s biggest questions pointed to ZK: Can we trust AI? Will quantum break encryption? Can private money live on public rails? How do we know whatโ€™s real online?

Read how in the 2026 ZK Industry Report with @zeroknowledgefm.
0
2
17
777
zkSecurity retweeted
๐ŸŽ™๏ธLast week @AnnaRRose, @nico_mnbl, @kobigurk spoke with @rotn256 & @g_dellimmagine from @zksecurityXYZ about zkGolf, a competition to build the most efficient, formally verified ZK circuits.

They dug into Clean, AI-driven circuit optimisation and more!

zeroknowledge.fm/podcast/414
2
5
16
1,171
zkSecurity retweeted
Now I own the Solana address whose private key is 4. solscan.io/account/4AjNauโ€ฆ
9
4
110
55,720
if you guys used zkao.io it would detect weak keys automatically, just saying
Announcing 3 Critical vulns for hundreds of millions of IoT, Firewalls, OT, and Military devices including: Palo Alto Networks, Comcast, D-Link, HP, Canon, Honeywell, GE, Oracle, Siemens, Rockwell, Digi, Lockheed Martin, Boeing...

The vulns are with GoAhead Web Server which is a backend library used by these devices. There's a patch available from GoAhead but that doesn't mean there's a patch available for the devices yet -- that's up to the manufacturer.

- TLS traffic over DHE ciphers have a 1-byte secret, "04", meaning anyone can decrypt connections to these devices and steal login credentials and session tokens if the client negotiated with DHE ciphers like the latest TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256, which is extremely likely.

- LibreSSL mTLS has been completely bypassed, meaning anyone can connect over mTLS. If you have one of these devices listening on the internet and are expecting mTLS to protect it from attackers, take it offline or patch asap.

- OpenSSL Certificate Revocation Lists (CRLs) are not enforced, meaning if a user device is stolen or compromised, and you revoke that mTLS cert, nothing actually happens. There are a lot of other attacks this can be used for.

These are critical because these types of devices run our world. Water systems, electricity, military, firewalls, critical infrastructure.

foxio.io/blog/choose-yoโ€ฆ
0
4
12
932
zkSecurity retweeted
What the hell is bro wearing ๐Ÿ˜ญ๐Ÿ™
26
179
3,123
46,669
New zk.golf challenge โ›ณ๏ธ Google ID Token Claims Extraction.

Take the raw JSON payload of a Google ID token, parse it, check it against Google's schema, and extract the claim values. All inside a circuit. (1/8)
3
4
28
1,783
Replying to @zksecurityXYZ
The best part: we never wrote the circuit ourselves.
We wrote the specification: a reference JSON parser and a simple declarative schema of what an acceptable Google ID token looks like. A few days later, an agent had written the corresponding circuit. (7/8)
1
0
1
136
Replying to @zksecurityXYZ
Think you can implement it using fewer constraints?
Prove it! โ›ณ๏ธ
zk.golf (8/8)
0
0
1
120
zkSecurity retweeted
What powers zkao? How is it different from running a model over your code? What does an audit cost?

A thread on how we approach AI security auditing, what youโ€™re paying for, and where the limits are. ๐Ÿงต
1
3
20
1,287
zkSecurity retweeted
we're seeing a peak of interest in our automated cryptography-bug finding tool zkao.io, did something happen this week?
0
3
5
352
we packed the last zk podcast with zksecurity folks! mathias, giorgio, nico, and kobi talk about our lean framework (clean) to formally verify zk circuits and our competitive platform for degens to submit lean proofs zk.golf!
2
5
22
3,418
Replying to @zksecurityXYZ
0
0
1
287