How RISC-V Could Supercharge Ethereum: Decoding Vitalik's Scalability Strategy

In a move that could redefine Ethereum’s technical foundations, Vitalik Buterin has floated a bold new idea — replacing the Ethereum Virtual Machine (EVM) with RISC-V, an open-source processor architecture. In a recent Ethereum Magicians forum post, Buterin called the proposal “radical” and “ambitious,” suggesting it may be the only viable path to scale Ethereum’s execution layer in the long term. As Ethereum prepares for its next upgrade, this concept signals a deeper shift in how smart contracts might run — and what the future of decentralized computation could look like.

Key Highlights

• Vitalik Buterin proposes a radical long-term idea to replace Ethereum’s EVM with RISC-V architecture.
  

• RISC-V is an open-source, modular processor architecture known for its speed, simplicity, and zk-friendly nature.
  

• The shift could reduce execution costs by up to 100x and significantly improve Ethereum’s scalability.
  

• Ethereum would maintain full backward compatibility with existing EVM contracts.
  

• A two-way interoperability model is proposed to enable smooth transition and developer flexibility.
  

• Ethereum’s immediate roadmap includes the “Pectra” upgrade, set for May 7.

1. Why RISC-V? Understanding the Shift

At the heart of Vitalik’s proposal is RISC-V, an open-standard instruction set architecture (ISA) that’s gaining popularity across hardware and software circles for its simplicity, flexibility, and performance efficiency. Originally developed for hardware processors, RISC-V offers a modular framework that can be adapted for a wide range of computing tasks — including, as Vitalik now suggests, running smart contracts on Ethereum.

So why consider RISC-V for Ethereum?

The answer lies in scalability and performance. The current Ethereum Virtual Machine (EVM) was designed in 2014 with limited foresight into the massive complexity and demand it would eventually face. It's optimized for security and portability, but not necessarily for high-throughput execution or zero-knowledge proof generation, which are becoming essential for scaling.

RISC-V, being a real-world architecture with proven efficiency, is better suited to modern execution environments. Vitalik argues that adopting it could cut on-chain execution costs by as much as 100x, especially as Ethereum moves deeper into zk-based scalability.

Key Reasons for Considering RISC-V:

• Efficiency: Simpler instruction sets make execution faster and more provable.
  

• Flexibility: Modular design allows customization for blockchain-specific needs.
  

• Compatibility: Being open-source, RISC-V is easier to implement and maintain than proprietary alternatives like ARM or x86.
  

• Future-Proofing: Aligns Ethereum’s virtual machine with modern processor design standards.
  

In short, RISC-V isn’t just about speeding things up — it’s about future-proofing Ethereum’s execution layer for the next generation of decentralized applications.

2. EVM vs. RISC-V: What Would Actually Change?

To understand the magnitude of Vitalik’s proposal, we need to unpack how the Ethereum Virtual Machine (EVM) currently works — and how it would differ under a RISC-V-powered execution model.

The EVM is a purpose-built, stack-based virtual machine designed to execute smart contracts. It runs its own custom bytecode and has been the backbone of Ethereum since its inception. However, it was never designed with high scalability, modularity, or provability in mind. As Ethereum evolves — especially with rollups, zk-proofs, and real-world integrations — its limitations are becoming more evident.

By contrast, RISC-V is a general-purpose architecture that can be adapted for smart contract execution with far greater computational efficiency. This switch could enable developers to write smart contracts in existing mainstream languages that compile down to RISC-V, reducing friction in onboarding and expanding Ethereum’s appeal to traditional devs.

EVM and RISC-V Comparison:

This shift wouldn’t just affect developers — it would change how Ethereum’s entire execution layer operates, opening the door to lower gas costs, more efficient ZK-rollups, and more scalable dApp architectures.

Still, Ethereum wouldn’t abandon the EVM entirely. Vitalik envisions dual support — where EVM and RISC-V smart contracts can coexist and interact — ensuring backward compatibility without forcing the ecosystem through a risky hard fork.

3. Keeping Compatibility: What Happens to Current Contracts?

One of the most critical concerns with any major protocol change is backward compatibility — and Vitalik Buterin addresses this head-on. Despite the proposal’s ambitious nature, Ethereum isn’t aiming to abandon the EVM. Instead, the vision is to support both EVM and RISC-V smart contracts side by side, preserving everything that already exists while building a more scalable path forward.

In practical terms, this means:

• Existing EVM contracts will continue to function as they do today — unchanged and uninterrupted.
  

• Ethereum could introduce a parallel RISC-V environment, where new contracts can be deployed using RISC-V architecture without impacting legacy contracts.
  

