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.
Here's the PR dedicated to the Intro draft. I have been able to find sources for more points but not all, so still a bit work in progress, hopefully others can chime in as well :)
Another thing we (the community) need to make clear about this intro (and site overall imho) is which "Merge" are we referring to ? The official ethereum.org doesn't really talk about "The Merge" but the docking and rightly so since I believe we are gathered here to shine some light on the various very recent "Quick Merge" proposals which popped up (Maybe in result of the EIP-1559 hostility)
Initially this PR was the spark : PR 2229 "Executable beacon chain / The Merge"
ethereum/consensus-specs#2229
But this has not been merged
It then morphed into PR 2257 / 2280 "Pure consensus upgrade" which has been merged.
ethereum/consensus-specs#2257
ethereum/consensus-specs#2280
On a PM level it seems tracked here : (Proposal to prioritize The Merge after London) ethereum/pm#278
I'll keep digging to hopefully make it clear in the intro but does the rest of the community agree on the scope/PR involved (and thus to be tracked) ?