Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions book/src/advanced_re-orgs.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,10 @@

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.
Because Lighthouse only does this when the opportunity presents itself and the odds of success are good, the code calls the behaviour “opportunistically re-organising late blocks when proposing.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the last sentence makes it too obvious that the paragraph above was written by a different author 😅 . I think we could could remove the "Since v3.4.0 Lighthouse will opportunistically re-org late blocks when proposing" paragraph altogether, and re-phrase (or remove) this sentence?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed the last sentence.


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.
Expand Down