Lesson 2 Quiz: Validator Roles and Duties
1) What are the two core responsibilities of a Proof‑of‑Stake validator?
Propose blocks and attest (vote) on others’ blocks.
2) In Ethereum, what information does an attestation vote on each epoch?
Source, target, and head votes (FFG source/target + LMD‑GHOST head).
3) What triggers the inactivity leak on Ethereum, and whom does it penalize?
Extended lack of finality; it penalizes validators not making correct FFG votes (inactive/incorrect) until finality is restored.
4) Name two slashable offenses for Ethereum validators.
Double proposal (two blocks in the same slot) and double vote (conflicting FFG attestations). Surround vote is also slashable.
5) What are the two main reward streams for Ethereum validators and which role primarily earns each?
Consensus‑layer issuance (earned by validators performing duties) and execution‑layer fees/MEV (primarily to block proposers).
6) What is the purpose of sync committees on Ethereum?
Provide signed headers for light clients, enabling efficient, trust‑minimized syncing.
7) In Tezos (Tenderbake), what are the two phases of block validation and why are both used?
Pre‑attestation then attestation; this two‑step process supports fast, deterministic BFT‑style finality.
8) How does Tezos’ native delegation in LPoS affect who can participate in securing the network?
Anyone can delegate without giving up custody, broadening participation via bakers.
9) Which behaviors are slashable on Tezos, and what is typically not slashable compared to Ethereum?
Double baking and double endorsing are slashable; simple downtime is typically not (missed rewards instead), unlike Ethereum’s inactivity leak.
10) What is proposer‑builder separation (PBS)/MEV‑Boost and how can it impact validator rewards and centralization risks?
It separates block building from proposing, potentially increasing MEV capture for proposers but introducing builder centralization risks.