FCR2026-06-23_009
Fast Confirmation Rule #009
2026-06-23 1 decision 291 transcript lines
Transcript
- Mikhail Kalinin
- Nico Flaig
we are also passing the fcr spec tests for gloas that we have since alpha.11
- Mikhail Kalinin
- Mikhail Kalinin
- Mikhail Kalinin
- Nico Flaig
Call summary
Targets
- •Lodestar public FCR release — this week or start of next week - 00:06:11
- •FCR edge case tests PR — tomorrow (June 24, 2026) - 00:17:25
- •FCR research paper publication — this week - 00:19:57
Decisions
- •EL block tag for FCR will reuse 'safe'; introducing a new tag requires hard fork coordination and is deferred until after Glamsterdam - 00:28:02
Highlights
- Client Updates:
- ·Lodestar: FCR deployed to test fleet and RC; public release + blog post expected this week or early next week - 00:05:51
- ·Lighthouse: investigating likely regression causing reversions to finality; test coverage needed for this case - 00:11:54
- ·Lodestar passing FCR spec tests for Gloas since alpha.11 (chat) - 00:13:45
- ·Grandine: metrics PR awaiting maintainer review; blocked on Samas or another core maintainer to merge - 00:12:05
- Api And Metrics:
- ·beacon-APIs PR #616 (adds current_slot to event stream) merged - 00:18:41
- ·beacon-metrics PR #22 (FCR metrics) approved; awaiting merge from Panda/Barnabas - 00:18:57
- ·Lodestar internal metric shows 3 FCR resets in last 7 days on Nico's node; cause uninvestigated - 00:20:33
- Research Updates:
- ·FCR research paper publication expected this week; no blockers identified - 00:19:54
- ·EL 'safe' block tag discussion: introducing a new fast-confirm tag would require hard fork coordination between CL and EL; deferred until after Glamsterdam - 00:27:41
- Testing Progress:
- ·New consensus-specs PR enables FCR tests for loss/hazard cases and disables BLS for stable, fork-independent shuffling - 00:15:12
- ·Edge case tests in progress; PR expected tomorrow — will complete initial FCR test suite - 00:17:18
Action Items
- •Mikhail Kalinin - Reach out to Panda/Barnabas to merge beacon-metrics PR #22 - 00:19:06
- •Nazar Hussain - Investigate cause of 3 FCR resets on Lodestar node; add debug logging for fallback-to-finality events - 00:23:09
- •Mikhail Kalinin - Investigate current usage of the EL 'safe' block tag by RPC providers - 00:31:13
Key decisions
EL block tag for FCR will reuse 'safe'; introducing a new tag requires hard fork coordination and is deferred until after Glamsterdam
to avoid hard fork coordination, the EL block tag for FCR will reuse 'safe' until after Glamsterdam
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.