Blockchain Security Training Consensus Mechanism Vulnerabilities 3 — Questions and Answers
Question 1: The 'nothing-at-stake' problem in early Proof-of-Stake designs refers to what?
- Validators having no funds to stake
- Validators being able to vote on multiple competing chains at no cost (Correct answer)
- Stakers losing internet connection
- Tokens having no market value
Correct answer: Validators being able to vote on multiple competing chains at no cost
Without penalties, validators can cheaply sign every competing fork, undermining consensus because they lose nothing by backing multiple chains.
Question 2: How does 'slashing' address Proof-of-Stake misbehavior?
- By increasing rewards for all validators
- By destroying a portion of a misbehaving validator's staked funds (Correct answer)
- By slowing down block production
- By encrypting validator messages
Correct answer: By destroying a portion of a misbehaving validator's staked funds
Slashing penalizes provably malicious actions, such as double-signing, by burning part of the offender's stake, deterring attacks.
Question 3: A 'grinding attack' in PoS attempts to manipulate what?
- The transaction mempool ordering
- The validator/leader selection randomness in the attacker's favor (Correct answer)
- The gas fee market
- The wallet backup process
Correct answer: The validator/leader selection randomness in the attacker's favor
Grinding attacks bias the pseudo-random leader-election process so the attacker is chosen more often than chance allows.
Question 4: Why is verifiable random function (VRF) based leader selection preferred in modern PoS?
- It uses less storage
- It produces randomness that is unpredictable yet publicly verifiable (Correct answer)
- It eliminates the need for staking
- It speeds up signature checks
Correct answer: It produces randomness that is unpredictable yet publicly verifiable
VRFs let validators prove their selection was legitimately random without letting anyone predict or manipulate the outcome in advance.
Question 5: A 'stake centralization' risk in PoS arises primarily when:
- Block times become too fast
- A small number of entities or staking pools control most of the stake (Correct answer)
- Validators run open-source software
- Gas fees are too low
Correct answer: A small number of entities or staking pools control most of the stake
If a few staking pools dominate, they can collude to censor or reorganize, weakening the decentralization that secures consensus.
Question 6: What does 'weak subjectivity' require of a new PoS node joining the network?
- Mining a genesis block
- Trusting a recent, reliable checkpoint to avoid long-range attacks (Correct answer)
- Buying the maximum amount of stake
- Disabling its firewall
Correct answer: Trusting a recent, reliable checkpoint to avoid long-range attacks
New or long-offline nodes must obtain a recent trusted checkpoint so they don't accept a fraudulent rewritten history from old keys.
Question 7: Inactivity leak in PoS chains like Ethereum is designed to do what?
- Reward offline validators
- Gradually reduce stake of offline validators so the chain can regain finality (Correct answer)
- Speed up block gossip
- Compress the blockchain state
Correct answer: Gradually reduce stake of offline validators so the chain can regain finality
If too many validators go offline, the inactivity leak slowly drains their stake until active validators again form a supermajority and finalize blocks.
Blockchain Security Training Consensus Mechanism Vulnerabilities 3
The 'nothing-at-stake' problem in early Proof-of-Stake designs refers to what?