Vitalik Buterin wants to create an Ether Leeum as simple as Bitcoin by 2030.
Vitalik Buterin, the co -founder of Ether Leeum, believes in the hinge of the long -term elasticity and scalability of the blockchain, like Bitcoin. In a blog post on May 3, he explained how Ether Lee can be as simple as Bitcoin in five years. Buterin wrote:
“One of the best things about Bitcoin is how beautiful the protocol is.”
According to Buterin, Bitcoin’s minimalist design and simplicity can be accessible, allowing even high school students to identify the concept and architecture of the protocol. Buterin also argued that Simplicity also provides other advantages, such as reducing the cost of new infrastructure production and the cost of maintenance of existing infrastructure and reducing the risk of bugs.
Recent upgrades, such as POS (Stoof-OF Stake) and zero simple non-knowledgeable non-corrugated non-corrupt non-corrugated non-knowledge arguments, have made Etherrium more powerful. But ignoring the simplicity of the design, the cost of Etherrium has been added. Buterin explained:
“Historically, Ether Lee has often did not do this (sometimes because of my own decision), which has contributed to the pursuit of our excessive development expenditure, all kinds of security risks and many R & D culture, and often fantastic benefits.”
Simplification of Ether Leeum Consensus layer
In November, Justin Drake, a researcher at the Etherum Foundation, proposed a consensus layer upgrade called Beam Chain. Buterin thinks that the beam chain is “much simpler” than the current beacon chain, the old -fashioned predecessor.
The beam chain will allow the three slot final re -design to remove complex concepts such as slots, Epoch and Sync Committee, buterin pointed out. He also made it much simpler because he could achieve the basic implementation of the three slot finals through about 200 lines of code.
The beam chain also reduces the number of active validity tests at once, “It is safer to use simpler implementation of fork selection rules.
The beam chain also integrates Stark -based aggregate protocols, so anyone can be a consent. Buterin mentioned:
“The complexity of aggregate encryption itself is important, but at least the complexity of the protocol is much lower.”
Buterin added that the decrease in active validation and the integration of the STARK -based Agrigator will enable the “simpler and more powerful” P2P architecture. He continued to have the opportunity to rethink and simplify various aspects, from the validation tester input to the exit to the non -activity leak. And this can reduce the number of code lines (LOCs) and create “easier to read warranty”.
Buterin emphasized that the consensus layer was “relatively broken” in the EVM (Ethereum Virtual Machine) execution, which provides “relatively wider latitude” compared to the executive layer.
Simplification of Ether Leeum Execution Class
Last month, Burterin proposed to replace the EVM contract language with RISC-V to replace the efficiency up to 100 times. Buterin said that the adoption of RISC-V will increase simplicity because the RISC-V specifications are simple than EVM.
However, this means that compatibility is preserved upside down of existing applications. Buterin wrote:
“The first to understand is that there is no way to describe” Ethereum Codebase “(in a single client).”
According to Buterin, the orange area cannot be reduced. Buterin is to minimize the green area by moving the code to the yellow area. “It’s not part of the agreement in a very valuable code or optimal block building to understand and interpret chains today.” Buterin compares this process to how Apple achieves long -term reverse compatibility through the translation layer. He wrote:
“Importantly, the orange and yellow areas are complexized, and those who want to understand the protocol can skip this, the implementation of Ether Leeum can be freely crossed, and the bugs in that area do not cause consensus.”
Therefore, the code complexity of the orange and yellow regions is “much less downside” compared to the code complexity of greenery.
To reduce green areas, Buterin proposed the following steps.
Step 1: The new pre-compile is written in RISC-V.
Step 2: The developer has an option to write a contract in RISC-V.
Step 3: All dictionary compounds are replaced by RISC-V implementation through hard fork.
Step 4: Implement an EVM interpreter in RISC-V and push onChain with a smart contract.
The above step is that the Ether Leeum Consensus will ensure that only RISC-V will be “understood”, buterin said.
Full standard standard for simplification
Buterin is a path to simplification and suggested sharing a “standard over another part of the stack.”
For example, Buterin has proposed to use a single deletion code for data soluble sampling, P2P broadcasting and distributed history storage. He insisted that it would minimize the total code line, increase efficiency, and ensure the possibility of verification.
Similarly, he proposed a single -shared serialization format of three Etherrium layers (execution layer, consensus layer and Smart Contract Calling Application Binary Interface). Buterin has proposed to use SSZs that are easy to decode and widely used.
Finally, if the EVM is replaced by RISC-V or another simple language, the Buterin suggests that the hexary Merkle Patricia tree will be shifted from the consensus and execution layer to the binary tree. Buterin says that this transition can improve efficiency and use the same code to access and interpret all Ether Leeum layers, while Buterin said.
Mental change
Buterin concluded by suggesting that Ethereum adopts an explicit maximum code target line according to the example of Tinygrad. Buterin is to create “to make Ethereum Consensus-Critical Code as simple as bitcoin.”
But more importantly, Ether Leeum should adopt a spirit that can choose as simple as possible. This means that it prefers encapsulated complexity compared to systemic complexity.
Buterin was convinced that the code dealing with the processing of Ethereum would continue to exist with his latest suggestion. But these code must be maintained outside the consensus critical code or greenery.
