Fast Confirmation Rule #006
Transcript
- Mikhail Kalinin
- Mercy Boma Naps-Nkari
Hello
- Roberto Saltini
Wrong reaction! I thought that it was a wave emoji, not a clapping emoji :D
- Mikhail Kalinin
lol
- Barnabas
nitpick but any reason CONFIRMATION_BYZANTINE_THRESHOLD is a config and not a preset? Do we expect to tune this value in devnets, or should we assume that its gonna stay 25 going forward ?
- Barnabas
Thanks
- Will Corcoran
And all of the backtesting / analysis is based around 25, right?
- Mikhail Kalinin
- Mikhail Kalinin
- Mikhail Kalinin
- Mikhail Kalinin
- Mikhail Kalinin
- Mikhail Kalinin
https://github.com/status-im/nimbus-eth2/releases/tag/v26.3.1
- Luca Zanolini
Reacted to "https://github.com/s..." with 🔥
- Will Corcoran
Reacted to "https://github.com/s..." with 🔥
- mushow
Reacted to "https://github.com/s..." with 🔥
- Barnabas
whats the holdup in merging this in?
- Barnabas
sounds good
- mushow
Do we have a timeframe for when to expect client teams to have it implemented? After merging it
- mushow
I’d also like to start reviewing client implementations
- Barnabas
nimbus should have a stable release already no?
- mushow
Reacted to "nimbus should have a..." with 👍
- Mercy Boma Naps-Nkari
- mushow
Reacted to "https://github.com/g..." with 🙏
- Barnabas
Lots of CL teams are full steam working on epbs.
- mushow
Reacted to "Lots of CL teams are..." with 👍
Call summary
Targets
- •ePBS devnet-2 launch targeted for next week - 00:03:00
Highlights
- Spec Status:
- ·FCR spec PR in final review; Gloas support deferred to follow-up PR - 00:09:41
- ·FFG conflict check tightened to strict inequality (>1/3 vs ≥1/3) - 00:14:03
- ·Restart condition now checks block epoch, not checkpoint epoch - 00:15:22
- ·FCR store abstraction separated from main fork choice store - 00:16:39
- ·Optimistic sync handling added: won't confirm unvalidated EL blocks - 00:17:02
- Client Updates:
- ·Grandine FCR PR validated end-to-end with Lodestar on devnet - 00:06:27
- ·Nimbus v26.3.1 released with FCR enabled by default - 00:18:42
- ·Lighthouse and Lodestar have ready-to-go implementations awaiting spec merge - 00:27:55
- ·ePBS work prioritized across CL teams; FCR implementations on hold - 00:29:32
- Organizational:
- ·Client implementer approvals needed to merge FCR spec PR - 00:19:14
- ·Gloas-compatible FCR requires fork choice abstraction changes first - 00:31:17
- Testing Progress:
- ·Backtesting confirms ~1-month mainnet analysis matches PR performance estimates - 00:21:00
Action Items
- •CL client teams - Review and approve FCR spec PR #4747 - 00:19:36
- •Reviewers (in progress) - Provide feedback on FCR technical paper - 00:23:10
Key decisions
Gloas support deferred to follow-up PR
FCR spec PR is in final review; Gloas support will be addressed in a subsequent update.FFG conflict check tightened to strict inequality (>1/3 vs ≥1/3)
Technical refinement of the FCR specification logic.Restart condition now checks block epoch, not checkpoint epoch
Technical adjustment to how FCR handles restart conditions.FCR store abstraction separated from main fork choice store
Architectural decision to decouple FCR storage from the primary fork choice store.Optimistic sync handling added: won't confirm unvalidated EL blocks
Safety measure to ensure FCR does not confirm blocks that have not yet been validated by the Execution Layer.Nimbus v26.3.1 released with FCR enabled by default
Client-specific decision to enable FCR functionality by default in the latest release.ePBS work prioritized across CL teams; FCR implementations on hold
Strategic organizational decision to prioritize ePBS development, resulting in a pause for FCR implementation work.