zkEVM2026-10-14_009

L1-zkEVM Breakout #009

2026-10-14 2 decisions 631 transcript lines

Transcript

Call summary

Targets
  • •EF prover deployment on Sepolia — near term, pending Prysm/Lighthouse interop resolution - 00:50:07
  • •Zilkworm Alpha 5 — native stateless input bytes support, two test fixes, full EERE integration out of draft - 01:00:20
Decisions
  • •EIP-7709 CFI'd at ACDE; removes 'headers' field from execution witness by routing BlockHash through EIP-2935 contract - 00:21:37
  • •Proof engine scope in consensus specs narrowed to verification only; proof generation/fetching is unspecified client responsibility - 01:03:20
Highlights
  • Testing Progress:
    • ·zkVM test release v21 based on Sepolia official tests; public keys field removed from stateless inputs - 00:23:54
    • ·R2 bucket live for Sepolia stateless inputs (50k+ blocks); Hoodi and mainnet buckets planned as forks activate - 00:28:38
    • ·Hive consumer now supports REST+SSZ variant of Engine API; Nimbus already merged implementation - 00:31:22
  • Cl Optional Proofs:
    • ·Consensus-spec refactor: proof engine scope reduced to verification only; client teams free to embed verifier or use HTTP sidecar - 00:44:09
    • ·New draft EIP for recursive chain proofs: single proof covering weak-subjectivity checkpoint to head, reducing sync bandwidth by orders of magnitude - 00:46:26
    • ·EF intends to deploy prover on Sepolia; client teams invited to join and test EIP-8025 on testnet - 00:50:07
    • ·Prysm proof-of-concept EIP-8025 implementation complete (gnark verifier embedded in binary); running verifier node on Sepolia; incompatibility with Lighthouse 'proof type 0' under investigation - 00:50:40
    • ·Lighthouse merged proof-engine sidecar support into Unstable; can now run Unstable without an EL; verifiers to be integrated into codebase later - 01:27:52
  • Zilkworm Guest Client:
    • ·Silkworm Alpha 4 registered in EERE benchmark; passes full zkVM test suite (2 known failures matching Reth); ~half the estimated proving cost of Reth on every block - 00:57:55
    • ·Alpha 5 target: native stateless input bytes support (no adapter); two failing tests to be fixed - 01:00:20
    • ·Alpha 2→Alpha 4: one-third reduction in executed cycles; SP1 Hypercube used as benchmark VM - 01:01:13
    • ·Airbender V3 integration live: ~3.8s proof with two 25090 GPUs; JUMPDEST analysis accounts for up to 30% of EVM execution cycles - 01:12:54
    • ·Zilkworm now fully open source (SDLC pipeline, CI, PRs all public) - 01:14:33
    • ·MFBD flat witness format: minimally-perfect-hash-based, zero-copy cast from input bytes; DirectState ~11% faster than full reconstruction from stateless input bytes - 01:15:04
  • Eip Proposals Glamsterdam:
    • ·EIP-8025 (zkEVM stateless inputs) targeting CFI at ACDC tomorrow; attendance encouraged - 00:18:57
    • ·EIP-7709 (BlockHash via EIP-2935 contract) CFI'd at ACDE; removes 'headers' field from execution witness - 00:21:37
  • Zkevm Standards And Security:
    • ·Hash-map collision attack described by Lukasz (Nethermind): all provers for a given zkEVM vulnerable simultaneously; new randomness-seeding standard proposed with OpenVM demo - 00:36:33
    • ·RISC-V compliance gaps identified across tested zkVM teams; proposal to require tests alongside each new standard - 00:37:50
Action Items
  • •EL/CL client teams and zkEVM stakeholders - Join ACDC tomorrow to support CFI vote for EIP-8025; teams with strong opinions should attend - 00:18:57
  • •CL client teams (Prysm, Lighthouse, Francesco) - Agree on Beacon API GET method for execution proofs to support Dora explorer - 00:53:10
  • •Zilkworm + guest program teams - Discuss upstreaming Zilkworm RISC-V optimizations (memcpy, byte-swap, JUMPDEST) to benefit all guest programs - 01:29:31

Key decisions

  • EIP-7709 CFI'd at ACDE; removes 'headers' field from execution witness by routing BlockHash through EIP-2935 contract

    CFIRemoves 'headers' field from execution witness by routing BlockHash through EIP-2935 contract
  • Proof engine scope in consensus specs narrowed to verification only; proof generation/fetching is unspecified client responsibility

    Consensus-spec refactor narrowing proof engine scope to verification only

EIPs discussed

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.