All protocol calls
PreviousNext
zkEVM2026-05-13_004

L1-zkEVM Breakout #004

2026-05-13 3 decisions 367 transcript lines

Transcript

Call summary

Targets
  • •zkEVM CL integration devnet launch targeting next week - 00:11:57
  • •Spec/test release 0.35 (with schema ID, chain config, pubkey fixes) targeting today or tomorrow - 00:26:16
Decisions
  • •Validator proof re-signing proposal deprecated; peer scoring is sufficient for DOS prevention - 00:17:21
  • •Misaligned jump standard: must cause abnormal termination — no recovery, no address rounding permitted - 00:39:29
  • •U256 acceleration interface not yet standardized; further investigation needed on addition/subtraction and bitwise acceleration - 00:41:10
Highlights
  • Cl Integration:
    • ·Prysm now supports 3 modes: proof generation (via ZKBoost), proof verification, and EL-less verify-only mode - 00:08:13
    • ·Optional proof spec still based on Gossip; plan to migrate to Gloas soon - 00:11:33
    • ·Lighthouse and Prysm Kurtosis interop devnet running; devnet launch targeting next week - 00:11:46
    • ·Max proof size bumped to 400 KiB (interim); likely to exceed 1 MB before prover optimization; ZisK already below 400 KB - 00:15:52
    • ·Validator proof re-signing proposal deprecated; peer scoring deemed sufficient for DOS prevention - 00:17:04
  • Spec And Witness:
    • ·Spec/test release 0.34 adds block test engine format and execution witness compliance dashboard - 00:25:17
    • ·Next release (imminent) adds schema ID prefix to guest input bytes, chain config in stateless input, and proper public key field population - 00:26:33
    • ·EIP-7709 proposed at last ACDE for Hegota; simplifies BlockHash resolution in execution witness - 00:30:39
    • ·Execution witness fixtures found a bug in a BAL implementation, validating test coverage value - 00:31:12
  • Guest Program Optimization:
    • ·eFrex/ZISK profiling yielded up to 26% reduction in AIR costs: 21% from switching to precompile hash calls; ~0.5% from removing rayon/sync overhead - 00:34:13
    • ·SSZ serialization rewrite of execution witness planned to replace archive format - 00:36:27
  • Zkvm Guest Api Standardization:
    • ·5 standards accepted: RISC-V target (RV64IM), I/O interface, Crypto Accelerator API, termination semantics, memory layout - 00:37:39
    • ·Two new standards in review: misaligned jump must cause abnormal termination (no rounding); vendor runtime spec (static lib + linker script) - 00:38:50
    • ·U256 acceleration benchmarked on ZISK: multiplication 2-6x gain, but addition/subtraction mixed or slower; impact on 500 real blocks negligible — not yet standardized - 00:41:10
    • ·Nethermind ZKVM effectively first to fully comply with unaligned-access standard per Cody's testing - 00:53:14
  • Infrastructure And Verification:
    • ·ZKBoost config simplified in Kurtosis package: prover image and guest program links now resolved automatically - 00:46:07
    • ·Nexus verifier crate separated from prover and integrated directly into ZKBoost; prover container no longer needed for verify-only mode - 00:46:31
    • ·Formal RISC-V semantics verification of ZISK proving system in progress; external review targeted within weeks - 00:50:25
Action Items
  • •EL teams - Execution-APIs PR for witness retrieval (withWitness boolean + executionWitness return field) needs review from EL teams - 00:18:41
  • •Community / L2 teams - Contribute to open issue on proof type encoding to support generic guest/ZKVM combinations (e.g., native rollup use cases) - 00:20:09
  • •ZKVM teams - ZKVM teams to review and opine on Keccak-F permutation accelerator PR vs. full Keccak function interface - 00:44:25

Key decisions

  • Validator proof re-signing proposal deprecated; peer scoring is sufficient for DOS prevention

    Peer scoring is sufficient for DOS prevention

  • Misaligned jump standard: must cause abnormal termination — no recovery, no address rounding permitted

    No recovery or address rounding permitted for misaligned jumps

  • U256 acceleration interface not yet standardized; further investigation needed on addition/subtraction and bitwise acceleration

    Further investigation needed on U256 acceleration interface

Links

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.