BC4: How a shared ledger agrees: blocks, consensus and finality

Lesson 3 of 5 · reading 15–25 minutes; practice and project time is on the module page

Proof of stake

🎯You'll be able to

Explain how proof of stake chooses blocks, how dishonesty is punished, and how Ethereum uses it.

🏠The everyday picture

Members who want to keep the register must leave a deposit with the group. Caught writing two different pages at once, they lose part of it.

📘What it really is

📝A worked example

Input: a validator on Ethereum signs two different blocks for the same slot.

Steps:

  1. Another validator notices the two signed blocks and submits them as evidence.
  2. The protocol slashes the dishonest validator: part of its stake is destroyed and it's forced to leave.
  3. Honest validators continue; the network keeps one chain.

Expected output: dishonesty costs more than it can gain, as long as enough stake is honest.

🌍Where it's used

📝Case scenario

A staking provider ran the same validator keys on two machines "for backup". Both signed blocks for the same slot, and the validators were slashed. The lesson: a validator's key must sign from one place, with safeguards against double signing.

🖱️Try it

How many slots happen in one hour on Ethereum? Success: 300, at one every 12 seconds.

⚠️Common mistakes

🛠️For your project

The practice network doesn't use stake: one node makes blocks at once. Project 3's notes should say confirmations behave differently on a public network.

✅Quick check

What is slashing?

Show the answer

Destroying part of a validator's stake when it signs conflicting blocks or votes.

About how long does an Ethereum block usually take to become final?

Show the answer

About two epochs, roughly 13 minutes.

← PreviousProof of work
ProLearners Assist