Introduce heterogeneous vocabulary for Consensus layer/Beacon Chain

[SebastianSupreme]

Repurposed extension of #10356

[gatsby-cloud]

✅ ethereum-org-website-dev deploy preview ready

• Deploy preview
• Build logs · 39m build time

[wackerow]

Hey @SebastianSupreme, thanks for dropping this! To my knowledge, despite using the terms "consensus" and "execution" to refer to these layers and client types, we do still use "Beacon Chain" in the consensus specs.
@djrtwo Any thoughts here? Is this a term the devs are trying to deprecate entirely?

[jmcook1186]

btw there was some discussion around this at merge-time. It was inconclusive, but the arguments are at least laid out in the issue description: #7828

[SebastianSupreme]

Considering that the page about the Beacon Chain speaks of it in past tense, indicating that it doesn't exist anymore, we should be consistent with this and remove the name from pages which are meant to explain Ethereum in simple terms in order to avoid any confusion for new readers (e.g. the staking pages).
Pages which do include a more technical terminology may continue to refer to the Beacon Chain for now because I'm aware that the consensus specs contain remains of Beacon Chain terminology as well.

[SebastianSupreme]

@corwintines Can we merge this now? According to the linked discussion, most people are in favor of this change.

[wackerow]

I personally disagree with removing the Beacon Chain terminology, but I do agree that the wording presented on the /roadmap/beacon-chain/ pages is poor. To my knowledge, the intent of rewording the "tense" on that page after upgrades were checked off was not to imply that the Beacon Chain no longer existed. The intro appears to try to tell a story of when the Beacon Chain started, but it definitely gives a tone that it no longer exists.

I'd be more in favor of correcting the tense surrounding this copy than to remove the name "Beacon Chain", which the page has always been named, in included in the URL, and is still used in the specs.

[corwintines]

I agree with @wackerow. @SebastianSupreme would you be interested in updating this instead?

[SebastianSupreme]

So, it seems like I was wrong and the Beacon Chain does still exist as Ethereum's consensus layer but has been modified compared to the pre-merge Beacon Chain. But even so, it still keeps its name after those updates and after being given the purpose to be Ethereum's consensus layer.

I'd be happy to rewrite the Beacon Chain page accordingly and remove the confusion that is caused by the past tense wording.

[jmcook1186]

yea i agree - I feel like the window for updating terms has kind of closed now being so far post-merge. BC has persisted and is pretty well embedded now. No need to purge the term from the site generally. That said, I still prefer @SebastianSupreme 's updates using consensus layer in most cases tbh.

@SebastianSupreme if you want to try to clarify the page then please go ahead and raise a PR, happy to go along with the consensus here.

[SebastianSupreme]

@jmcook1186 suggested using consensus layer instead of Beacon Chain whenever it is mentioned elsewhere and those changes are already included in this PR here.
@corwintines @wackerow What do you guys think?
If everyone agrees on this we could just use this PR for that.

[corwintines]

@SebastianSupreme could you fix conflicts here, ill pull in after :) Thanks!

[SebastianSupreme]

@corwintines should be good to go now

[minimalsm]

@jmcook1186 @wackerow please review and confirm we're happy here 😀 (either or, don't need you both to review, i don't think...)

[wackerow]

Lgtm, just left one small suggestion but not critical
cc: @corwintines