Introduction | Beyond the Beacon Chain: Execution Environment in Eth2

Editor's Note: This article is the PPT used by Dr. Robert Drost of the ConsenSys Research Department at the BuildEth SF 2019 conference on the Eth2 Execution Environment.

This section describes the differences between Eth1 and Eth2 in the consensus rule pattern.

In Eth1, the transaction execution framework is hard-coded, so any changes to the consensus rules require hard forks. However, there are differences between the fixed layer and the execution environment layer in Eth2. The former is the rule used by the beacon chain and the fragmented PoS protocol. It is also the rule that defines the eth transfer. The latter defines the transaction and state in a specific execution environment. And state transition rules; the former requires a fork to change, the latter does not.

This section introduces the definition of the Execution Environment (EE), the way in which Eth2's beacon chain works with different EEs.

The execution environment defines the state transition function; the execution environment is defined by the "contract" on the beacon chain; this "contract" is not a smart contract on Eth1, but an executable definition of a blockchain (of course, Must accept the constraints of the beacon chain operating mode).

This section describes the meaning of the execution environment and its practical examples.

The significance of EE is that the beacon chain and the TPS provided by Sharding can be shared between different programmable execution layers. The author also lists many examples of execution environments, such as Eth1.x, UTXO, Layer-2 Checkin, and Rollup.

This section describes the development of the test network for Phase2.

This section also gives a development kit for the execution environment, as well as a brief introduction to the tool.

Original link:

Author: Robert Drost (This article comes from Ethernet Square enthusiasts EthFans, without the permission of the author is forbidden and offenders will study law)