FOCIL2026-09-15_042

FOCIL Breakout #042

2026-09-15 2 decisions 355 transcript lines

Transcript

Call summary

Targets
  • Next breakout: discuss FOCIL+frames spec changes, max verify gas benchmarks, and potential VOPS use cases - 00:41:50
Decisions
  • FOCIL devnet-0 will launch once Teku+Lodestar interop issue is resolved; no need to wait for all clients - 00:13:00
  • Two-track approach adopted: continue FOCIL devnet-0 work in parallel with FOCIL+frames spec and interaction design - 00:43:44
Highlights
  • Devnet Status:
    • ·Teku batching gossip objects into single RPC exceeds Lodestar's 4MB incoming limit; PR open to raise limit to 10MB - 00:04:24
    • ·FOCIL devnet-0 minimum bar is 2 EL + 2 CL clients; 3 EL clients ready, waiting on Teku+Lodestar interop fix to launch - 00:10:32
  • Focil Frames Interaction:
    • ·EIP-8369 (VOPS Profiles for FOCIL Eligibility) defines two profiles: Profile 1 = FOCIL with regular txs, Profile 2 = FOCIL + frame txs - 00:14:36
    • ·VOPS state boundary is key trade-off: larger VOPS = more txs benefit from FOCIL guarantees but higher node storage requirements - 00:17:05
    • ·Builder index (witness for frame tx omission) mechanism unresolved: unclear if separate object or embedded in existing payload envelope - 00:20:48
    • ·Nethermind and ethrex both have untested FOCIL+frames implementations; ethrex spec PR expected within 1–2 weeks - 00:31:33
Action Items
  • Iván | ethrex - ethrex to open spec PR for FOCIL+frames interaction; target: before next breakout - 00:41:25
  • Nethermind, ethrex - Marc and Iván to share FOCIL+frames implementation links in Discord for cross-team review - 00:46:15

Key decisions

  • FOCIL devnet-0 will launch once Teku+Lodestar interop issue is resolved; no need to wait for all clients

    devnet-0Launch after resolving Teku+Lodestar interop issue, without waiting for all clients
  • Two-track approach adopted: continue FOCIL devnet-0 work in parallel with FOCIL+frames spec and interaction design

    Proceed with devnet work while developing spec and interaction design

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.