FABRKNT
Consensus Engineering — Building L1 Consensus on Reth
Reading real consensus code
Lesson 8 of 12·QUIZ10 min40 XP

Treat this page as a workbench, not a blog post. The goal is to extract a reusable mental model from the source and carry it into the rest of the Fabrknt stack.

Course
Consensus Engineering — Building L1 Consensus on Reth
Lesson role
QUIZ
Sequence
8 / 12

Quiz — Reading consensus internals

Question

Recap the four code-reading lessons: Reth Consensus trait, Malachite Driver / VoteKeeper / Context, bera-reth Proof-of-Liquidity.

Principle (minimum model)

  • Reth Consensus trait. ~6 methods; stage-integrated (HeaderStage / BodyStage / ExecutionStage). Custom L1s implement + register via NodeBuilder.
  • Malachite. Driver (state machine) + VoteKeeper (vote tally + equivocation) + Context (host interface). Same shape as any classical BFT.
  • bera-reth. PoL = validators picked by LP positions; demonstrates Reth SDK consensus customisation.

Worked example + steps

Quiz: reading consensus internals

Short test on what you've read in this module. No fluency answers — every question maps to a specific source file or design choice.

Summary (3 lines)

  • Eight questions across reading the three real consensus codebases.
  • Get three or more wrong → re-read the relevant lesson before moving on.
  • Pass → Module 3: build consensus on Reth (NodeBuilder slot, minimal BFT, validator economics).