From 4fc0665ccdd6a317d6c1220ca9ccee79ad325c1d Mon Sep 17 00:00:00 2001 From: diegomrsantos Date: Sat, 14 Jun 2025 05:45:35 +0200 Subject: [PATCH] Add more context to Late Block Re-orgs (#7592) Giving more context about late block re-orgs would make the concept easier to grasp for newcomers. Add more context to this section in the Lighthouse Book. --- book/src/advanced_re-orgs.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/book/src/advanced_re-orgs.md b/book/src/advanced_re-orgs.md index fca156bda3..3a31778786 100644 --- a/book/src/advanced_re-orgs.md +++ b/book/src/advanced_re-orgs.md @@ -2,6 +2,9 @@ Since v3.4.0 Lighthouse will opportunistically re-org late blocks when proposing. +When Lighthouse is about to propose a new block, it quickly checks whether the block from the previous slot landed so late that hardly anyone attested to it. +If that late block looks weak enough, Lighthouse may decide to “re-org” it away: instead of building on it, Lighthouse builds its new block on the grand-parent block, turning the late block into an orphan. + This feature is intended to disincentivise late blocks and improve network health. Proposing a re-orging block is also more profitable for the proposer because it increases the number of attestations and transactions that can be included.