Update PoS overview to add a more on-point lede #6651
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* the intro paragraph/sentence should succinctly state the core idea rather than explaining the building blocks * I don't think consensus mechanism needs to be both defined and linked to * The remainder of the article can explain the building blocks from the ground up
setgree
requested review from
samajammin,
wackerow,
corwintines,
pettinarip and
minimalsm
as code owners
github-actions
bot
added
content 🖋️
setgree
changed the title
Gatsby Cloud Build Reportethereum-org-website-dev 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 30m PerformanceLighthouse report
|
minimalsm
reviewed
Jun 13, 2022
| @@ -5,7 +5,7 @@ lang: en | |||
| sidebar: true | |||
| --- | |||
|
|
|||
| A [consensus mechanism](/developers/docs/consensus-mechanisms/) is a set of rules and incentives that enable nodes to come to agreement about the state of the Ethereum network. There are several different classes of consensus mechanisms that have been implemented on various blockchains, including [proof-of-work (PoW)](/developers/docs/consensus-mechanisms/pow/), proof-of-stake (PoS) and proof-of-authority (PoA). Ethereum has used PoW since its genesis, but is moving to PoS. This was always the plan because PoS is thought to be more secure than PoW, uses drastically less energy, and enables new scaling solutions to be implemented. However, proof-of-stake is also more complex than proof-of-work and refining the mechanism has taken years of research and development. The challenge now is to implement PoS on the live Ethereum network - a process known as ["The Merge"](/upgrades/merge/). | |||
| Proof-of-stake (PoS) is a a [consensus mechanism](/developers/docs/consensus-mechanisms/) that Ethereum is moving to, away from [proof-of-work (PoW)](/developers/docs/consensus-mechanisms/pow/), because PoS is thought to be more secure, less energy-intensive, and better for implementing new scaling solutions. While it has always been the plan to transition to PoS, proof-of-stake is also more complex than proof-of-work, and refining the mechanism has taken years of research and development. The challenge now is to implement PoS on the live Ethereum network. This process is called ["The Merge"](/upgrades/merge/). | |||
There was a problem hiding this comment.
We always spell out proof-of-stake/work fully as per our style guide.
There was a problem hiding this comment.
gotcha 😃 I was following the conventions of the page as I found it, next time I will consult the style guide more closely 🙏
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Related Issue