Vitalal Buterin calls on Ethereum to take up Bitcoin -style simplicity over the next five years

Vitalal Butterin said Ethereum had to give up that pretending it was okay. On Friday, he announced a long proposal calling for Ethereum to cut out its overflow guts and move closer to the clean structure of Bitcoin for five years.

“Ethereum wants to be the general ledding of the world,” Vitalal wrote, pointing to his role as a base layer of crypto, finance, management, authentication and records. But in reality, he said that the chain must be both scalable and durable – and now it is too difficult to handle it.

Fusaka hard fork should increase the L2 data space by 10x. Ethereum's 2026 Action Plan promises to increase the L1 data. The network had already been replaced to prove its stake, improved customers' diversity and is engaged in ZK's control and quantum resistance.

But Vitalik said it didn't matter if the main protocol remains bloated. “We have to illuminate the importance of simplicity,” he wrote. He pointed to Bitcoin's design – blocks, hips, work proof and nothing else – as the model Ethereum should follow.

Vitaly requires a simpler ethereum consensus layer

Vitalal said that Ethereum could get there by writing around his consensus layer. He wants to replace the current lighthouse chain with a so-called 3-plot-ending, which would remove slots, eras, mixing the Commission and other moving parts.

“You could build it in 200 codes of code,” wroteTo. He said it offers strong security and removes a lot of bloating from the system. Smaller validator kits also make the fork choice rule easier.

He said that Ethereum should use a star -based redundancy so that everyone could be a concentrator without the need for special trust or Bitfields. Cryptography is complex, but it is in the box and does not screw the entire system. It opens the door to a simpler peer-to-peer layer.

Validation functions – such as entry, exit, withdrawal, main changes and leakage of inactivity – should be rebuilt to reduce the number of lines and make the system warranty more easily readable. Vitalik said that the best part of the consensus is that it is not closely connected to the filling layer, so that it could develop without breaking the contracts.

But the real mess is, he says, a virtual machine on Ethereum.

Vitalik wants to kill EVM and move to RISC-V

Vitalal said the EVM was filled with an outdated mess. He called it an over-built 256-bit machine that was optimized for cryptocurrencies that nobody uses anymore. He admitted that most of the complexity came from his own choices.

The fight to remove spontaneous learning was a waste of time. So was the whole EOF discussion. His solution: Skip small version updates and just replace EVM.

He proposed to exchange RISC-V or some or other Cairo-Sama, which is used by Ethereum's zero-knowledge evidence. “Short data show that it can increase efficiency by 100x,” he said. Simpler data would mean faster filling and less errors.

Developers would get more opportunities. Gym and Vyper compile for new or other devils, and the users using the usual programming language could first write ethereum contracts. Most pre -compilers can be demolished, except for elliptical curves OPs.

Vitalik admitted that RISC-V was not ready tomorrow. While waiting, he wants to convey fast version updates to the current EVM, such as to increase the size of the contract and add new DUP/Swap Opcode. But the real goal is to replace the whole thing. His plan comes in four steps.

First, every new pre-compilation must be with the RISC-V version. Secondly, developers should be allowed to write contracts in both RISC-V and EVM. Third, Ethereum would make a hard fork to remove the pre-components and replace them with RISC-V contracts. Fourthly, the EVM will be re-implemented RISC-VS and would travel as a contract translator.

Vitalik said that Ethereum was also wasting the use of different tools in different places in different places. He pointed to the deletion codes necessary for the availability of data, P2P -Lev and history. All three should use the same code. The same goes for serialization formats – Ethereum should completely move SSZ, which is already in use in the consensus layer and works within smart contracts.

He also said that the Ethereum Merkle Tree also sucks. The current hexaar structure hardens the block. Switching to a binary binary tree with a better hassle would make it faster and cheaper. This same binary trees should be used for both execution and consensus.

Cryptopolitan Academy: Are you tired of market changes? Here's how Defi helps you build a permanently passive income. Sign up right now