search

InsideTheSim / ethmerge.com-content

Markdown formatted content for the ethmerge.com website.
https://ethmerge.com
31 stars 37 forks source link

Intro draft #26

Closed Myu-Unix closed 3 years ago

Myu-Unix commented 3 years ago

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"

https://github.com/ethereum/eth2.0-specs/pull/2229

But this has not been merged

It then morphed into PR 2257 / 2280 "Pure consensus upgrade" which has been merged.

https://github.com/ethereum/eth2.0-specs/pull/2257 https://github.com/ethereum/eth2.0-specs/issues/2280

On a PM level it seems tracked here : (Proposal to prioritize The Merge after London) https://github.com/ethereum/pm/issues/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) ?

InsideTheSim commented 3 years ago

Yes - regardless of when it happens this site is meant to educate the community on what the ETH 1.0 -> ETH 2.0 transition looks like and how it does (or does not affect them).

That said - I also hope that this site acts as a resource to gather community support around pursuing the merge as the top priority after the planned summer hardfork. It seems consensus is already headed that way but having a site that answers questions in an easy-to-digest way is a good way to continue to grow that support.

InsideTheSim commented 3 years ago

@Myu-Unix I'm going to go ahead and merge your draft into a feature branch to signal that it's part of the repo but still interested in more robust contribution from the community and discussion about which facets are most important to cover at a high level outside of the FAQs.