• A two-way interoperability layer would allow EVM and RISC-V contracts to call each other, creating a hybrid execution model during the transition.
  

• A future interpreter or compiler could convert existing EVM contracts into RISC-V-compatible formats, reducing the burden on developers and preserving historical codebases.
  

This gradual and interoperable rollout would prevent the need for a disruptive hard fork and instead offer developers the choice to migrate or build natively on the new architecture when ready.

The key takeaway? Vitalik’s proposal isn’t about rewriting Ethereum’s past — it’s about future-proofing its future, while maintaining stability, community trust, and developer continuity.

4. What This Means for Ethereum’s Future

Vitalik’s RISC-V proposal isn’t an immediate roadmap item — it’s a long-term vision that could reshape how Ethereum scales, executes, and attracts developers. If implemented, this shift could position Ethereum to better handle the computational demands of the next decade, from high-frequency DeFi protocols to real-world asset tokenization and large-scale zk-rollup ecosystems.

Potential Long-Term Impacts:

• Massively Improved Scalability
  RISC-V could significantly reduce execution costs and improve prover efficiency for zkEVMs, leading to faster, cheaper, and more scalable applications.
  

• Better Developer Experience
  Mainstream programming languages like Rust or C could become more compatible with Ethereum contracts, lowering the barrier to entry for traditional developers.
  

• Institutional-Grade Performance
  A high-efficiency virtual machine could make Ethereum more attractive for enterprise and high-throughput use cases, especially in the context of Real World Assets (RWAs).
  

• Multi-VM Coexistence
  With other chains like Polkadot already exploring multi-VM architectures (e.g., PolkaVM), Ethereum’s move toward supporting both EVM and RISC-V could establish a more modular and extensible execution environment.
  

Meanwhile, in the short term, Ethereum is still focused on nearer milestones — including the Pectra upgrade slated for May 7, which aims to improve user experience, raise validator stake limits, and boost rollup scalability. These updates are part of a broader, layered strategy that balances iterative improvements with bold innovation.

Vitalik’s RISC-V proposal may take years to materialize, but it sends a clear message: Ethereum isn’t afraid to rethink its foundations if it means long-term viability.

5. Final Thoughts

Vitalik Buterin’s proposal to adopt RISC-V as a new virtual machine architecture for Ethereum signals a bold willingness to reimagine the network’s foundations. While still in its early conceptual stages, the shift could unlock significant improvements in execution efficiency, developer accessibility, and long-term scalability.

Ethereum’s evolution has always hinged on balancing innovation with stability — and this proposal is no different. By preserving backward compatibility with EVM contracts while opening the door to a high-performance, zk-friendly alternative, Ethereum continues to lead in shaping what scalable, decentralized computation can look like.

In a time when execution costs, developer flexibility, and institutional adoption are under the spotlight, platforms like Laika AI help users track and understand foundational shifts like this.
Explore Laika AI or install the Laika Chrome Extension to stay informed on the evolving architecture of Web3.

FAQs

1. What is RISC-V and why is it relevant to Ethereum?
RISC-V is an open-source instruction set architecture (ISA) designed for high-performance computing. Vitalik Buterin proposes using it to replace the Ethereum Virtual Machine (EVM) due to its modular design, scalability, and better compatibility with zero-knowledge proving systems — all crucial for Ethereum’s long-term growth.

2. Why does Vitalik want to replace the EVM with RISC-V?
Vitalik argues that the EVM is becoming a bottleneck for scalability and zk-proof efficiency. RISC-V could dramatically reduce execution costs (by up to 100x), improve rollup performance, and offer better tooling for developers.

3. Will Ethereum abandon existing smart contracts if RISC-V is adopted?
No. The proposal includes full backward compatibility with EVM contracts. Old-style contracts would continue working as usual, with optional interoperability layers or interpreters to bridge EVM and RISC-V contracts.

4. How would RISC-V impact Ethereum developers?
If implemented, developers could write contracts in a wider variety of programming languages, enjoy better performance, and access new tooling. However, EVM-based development would still be supported during the transition.

5. What are the risks or trade-offs of switching to RISC-V?
Key concerns include developer migration, ecosystem fragmentation, additional implementation complexity, and the need for long-term community consensus. The shift would also require extensive testing and phased integration.

6. Have other blockchains used RISC-V before?
Yes. Polkadot introduced PolkaVM in 2023, supporting multiple virtual machines including RISC-V. This multi-VM approach serves as a real-world example of how Ethereum could implement a similar hybrid system.