EIPsInsight

Loading Experience

Preparing your insights...

Loading0%
EIPsInsightEIPsInsight
Sign in
All protocol calls
Previous
FCR2026-07-07_010

Fast Confirmation Rule #010

2026-07-07 1 decision 396 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
  • •Cross-client FCR compatibility testing to be coordinated on next FCR breakout call (~2 weeks) — 00:27:13
  • •FCR paper publication pending appendix clarifying pseudocode vs. Python spec differences — 00:31:53
Decisions
  • •FCR must not trigger during node sync; activation deferred until node is fully synced with head (agreed with Nimbus and Lodestar) — 00:14:27
Highlights
  • Client Updates:
    • ·Grandine: FCR-specific tests passing; PR pending review from Thomas — 00:05:00
    • ·Lodestar: FCR shipped in v1.44.0 (experimental flag); epoch-boundary reset fix deployed Friday, no resets since — 00:06:05
    • ·Lighthouse: regression from prior call resolved; fix in progress, mainnet runs show no resets — 00:16:42
    • ·Teku: production-ready FCR implementation underway; Prysm blocked on human review — 00:17:44
  • Research Updates:
    • ·Proof review complete; pseudocode differences from Python spec to be addressed in paper appendix — last blocker before publication — 00:31:02
    • ·Late-block recovery optimization (~1–1.5% more single-slot confirmations, prototyped in Teku) under consideration; proof work costly and may conflict with Casper research — 00:32:23
  • Spec And Testing:
    • ·FCR manual test suite complete; all planned cases covered (PR merged) — 00:28:21
    • ·Mainnet-config test vector generation took ~3 hours per test; minimal preset deemed sufficient — 00:29:02
    • ·FCR metrics PR merged; teams encouraged to implement across all clients — 00:30:10
  • Fcr Behavior And Gloas:
    • ·Decision: FCR should not trigger during node sync; only activate once fully caught up with head — 00:14:27
    • ·FCR on Gloas: confirmed payload from two slots prior (not one) due to Gloas timing change — 00:19:35
    • ·Some clients (e.g., Nimbus) enable FCR by default; others require a feature flag — 00:22:10
    • ·Barnabas: FCR should be tested on Gloas devnet 7; Dora visualization of FCR event stream planned — 00:23:52
Action Items
  • •Nazar Hussain (Lodestar) — Nazar to share epoch-boundary reset analysis and fix details in FCR Telegram group — 00:07:46
  • •Mikhail Kalinin — Mikhail to share Teku late-block optimization code reference in FCR Telegram group — 00:35:05

Meeting chat12

Key decisions

  • FCR must not trigger during node sync; activation deferred until node is fully synced with head (agreed with Nimbus and Lodestar)

    To prevent FCR from triggering during node sync, activation will be deferred until the node is fully synced with the head.

Links