ethereum-org-website icon indicating copy to clipboard operation
ethereum-org-website copied to clipboard

Add Quiz on Ethereum Merge & Proof of Stake

Open dinitheth opened this issue 9 months ago • 7 comments

Page URL

https://ethereum.org/en/roadmap/merge/

Question content

Proof of Stake & The Merge

1. What was the main goal of The Merge?

Correct Answer: B. To transition Ethereum from Proof of Work to Proof of Stake Explanation: The Merge was Ethereum’s upgrade to switch from energy-intensive mining (Proof of Work) to Proof of Stake, which is more environmentally friendly.

Incorrect Answers with Explanation:

A. To increase the Ethereum block size → The Merge did not change block size; it changed the consensus mechanism. C. To create a new Ethereum token → No new tokens were created; ETH remained Ethereum’s native currency. D. To improve Bitcoin’s consensus mechanism → The Merge was specific to Ethereum and had no impact on Bitcoin.

2. How did The Merge affect Ethereum’s energy consumption?

Correct Answer: C. It reduced Ethereum’s energy use by approximately 99.95% Explanation: By eliminating mining, The Merge drastically reduced Ethereum’s electricity consumption.

Incorrect Answers with Explanation:

A. It increased energy use due to higher block production → Ethereum’s energy use significantly decreased, not increased. B. It had no impact on energy consumption → False; Ethereum’s switch to staking cut energy consumption drastically. D. It doubled Ethereum’s transaction fees → Transaction fees depend on demand and block space, not The Merge.

3. What mechanism secures the Ethereum network after The Merge?

Correct Answer: B. Proof of Stake Explanation: Proof of Stake replaced mining and now validators secure the network by staking ETH.

Incorrect Answers with Explanation:

A. Proof of Work → Ethereum abandoned Proof of Work with The Merge. C. Delegated Proof of Stake → Ethereum uses traditional Proof of Stake, not a delegated system like EOS. D. Hash Power → Hash power is used in Proof of Work, which Ethereum no longer uses.

4. How much ETH is required to run a full validator node?

Correct Answer: C. 32 ETH Explanation: A validator node requires a minimum of 32 ETH to participate in Ethereum staking. However, with EIP-7251 (MaxEB) introduced in the Pectra upgrade, validators will be able to stake more than 32 ETH in a single validator, allowing for greater efficiency.

Incorrect Answers with Explanation:

A. 1 ETH → 1 ETH is not enough to run a validator node. B. 16 ETH → Ethereum does not have a 16 ETH requirement for validators. D. 64 ETH → Validators will be able to stake more than 32 ETH with EIP-7251, but 32 ETH is still the minimum required to run a validator.

5. What is a validator in Proof of Stake?

Correct Answer: B. A node operator who stakes ETH to propose and validate blocks Explanation: Validators replace miners in Ethereum’s Proof of Stake system by staking ETH and validating transactions.

Incorrect Answers with Explanation:

A. A miner who finds new blocks → Mining no longer exists in Ethereum. C. A user who sends transactions → Users send transactions but do not validate blocks. D. A blockchain developer → Developers build applications but do not validate transactions.

Would you like to work on this issue?

  • [x] Yes
  • [ ] No

dinitheth avatar Feb 14 '25 21:02 dinitheth

This issue is stale because it has been open 30 days with no activity.

github-actions[bot] avatar Mar 17 '25 08:03 github-actions[bot]

Thanks for submitting the quiz, @dinitheth!

@wackerow can you please review the content and let us know the next steps?

isabelladebrito avatar Mar 21 '25 00:03 isabelladebrito

Thanks @dinitheth

Overall these seem good. I would maybe consider the changes coming in Pectra and how they will affect question 4. https://eips.ethereum.org/EIPS/eip-7251 this EIP will maybe any balance above 32ETH a valid.

corwintines avatar Mar 24 '25 20:03 corwintines

Thanks @corwintines I appreciate your suggestion!

dinitheth avatar Mar 25 '25 16:03 dinitheth

General style note:

"Proof of Work" -> "proof-of-work" (https://ethereum.org/en/contributing/style-guide/content-standardization/#proof-of) (no special capitalization, hyphenated; same with "stake")


like EOS.

would drop

B. It had no impact on energy consumption → False; Ethereum’s switch to staking cut energy consumption drastically.

Can probably drop "False;" from the explanation here

However, with EIP-7251 (MaxEB) introduced in the Pectra upgrade, validators will be able to stake more than 32 ETH in a single validator, allowing for greater efficiency.

Love the Pectra additions, but feels extraneous to the explanation of the correct answer. The question is about min ETH to run a validator, which is 32 and Pectra does not change.

Having this in the explanation for the "64" answer choice makes more sense.

If we want to include more information around Pectra changes, would suggest an additional question about it.

Validators will be able to stake more than 32 ETH with EIP-7251, but 32 ETH is still the minimum required to run a validator.

And on that note, let's future-proof the copy a touch.. instead of "will be able to" would recommend something like:

"EIP-7261 enables validators to stake up to 2048 ETH, but 32 ETH is still the minimum required to run a validator."

What is a validator in Proof of Stake A node operator who stakes ETH to propose and

Some nuance I'll request out of this... "validator" is effectively an account, with a pub key, index number, balance, and status... If we can, let's try to separate that concept from the human "node operator" who controls hardware/software, and also sometimes the "staker" who provides ETH to be locked in the proof-of-stake system.


Otherwise this is looking great and welcome a PR to move it along! Nice job @dinitheth, have assigned

wackerow avatar Mar 28 '25 00:03 wackerow

Hey @dinitheth! Thank you so much for your contribution - would you still be able to look at the comment above and submit the PR? Let us know!

isabelladebrito avatar Apr 24 '25 13:04 isabelladebrito

This issue is stale because it has been open 30 days with no activity.

github-actions[bot] avatar May 25 '25 08:05 github-actions[bot]