On March 2nd, PANews reported that Ethereum co-founder Vitalik Buterin outlined the Ethereum execution layer roadmap on social media, focusing on two major changesOn March 2nd, PANews reported that Ethereum co-founder Vitalik Buterin outlined the Ethereum execution layer roadmap on social media, focusing on two major changes

Vitalik outlined the Ethereum execution layer roadmap, focusing on two major changes: the state tree and the virtual machine.

2026/03/02 08:05
2 min read

On March 2nd, PANews reported that Ethereum co-founder Vitalik Buterin outlined the Ethereum execution layer roadmap on social media, 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 via EIP-7864. This change can shorten Merkle branches by four times, reducing bandwidth costs for client-side data verification; simultaneously, the hash function can be changed to Blake3 or Poseidon series, significantly improving proof efficiency. The binary tree design also groups storage slots into "pages," making access costs between adjacent storage locations lower, saving many DeFi applications over 10,000 Gas per transaction. Furthermore, the simpler binary tree structure allows for the reservation of metadata bits for future state expiration functionality.

Regarding virtual machines, Vitalik proposed a long-term direction of replacing the EVM, potentially adopting a RISC-V architecture. The new VM needs to meet four goals: higher raw execution efficiency, making most pre-compiled code unnecessary; superior proof efficiency compared to the EVM; support for client-side ZK proof generation; and maximum code simplification. He pointed out that while Ethereum is "sufficient" at the "EVM+GPU" level, a better VM would make the protocol more robust. The deployment roadmap consists of three steps: the new VM will initially replace pre-compiled code; subsequently, users will be allowed to deploy contracts based on the new VM; and finally, the EVM will be retired, replaced by smart contracts written with the new VM, achieving full backward compatibility.

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact crypto.news@mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.