Partnered With:

Ethereum Core Developers Propose Eth1 to Eth2 Transition Proposal "Executable Beacon Chain"

Read this article in 3 Minutes

The Eth2 execution model is an alternative to executable shards, supporting a single thread of execution held within the beacon chain.

Rhythm BlockBeats news, on November 27, Ethereum core developer Mikhail Kalinin initiated a transition proposal from Eth1 to Eth2 "Executable Beacon Chain". The Eth2 execution model is an alternative to executable shards, supporting a single thread of execution held within the beacon chain.

Mikhail Kalinin said that the Eth1 shard design assumes communication with data shards via the beacon chain. This approach makes sense if Phase 2 with multiple execution shards will be rolled out later. With a primary focus on a rollup-centric roadmap, putting Eth1 on a dedicated shard (i.e. separate from and often "cross-linking" the beacon chain) would add unnecessary complexity to the consensus layer and increase the Latency between publishing data on a shard and accessing it in Eth1.

He therefore proposes to embed Eth1 data (transactions, state roots, etc.) Beacon proposers remove this complexity by generating executable Eth1 data.

Proposal Overview

Eth1-engine is maintained by each validator in the system.

When a validator intends to propose a beacon block, it asks the Eth1-engine to create Eth1 data. The Eth1 data is then embedded into the body of the beacon block being generated.

If Eth1 data is invalid, it also invalidates the beacon block carrying that data.