Vitalik just shared a bold idea to transition from EVM to RISC-V to meet the demand for enhanced performance of the Ethereum network $ETH
1️⃣ Problems that Ethereum is facing:
EVM - the 'engine' running Ethereum smart contracts consumes a lot of resources, especially at the block execution step. Since it was not designed to optimize for ZK technology, EVM is making it difficult for Ethereum to scale Layer 1 to handle more transactions effectively.
2️⃣ RISC-V Solutions
- In theory, the transition to RISC-V requires developers on Ethereum to readapt to fully leverage RISC-V, such as: using the new programming language Rust (instead of the current Solidity/Vyper), rewriting old smart contracts, updating the entire accompanying tool ecosystem,....
- RISC-V can be simply understood as the 'new engine' replacing EVM. RISC-V has an open-source architecture, is ZK-friendly, and has been adopted by Nervos & Polkadot.
- RISC-V is estimated to potentially reduce the processing cost of smart contracts by over 100 times in some cases for Ethereum.
3️⃣ RISC-V Deployment Plan
According to Vitalik's proposal, Ethereum does not discard everything that has been built but only changes to better adapt to ZK technology:
- Old-style EVM smart contracts can still operate and are fully compatible two-way with the new RISC-V.
- Developers can still write code in Solidity/Vyper, the only difference is that the backend will compile to RISC-V instead of EVM bytecode.
- Core concepts of Ethereum such as accounts, storage, ETH balance… remain unchanged.
👉 If properly implemented, users and developers will hardly notice any change in the experience.
4️⃣ Roadmap
Ethereum is still focusing on the Pectra upgrade (7/5/2025) while RISC-V is a long-term plan and this is only a proposal.
=> Vitalik affirms that if Ethereum wants to become the global financial infrastructure, restructuring this execution layer is inevitable.
