L1-zkEVM Breakout #007
Transcript
- read.ai meeting notes
Ignacio added read.ai meeting notes to the meeting. Read provides AI generated meeting summaries to make meetings more effective and efficient. View our Privacy Policy at https://www.read.ai/pp Type "read stop" to disable, or "opt out" to delete meeting data.
- Gary Schulte
GM
- ignacio
gm
- Derek Sorensen
gm
- ignacio
waiting an extra minute and we'll start
- Francesco Risitano (Tau)
gm
- Derek Sorensen
Reacted to "waiting an extra minute and we'll start" with 👍
- read.ai meeting notes
Read isn't recording yet. The Zoom host needs to enable recording permission first. Learn more at https://support.read.ai/hc/en-us/articles/16949100155923-How-do-I-enable-recording-permissions-in-Zoom
- Francesco Risitano (Tau)
brb
- read.ai meeting notes
Read wasn't granted recording permission, so no part of this meeting was recorded. Read is now leaving.
- ignacio
my slides https://docs.google.com/presentation/d/1iS976lc4LY_H06L7v6aB8aaQXcdTzc7j_p2xI6QXhVE/edit?usp=sharing
- Gary Schulte
Reacted to "my slides https://docs.google.com/presentation/d/1iS976lc4LY_H06L7v6aB8aaQXcdTzc7j_p2xI6QXhVE/edit?usp=sharing" with 👍
- Gary Schulte
is it reasonable to expect to be able to compare “c” across zkvms? edit: nvm, I see the note about optimization signal
- ignacio
Replying to "is it reasonable to ..." Nope, c should only be comparable within the same zkVM.
- Gary Schulte
Reacted to "Nope, c should only be comparable within the same zkVM." with 👍
- cody
Reacted to "Nope, c should onl..." with 👍
- Gary Schulte
slide deck link for Marcin?
- Marcin Bugaj
https://drive.google.com/file/d/1byxArSPp9o3vanjZRHk8woae3vRpcN2b/view?usp=sharing
- Marcin Bugaj
the link to my presentation
- Gary Schulte
Reacted to "the link to my presentation" with 🙏
- Kevaundray Wedderburn
Reacted to "the link to my presentation" with 🙏
- Han Jian
https://docs.google.com/presentation/d/1cIwP42r7MiHZ7fSfr4nBCW_1TtHl7zrychtsj3FoLhY
- Gary Schulte
Franceso slides?
- cody
https://codygunton.github.io/talks-and-writing/2026-08-12-zkevm-breakout/
- Francesco Risitano (Tau)
- Francesco Risitano (Tau)
- Francesco Risitano (Tau)
Call summary
Targets
- •V070 guest program release supporting Glamsterdam devnet 8 — today or tomorrow (Aug 12–13, 2026) - 00:10:24
Decisions
- •EIP-8025 refreshed spec to be CFI'd for Hegota - 00:05:38
- •EIP-7709 (BlockHash via EIP-2935 system contract) merged and CFI-ready for Hegota - 00:06:15
- •zkVM guest API standards ownership transfers from Marcin Bugaj to Cody upon Marcin's departure end of August - 00:23:29
Highlights
- Zkvm Standards:
- ·10 standards accepted; new draft: proving cost estimation (single metric C, linear to proving time; cost scopes for sub-region measurement) - 00:20:38
- ·Marcin Bugaj leaving EF end of August; zkVM guest API standards ownership transfers to Cody - 00:23:29
- Eip Proposals Hegota:
- ·EIP-8025 spec refreshed (led by Francesco + Jochem review); CFI for Hegota targeted; much more complete than prior draft - 00:05:38
- ·EIP-7709 merged: BlockHash resolved via EIP-2935 system contract (SLOAD); simplifies stateless input; CFI-ready - 00:06:15
- Prover Infrastructure:
- ·OpenVM 2.1 benchmarked on mainnet + EEST blocks; reproduces ~2.4s mean proving time for same 1,000-block set - 00:35:31
- ·Prover implemented as a target client for benchmarker; forwards requests to distributed proving cluster; supports OpenVM and SP1; results published to GitHub Pages via Benchmarker UI - 00:36:26
- ·Cost estimator integration into airguest planned; dashboard for guest performance tracking + correlation analysis with cluster proving times - 00:38:15
- Recursive Guest Program:
- ·Francesco: recursive guest client design — execution proof attests to full chain from weak-subjectivity origin to head; eliminates P2P request-response protocol for proofs - 00:28:55
- ·Initial implementation in airguest for ethrex and Reth; CI not yet green; early research, subject to rapid change - 00:34:12
- Security And Compliance:
- ·OpenVM 2.1 fully compliant on compliance testing dashboard; SP1 proving support added; zk upgraded to 1.0.0-alpha (one gap, next release) - 00:39:56
- ·RISC-V fuzzer (Stefanos, Martin, Varun EF grant) released publicly; found multiple bugs; covers GPU proving across several zkVM provers - 00:41:03
- ·Formal RISC-V compliance verification of ZSK: 5 circuit bugs found (6th peripheral); all constraints now confirmed in use - 00:42:43
- Hive Dashboard And Tooling:
- ·Hive dashboard now covers Besu, ethrex, Geth, Nethermind, Nimbus (stateful ELs) + guest program/zkVM combos (stateless validators) in one view - 00:11:32
- ·Single EEST fixture format now used for tests, benchmarks, devnet blocks, and mainnet blocks across all tooling - 00:16:25
- ·opcode count metadata added to benchmark results; feeds directly into EVM gas repricing regression models (EVM Gasfit) - 00:17:27
- Guest Program And Spec Updates:
- ·Three releases (B060–B062) on Glamsterdam devnet 7; upcoming V070 targets Glamsterdam devnet 8 (today/tomorrow) - 00:08:02
- ·Chain config simplified: schema ID added to public input, chain config removed (only CHAINID retained); Progressive SSZ for state/public keys eliminates gas-limit-dependent list sizing - 00:09:47
- ·Guest program handbook published: defines expectations for guest teams (licensing, ELF ownership, CI, dashboards) - 00:13:54
- ·ELF generation ownership shifting to each guest program team (Besu, ethrex, Reth, Nethermind in progress); aria/airguest provides tooling only - 00:14:51
Action Items
- •EL client teams / EIP stakeholders - Review UX impact analysis for EIP-7709 (BLOCKHASH via SLOAD); ping affected projects re: hard-coded gas - 00:07:15
- •zkVM teams - Review proving cost estimation standard (large, significant zkVM implementation burden) - 00:23:14
Key decisions
zkVM guest API standards ownership transfers to Cody upon Marcin's departure end of August
zkVM guest API standards ownership transfers from Marcin Bugaj to Cody upon Marcin's departure end of August
AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.