EIPsInsight

Loading Experience

Preparing your insights...

Loading0%
EIPsInsightEIPsInsight
Sign in
All protocol calls
PreviousNext
FCR2026-05-12_007

Fast Confirmation Rule #007

2026-05-12 1 decision 311 transcript lines

Transcript

Ask about this call

Answered from this call's summary and transcript only.

AI-generated — verify against the recording.

Call summary

Targets
  • •Next FCR call in approximately two weeks — 00:31:41
Decisions
  • •FCR spec will be made gGLOSSS-compatible via fork choice abstraction layer refactor; if infeasible, spec will be made fork-aware instead — 00:20:42
Highlights
  • Client Updates:
    • ·Lodestar: FCR implementation deployed on 5+ nodes for over a week; PR under team review, expected merge within a week — 00:08:15
    • ·Grandine: Two pre-existing bugs identified post-spec-merge — relative epoch helper rejecting lookups and unrealized justified checkpoints on fork chains; fix expected by Friday — 00:14:26
    • ·Nimbus shipped FCR enabled by default, then disabled it after discovering Nethermind safe-head incompatibility with engine API spec; FCR will be re-enabled once Nethermind fix is released — 00:16:59
    • ·Nethermind fix for safe-head engine API bug merged (PR #11187) but not yet released — 00:17:31
  • Research Updates:
    • ·FCR research paper nearly ready for publication; pending review of latest feedback round — 00:24:46
  • Spec And Testing:
    • ·Main FCR spec PR merged; not yet gGLOSSS-compatible — work in progress to abstract fork choice layer so FCR works across forks — 00:19:26
    • ·Spec tests exist for minimal preset only; mainnet preset tests under consideration but constrained by 6-hour CI time limit — 00:11:43
    • ·Beacon API PR #598 merged: adds FCR confirmed-block events (block root + slot) to event stream — 00:30:07
  • Metrics And Observability:
    • ·Lodestar already tracks confirmed block slot and finalized slot; distance calculable in Grafana — 00:27:37
    • ·Dora explorer proposed to be extended to display most-recently confirmed block on devnets — 00:32:35
Action Items
  • •Mikhail Kalinin — Open PR defining standard FCR metrics (confirmed slot distance, restarts, runtime) for cross-client alignment — 00:27:49
  • •Mikhail Kalinin — Add Grandine (Mercy) to Fast Confirmation Telegram group — 00:15:33

Meeting chat7

Key decisions

  • FCR spec will be made gGLOSSS-compatible via fork choice abstraction layer refactor; if infeasible, spec will be made fork-aware instead

    To ensure cross-client alignment and compatibility

Links