Ethereum Foundation

Fast Finality WorkshopCambridge

Agenda

Password

weeping-amuze-bejan-shoelace-burrknot

Scan to open the agenda

Fast Finality Workshop · Cambridge

Open problems

The board

Add anything you’d like to bring up during the open sessions, or things you’d like to challenge.

notes.ethereum.org/yNWbJIsoROGSdT3Nq04Tpw · also linked from the agenda page

Scan to open the board

Fast Finality Workshop · Cambridge

Introductions

  • Your name, and where you work
  • What you are working on
  • What you want to leave Cambridge with
Fast Finality Workshop · Cambridge

Expectations

What we’re doing is very hard

Tuesday · 09:00

Very confused

Mark Rober · Metronome Synchronization Is Like Magic

Thursday · 17:30

Aligned

These are (almost) unique to us.

…but they also require:

Fast Finality Workshop · Cambridge

Context

How we got here, and what’s next

2022 – 2025

Years of research

  • Goldfish
  • RLMD‑GHOST
  • TOB‑SVD
  • 3SF
  • Majorum, …

Oct 2025Cambridge

Not BFT‑only
+ stabilization gadget

Nov 2025Devconnect ARG

First designs validated

Jan 2026Berlin

Strawmap: decouple DC & 1RF

Mar 2026ethresear.ch

DC goes public

Oct 2026Cambridge

Converge

You are here

3–6 Nov 2026Mumbai

Devcon

In three weeks, in front of core devs

Could startsoon

I* headliner selection

So, this week

  • Don’t give core devs something unready to look at.
  • Add Lindy-ness to the right thing.
Fast Finality Workshop · Cambridge

Programming

Three days, three objectives

  • DC design Objective 1
  • Shipping DC & open sessions Objective 2
  • Future of fast finality Objective 3
  • Formal verification
  • Admin & misc
13

Tuesday

The design, part one · consensus & networking

  1. 09:00Intro
  2. 09:30DC consensus: overviewRoberto
  3. 11:30DC consensus: GoldilocksFrancesco
  4. 14:00Goldilocks, continuedFrancesco
  5. 15:00DC networking: design & benchmarkingSukun
  6. 16:30PQ networkingKev & Kamil
  7. 17:00Open session I
14

Wednesday

The design, part two · future of fast finality

  1. 09:00Recap
  2. 09:15Open sessions II–III · consensus
  3. 11:30IncentivesAnders
  4. 14:00Specs & prototypingMikhail, Justin & Thomas C
  5. 14:30The transitionMikhail & Justin
  6. 14:45PQ networkingKev & Kamil
  7. 15:15Lean clientsMihir, Mega, Pablo & Locki
  8. 15:45Tens-of-seconds PQ finalityBarnabé
  9. 17:00Open sessions IV–V · networking
15

Thursday

The road to review

  1. 09:00Formal verification · with the FV workshopRoberto, Francesco & Alex
  2. 14:00One-round finalityFrancesco & Yann
  3. 14:30Open session VI
  4. 15:00ACDC
  5. 17:00Security reviewYann
  6. 17:15Synthesis
  7. 17:30Conclusions · working group, commitments, next steps
Fast Finality Workshop · Cambridge

Reminder

Why we need decoupled consensus

Post-quantum readiness

A small committee signs with post-quantum signatures as they are. The heartbeat goes PQ first; finality follows.

Fixing Gasper

A dynamically available, reorg-resilient chain in place of LMD-GHOST, cleanly separated from finality.

Fast finality

Finality runs in parallel, off the critical path, so slots and finality no longer trade off.

Fast Finality Workshop · Cambridge

Starting point

Decoupled consensus, as it stands

Let’s see how much stays the same — and how much we can improve.

finality.watch

I’ll try to track the protocol here as it evolves.

One transaction, from inclusion to finality

≈ 3m 48sexpected · today ≈ 16 min

included
Inclusion6 sec
Confirmation12 sec
Wait for its round54 sec
Justification1m 12s
Finalization1m 24s

Expected values · finality.watch “DC today” model · ~1.1M validators · 12-second slots

Fast Finality Workshop · Cambridge

Goals

A henohenomoheji face standing in for Ben
BenModerator · product owner of DC