Popular Science: Design Choices of Ethereum 2.0
Editor's Note: This article is from:Ethereum enthusiasts (ID: ethfans)Editor's Note: This article is from:
Ethereum enthusiasts (ID: ethfans)
Ethereum enthusiasts (ID: ethfans)
, Author: ditya Asgaonkar, reprinted with authorization by Odaily.
This article is the slides of researcher Aditya Asgaonkar's speech at the EthCC conference. According to his own statement, it is to explain the design of Eth2 to smart contract developers and what changes the developer's development experience will have. In his speech, he clearly outlined the basic architecture of Eth2 and the design challenges of Eth2.
The explanations and subsections of the contents of the slides in the text were added by the editor.
In this paragraph, the author points out that the two major design goals of Ethereum 2.0 are scalability and security.
The former means that the throughput increases super-linearly. If the input of node resources is increased by K times, the throughput of the entire system will increase by more than K times.
The latter implies security corresponding to the consensus formed by the nodes, ensuring that all parts are equally secure.
The latter is implemented with sharding (splitting the state of the entire system to form different shards), while the former is implemented with the beacon chain.
But with the combination of the two, the beacon chain cannot save all shard data and execute all shard transactions, otherwise it will break the scalability requirements.
Therefore, the division of labor between the two is that the beacon chain is responsible for consensus, only saves the Merkle root of the shard state, and does not execute shard transactions; shards do not have any consensus mechanism, and only randomly selected verifiers come out to produce blocks , validate and commit the Merkle root to the beacon chain.
