Buterin talks about the early design shortcomings of Ethereum: wrong EVM standard selection, PoS transformation too late, etc.

This site (120btC.coM): Vitalik Buterin, the founder of Ethereum, said at the ETH Berlin event last week that even though Ethereum is becoming more and more mainstream, people are still concerned about it. It still has a lot of misunderstandings.

At the same time, Buterin also described some regrets about his initial design of Ethereum, involving the development of the Ethereum Virtual Machine (EVM), smart contracts, Ethereum’s PoS proof mechanism, etc., which are summarized as follows:

Ethereum Virtual Machine EVM Development

In terms of Ethereum Virtual Machine development, Buterin stated that the original EVM design chose 256-bit processing instead of 64-bit or 32-bit.

However, the original design was too complex for 256-bit, which is very inefficient and can produce large amounts of redundant data on the blockchain even when performing simple tasks.

Note: The Ethereum Virtual Machine can be understood as a virtual computer running on Ethereum, which can do many things that a physical computer can do, such as executing smart contracts, operating DApps, etc.

Smart Contract Optimization

Secondly, Buterin said that early Ethereum developers should focus on allowing developers to use less and easier code to write smart contracts: With less code, it's easier for people to properly inspect what's going on internally.

Transformation to PoS mechanism

At the same time, Buterin also pointed out that Ethereum will switch from the Proof of Work consensus mechanism (PoW) to the Proof of Stake consensus mechanism (PoS) in 2022 as a historic step. , should be done earlier: We end up wasting a lot of time trying to make Proof of Stake perfect, and when we want to move to Proof of Stake, we should act sooner, even if it means making a worse version. If we do this in 2018, we can save a lot of forestry resources.

Automatic log of Ethereum transfers

V God also added that the automatic log of Ethereum transfers should exist from the beginning: We only need to spend 30 minutes to complete the coding, however, it But it became an EIP.

Selection of Encryption Algorithm

Vitalik finally stated that if he had to choose again, he would use SHA-2 to encrypt Ethereum instead of the currently used one called Keccak Encryption Algorithm.

Despite a series of small design missteps, Vitalik said that is inevitable with any project: "I'm really happy, I feel like our core developers and their ability to execute seem to be improving every year." improve. We now have the ability to effectively and safely correct some of these errors.

The above is the detailed content of Buterin talks about the early design shortcomings of Ethereum: wrong EVM standard selection, PoS transformation too late, etc.. For more information, please follow other related articles on the PHP Chinese website!