Jon Stephens

🔐 How does private state actually work in @AleoHQ? In our latest blog, @VeridiseInc security analyst Mark Anthony @epizeuxius breaks down records in Leo — the core primitive behind Aleo’s privacy & scalability. Link to the full blog post below 🧵 1/3

And we're LIVE! 🚀 We're thrilled to announce the general availability of Cubist Confidential Cloud Functions (C2F), the first Web3 confidential compute platform that brings smart contract guarantees to private off-chain code. Not only is C2F GA. It’s already being leveraged by leading Web3 teams, including by @squidrouter in the latest version of their Cross-Chain Order Routing and Auction Layer (CORAL). With Cubist C2F, you can: ✅ run compute-heavy logic ✅ execute sensitive logic privately ✅ scale across chains without rewriting everything ✅ apply strong governance and safe upgrade paths to critical code ✅ produce evidence that security and compliance controls are real Run your sensitive, compute-heavy, and cross-chain logic verifiably with Cubist C2F.

🚀 Introducing AuditHub: The next-generation blockchain security platform for Web3 developer teams. Built by Veridise — now available to the entire dev community. Follow @AuditHubDev for updates. Thread 🧵

We’re excited to launch LLZK, an open-source intermediate representation (IR) for zero-knowledge circuits. Think LLVM, but for ZK. Built by @VeridiseInc and supported with a grant from the @ethereumfndn, LLZK is now live on GitHub. Thread 🧵 1/4

House of ZK Radio #49: Jon Stephens, CEO of Veridise - out now on Spotify & YouTube 🔲🔳 In this episode we sit down with @FormallyJon, Co-founder & CEO of @VeridiseInc, to explore the state of security in zero-knowledge systems. From smart contract audits to formal verification of ZK circuits and ZKVMs, Jon breaks down where things go wrong, how Veridise builds internal tools like Vanguard and Picasso, and what developers should know when building verifiable applications. Essential listening for anyone serious about ZK security 🤝 Spotify: open.spotify.com/episode/1VLBRf… YouTube: youtube.com/watch?v=W-9hD7…

Join us for an insightful fireside chat with @mjdklein, a software engineer at @aztecnetwork, as we dive deep into the @NoirLang programming language—a key component of the Aztec Network. Hosted by @FormallyJon from @VeridiseInc. Timestamps: 0:00 – Introduction: Aztec & Noir language 0:57 – Why Aztec built its own ZK language 2:22 – Overview of Noir and its developer experience 3:20 – How Noir compares to other ZK DSLs 4:33 – Unconstrained functions 6:19 – What Noir offers that other zk DSLs don’t 7:00 – Tools that are currently missing in Noir 8:24 – How the Noir ecosystem might evolve & new tools 9:19 – Metaprogramming in Noir and what it enables 11:28 – Improved succinctness & metaprogramming 13:56 – Who can use Noir and whether it’s tied to Aztec 15:17 – The types of vulnerabilities that are top of mind 17:15 – Work done to ensure optimization passes are valid 18:20 – Formal verification (SMT solvers) considerations 19:18 – Types of bugs devs may unintentionally introduce 21:18 – How entropy could lead to privacy leaks 23:35 – Guardrails built into Noir to prevent such issues 24:50 – How common such vulnerabilities might be 26:13 – Noir circuits vs zkVMs in terms of privacy 28:16 – Local proving systems vs. proving networks 29:36 – How devs can evaluate if SMT solvers are right for them

We set out to implement the Mastermind game in 5 different ZK languages/frameworks: Circom, Gnark, Noir, Halo2, and Arkworks. The aim was to evaluate the capabilities and characteristics of these various ZK languages. Check out @iangneal's full blog post below 🧵 1/5

Today at 12:00 PM EST, Week 7, Session 13 of the Zkmonk BootCamp features - @FormallyJon Jon Stephens, CEO of @VeridiseInc, presenting on ‘ZK Security Considerations.’ Gain valuable insights into the security challenges and best practices for zero-knowledge technologies from an industry expert. LINK: meet.google.com/jdn-ihmj-eyg

Big data drop❗Breakdown of 100 Veridise security audits. @TheBlock__ covers our top insights from 1605 vulnerability findings. Key takeaways below 🧵 1/8