Vitalik outlines the Ethereum execution layer roadmap, focusing on changes to the state tree and the virtual machine.

ETH-3,3%

PANews March 2 News: Ethereum co-founder Vitalik Buterin posted on social media outlining the Ethereum execution layer roadmap, focusing on two major changes: the state tree and the virtual machine. Regarding the state tree, Vitalik supports upgrading the current hexadecimal Merkle Patricia tree to a binary tree based on a more efficient hash function through EIP-7864. This change can reduce Merkle branch length by four times, lowering client verification bandwidth costs; at the same time, the hash function can be replaced with Blake3 or Poseidon series, significantly improving proof efficiency. The binary tree design will also group storage slots into “pages,” reducing access costs for adjacent storage, saving over 10,000 Gas per transaction in many DeFi applications. Additionally, the binary tree structure is simpler and reserves metadata bits for future state expiration features.

On the virtual machine side, Vitalik proposes a long-term direction to replace the EVM, potentially adopting a RISC-V architecture. The new VM must meet four goals: higher raw execution efficiency to eliminate most precompiles; better proof efficiency than EVM; support for client-side generation of ZK proofs; and maximum simplification of code implementation. He notes that if Ethereum remains at the “EVM + GPU” level, it is “good enough,” but a better VM can make the protocol more powerful. The deployment roadmap consists of three steps: first, the new VM will replace precompiles; then, users will be allowed to deploy contracts based on the new VM; finally, the EVM will be retired, replaced by smart contracts written for the new VM, achieving full backward compatibility.

Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.

Related Articles

A whale opens 20x leverage BTC and ETH short positions, with a position value of about $80 million

Gate News said that on April 9, according to Lookonchain monitoring, a whale address opened 20x leveraged BTC and ETH short positions about 30 minutes ago. Among them, the Bitcoin short position holds 562.58 BTC, and the Ethereum short position holds 18,350 ETH; the total value of the two positions is about $80 million.

GateNews58m ago

BlackRock ETHA fund transferred nearly 20k ETH to a certain CEX Prime address

Gate News, April 9, Arkham monitoring data shows that about 50 minutes ago, BlackRock, via its Ethereum exchange-traded fund ETHA, transferred a total of 19,935 ETH worth $43.65 million to a CEX Prime address.

GateNews1h ago

SUI Will Overtake Ethereum: Mysten Labs Co-Founder Makes Bold Call

A bold statement from Mysten Labs has pushed Sui back into the spotlight, especially as the conversation around scalability and real-world crypto payments continues to evolve. The claim centers on one idea. Future financial systems will demand fast and near-free transactions, and that

CaptainAltcoin4h ago
Comment
0/400
ABigHeartvip
· 03-02 00:13
Ethereum co-founder Vitalik Buterin discussed the Ethereum execution layer roadmap on social media, including changes to the state tree and virtual machine. He supports upgrading the Merkle Patricia tree to a binary tree to improve efficiency and reduce verification costs. At the same time, he recommends replacing the EVM with RISC-V architecture to enhance execution and proof efficiency, as well as simplify code implementation. The overall deployment will be carried out in three steps to ensure backward compatibility.
View OriginalReply0