Engineering Sandbox lab ยท distributed consensus

Split the same chain across peers, then watch tampering turn into disagreement.

This view works best after the single-chain demo. Compare Peer A, Peer B, and the attacker row as competing claims about history. The important move is seeing which branch repairs locally, which branch still diverges, and why consensus is more than one valid hash.

Compare peers side by sideWatch disagreement propagateReturn to the main chain when needed
Try this first

Change a block in Peer A, then compare the same block in Peer B before mining anything. Once the histories drift, use the mine buttons to see how hard it is to restore agreement instead of only repairing one branch.

Back to blockchainOpen combined flow

What the peers mean

  • 1
    Peer A is one history proposal you can tamper with directly.
  • 2
    Peer B gives you a clean comparison branch that may keep different data.
  • 3
    The third row makes the consensus problem visible instead of abstract.

Use the layout

This row is horizontally scrollable for the same reason the main blockchain row is: later blocks still matter. Move sideways when the early peer state makes sense so you can keep reading divergence as it propagates.

Distributed Blockchain

Peer A

#
#
#
#
#

Peer B

#
#
#
#
#

Peer C

#
#
#
#
#