EIPsInsight

Loading Experience

Preparing your insights...

Loading0%
FOCIL2026-03-24_031

FOCIL Breakout #031

2026-03-24 3 decisions 95 transcript lines

Transcript

Call summary

Targets
  • Post-ECC - Resume spec and testing progress - 00:20:51
  • April 7, 2026 - Next FOCIL Breakout #32 - 00:21:15
Highlights
  • Spec Updates:
    • ·All specs rebasing to Hegotá: execution-specs, engine-apis completed; CL spec updates pending - 00:16:29
    • ·New 12-second attester cutoff deadline needed to prevent split view during equivocations - 00:17:01
    • ·Split view issue: attesters seeing IL equivocation at different times vote inconsistently - 00:18:19
    • ·8-second deadline to be removed as implementation-dependent example - 00:19:23
  • Testing Updates:
    • ·CL: Focus on reference tests initially, expand to fuzzing/devnets later - 00:19:33
    • ·EL: Updating test infra to support inclusion lists with testing team - 00:19:42
  • Development Progress:
    • ·Besu: PR under review; Hegotá timeline feasible, prioritizing Glamsterdam optimizations - 00:12:03
    • ·Besu targeting build-ready status for Interop (~4 weeks out) - 00:13:43
    • ·Lodestar: Implementation simple, can hack together in hours if needed - 00:14:30
Action Items
  • All teams - Review rebased execution-specs PR #1928 and engine-apis PR #609 - 00:16:32
  • Jihoon - Finalize attester cutoff deadline spec changes post-ECC - 00:17:51

Key decisions

  • All specs rebasing to Hegotá: execution-specs, engine-apis completed; CL spec updates pending

    The team decided to rebase all technical specifications, including execution-specs and engine-apis, to the Hegotá upgrade base.
  • New 12-second attester cutoff deadline needed to prevent split view during equivocations

    A decision was made to introduce a 12-second attester cutoff deadline to address network split view issues occurring during equivocations.
  • 8-second deadline to be removed as implementation-dependent example

    The 8-second deadline will be removed from the specification because it was considered an implementation-dependent example rather than a core requirement.