Fast Confirmation Rule #008
Transcript
Ask about this call
Answered from this call's summary and transcript only.
AI-generated — verify against the recording.
Call summary
Decisions
- •FCR Beacon API event sends only the tip of the confirmed chain, not an event per confirmed block — 00:15:38
- •FCR call in 2 weeks skipped by default; async Telegram updates instead — 00:33:14
Highlights
- Spec Updates:
- ·PR #5288: reconfirmation validation changed to check checkpoint is in confirmed block's chain, not just block ancestry — 00:09:03
- ·PR #5249: makes FCR compatible with Gloas and future Gloas-based forks; FCR tests passing with this PR — 00:12:05
- Organizational:
- ·Next call in 2 weeks skipped by default (Mikhail on vacation); async updates in Telegram instead; reconvene in 4 weeks — 00:32:15
- Api And Metrics:
- ·Beacon API PR #611: FCR event emits only tip of confirmed chain, not every confirmed block — 00:15:23
- ·Beacon metrics PR #22: proposes standardized FCR metrics (reorgs, fallbacks, restarts, confirmed slot, duration) — 00:16:54
- Testing Progress:
- ·Plan to disable BLS in FCR tests to speed up test generation; no functional impact expected — 00:13:43
- ·After PRs #5249 and #5288 merge, FCR tests will be enabled for Gloas and Haze forks — 00:13:48
- Research And Monitoring:
- ·Public Grafana dashboard live showing FCR performance from a Lighthouse node; ~97% same-slot confirmation rate — 00:19:13
- ·EthPandaOps FCR simulator published: no reorged/orphaned slots were fast-confirmed across historical mainnet data — 00:20:55
Action Items
- •All client teams — Review beacon-metrics PR #22 and provide feedback on proposed standardized FCR metrics — 00:16:54
- •samcm (EthPandaOps) — Implement chain-walking logic in dashboard to correctly display all confirmed blocks between events — 00:27:56
Meeting chat27
- Mikhail Kalinin
2 mins and we will start
- Mikhail Kalinin
- Mikhail Kalinin
- Justin Traglia
Hmm I renamed the title. Is my change accurate?
- Justin Traglia
Replying to "Hmm I renamed the ti..." Ah no. It’s not. Will fix later.
- Mikhail Kalinin
- Justin Traglia
Soon.
- Jihoon
Replying to "https://github.com/ethereum/consensus-specs/pull/5249" Will give it another round of review today
- Mikhail Kalinin
- Mikhail Kalinin
- Mercy Boma Naps-Nkari
beacon_fast_confirmation_enabled , beacon_fast_confirmation_confirmed_slot , beacon_fast_confirmation_confirmed_lag_slots , beacon_fast_confirmation_advances_total, beacon_fast_confirmation_resets_total, beacon_fast_confirmation_duration_seconds
- Mercy Boma Naps-Nkari
This is what I have implemented
- samcm
https://grafana.observability.ethpandaops.io/public-dashboards/6016259683994b79b0ed2edade33dd3e
- mushow
Reacted to "https://grafana.obse..." with 🔥
- Mercy Boma Naps-Nkari
Reacted to "https://grafana.obse..." with 🔥
- Mikhail Kalinin
Reacted to "https://grafana.obse..." with 🔥
- samcm
- Justin Traglia
Reacted to "https://grafana.obse..." with 🔥
- Roberto Saltini
Reacted to "https://grafana.obse..." with 🔥
- mushow
Reacted to "https://ethpandaops...." with 🔥
- Mikhail Kalinin
Reacted to "https://ethpandaops...." with 🔥
- Justin Traglia
Reacted to "https://ethpandaops...." with 🔥
- Mikhail Kalinin
Replying to "beacon_fast_confirma..." thank you!
- Luca Zanolini
Reacted to "https://ethpandaops...." with 🔥
- Mercy Boma Naps-Nkari
Reacted to "https://ethpandaops...." with 🔥
- Mikhail Kalinin
beacon_fcr_slot
- Justin Traglia
Sounds good to me
Key decisions
FCR Beacon API event sends only the tip of the confirmed chain, not an event per confirmed block
This change is made to improve the efficiency of the FCR Beacon API event.FCR call in 2 weeks skipped by default; async Telegram updates instead
This decision is made due to Mikhail's vacation and the need for async updates in Telegram.