Can we prove that a zkVM works as intended? @theyisun, co-founder of @axiom_xyz, is joining Devcon 8 to share his work on end-to-end formal verification of OpenVM. Building with ZK? Join Yi to learn how verification can help strengthen the security of systems you're building.⚡

Announcing Pico Prism, the state-of-the-art zkVM for Ethereum real-time proving. 99.6% of blocks proven under 12 seconds, 6.9s average with 64 RTX 5090 GPUs. This marks a major step toward scaling Ethereum by 100x and a future where you can validate the chain from a phone.

"Trust me, it's done" is where every agent marketplace breaks. AACP escrow: USDC/USDT locked on-chain before work starts, released only when an evaluator verifies the deliverable. zkVM proof, not vibes. Nobody can pull it early. Not even us.

THE BLOCK: The Ethereum Foundation is dropping the specialized Poseidon hash for the base layer in favor of established options like SHA or BLAKE, after new research showed traditional hashes can now perform just as well in advanced zero-knowledge systems. Introduced in 2019, Poseidon secures "billions via zkrollups and zkVMs," EF researcher Justin Drake said.

We’re hiring a Technical Partnerships Lead (remote + full-time)! We're looking for someone with: • ZK / zkVM / proving infra knowledge • Technical BD or ecosystem experience • AI-native execution • Ability to drive real integrations Apply here 👉

you used to carry five devices. now you carry one. we did the same for finance. aligned is the full stack for building financial products on @ethereum: wallets, rollups, proof aggregation, interoperability and a zkvm in a single integration.

From 0 to ZK Concept Bites #7#: Verifiable Provenance Last time we covered the redundancy problem, how Ethereum's "everyone verifies everything" model creates the bottleneck that real-time proving solves. This time, a different ZK property: provenance. 🛡️ Provenance is the ability to prove where something came from and what happened to it along the way. The clearest live example is Brevis Vera. Modern flagship cameras (Sony, Leica, Nikon, Canon) ship with C2PA, a standard that cryptographically signs every photo at the moment of capture. The image carries a verifiable record of which device produced it. Any edit afterwards breaks that signature. Vera fixes the break. Each edit between capture and publication runs inside Pico zkVM, which generates a proof that the edit was legitimate. The result is an unbroken chain from camera sensor to whatever image you're looking at. Provenance shows up beyond images too. Anywhere you need a verifiable chain of custody, this is the property doing the work. We just added a section on this to Part 4 of the refreshed From 0 Knowledge to Zero Knowledge series. Dive deeper there 👇

lowercase snarks Words like laser, scuba, radar began uppercase. LASER — Light Amplification by Stimulated Emission of Radiation SCUBA — Self-Contained Underwater Breathing Apparatus RADAR — RAdio Detection And Ranging When a technology matures and becomes reliable, trusted, commoditised, it earns the lowercase. Lean Ethereum is a bet on snarks, not Succinct Non-interactive ARguments of Knowledge. Post-quantum security. Provable soundness. End-to-end formal verification. Deep cryptanalysis. Real-time proving. zkVM programmability. Simplicity and elegance. All essential for the lowercase. All inevitable. Ethereum L1 has 10y uptime and $1T secured with hashes and signatures, our cryptographic workhorses. I believe in 100y uptime and $1Q secured with snarks, our cryptographic jet engines. * L1 scale — 10K TPS gigagas scale with real-time zkEVMs * L1 security — post-quantum security with snarked signatures * L1 privacy — Zcash-grade stealth with wormholes (eg EIP-7503) Shipping snarks is a cryptographic Manhattan Project, one the EF is investing tens of millions into: * verified-zkevm[.]org — formal verification * poseidon-initiative[.]info — deep cryptanalysis * ethproofs[.]org — real-time proving * proximityprize[.]org — provable soundness * zkevm.ethereum[.]foundation — enshrinement * pse[.]dev — privacy Step by step, the EF is evolving into a snark-first org: * cryptography team — driving soundness and cryptanalysis * snarkification team — driving formal verification * zkEVM team — driving protocol integration * Ethproofs team — driving real-time proving * PSE team — driving privacy * PQ consensus team — soon™ Believe in something magical. Believe in lowercase snarks.