The future of Ethereum may be undergoing one of its most foundational shifts yet — not in consensus or scalability alone, but at the very heart of how smart contracts are executed. A recent proposal by Ethereum co-founder Vitalik Buterin has ignited widespread discussion across the developer community: replacing the Ethereum Virtual Machine (EVM) with RISC-V as the core execution environment for smart contracts.
Dubbed a potential “beam chain-level upgrade,” this transformation isn’t just about boosting performance — it aims to resolve long-standing inefficiencies in Ethereum’s execution layer by embracing a simpler, more modular, and hardware-friendly architecture.
👉 Discover how next-gen blockchain execution could redefine speed and security.
What Is RISC-V — And Why Replace the EVM?
At the center of this vision is RISC-V, an open-source, modular instruction set architecture (ISA) originally designed for hardware processors. Unlike proprietary ISAs, RISC-V is royalty-free, extensible, and increasingly adopted in both academic and industrial computing.
But why apply it to Ethereum?
The idea isn’t to dismantle what works — far from it. Instead, the shift would preserve Ethereum’s high-level abstractions:
- Account model and contract interoperability remain unchanged
- Existing languages like Solidity and Vyper can be recompiled to target RISC-V backends
- Legacy EVM bytecode remains compatible through cross-VM communication
This means developers won’t need to relearn everything from scratch. Yet beneath the surface, the entire execution engine could become significantly leaner, faster, and easier to verify — especially in zero-knowledge (ZK) proof systems.
ZK-EVM: The Hidden Bottleneck in Ethereum Scaling
As Ethereum advances toward full scalability via upgrades like EIP-4444, statelessness, and data availability sampling, the real bottleneck is shifting from data throughput to computational efficiency in ZK proofs.
Today, generating a ZK proof for a single Ethereum block involves simulating every step of the EVM. Shockingly, nearly 50% of the total proving time is spent emulating EVM logic itself — a complex, stack-based virtual machine never optimized for cryptographic verification.
Here's the irony: many ZK-EVM implementations already compile EVM operations into RISC-V-like intermediate representations before generating proofs. So why not skip the middleman?
👉 See how cutting-edge architectures are accelerating blockchain verification.
By making RISC-V the native execution environment, Ethereum could eliminate redundant translation layers. The result? Potential 50x to 100x improvements in ZK proof generation speed, drastically lowering costs and enabling faster finality across rollups and Layer 1.
Why RISC-V Is Faster: Optimizing From Hash Functions to Architecture
To understand RISC-V’s advantage, we must examine where ZK systems spend their resources. Four primary operations dominate current proving workloads:
deserialize_inputsinitialize_witness_dbstate_root_computationblock_execution
The first three can be optimized independently using better cryptographic primitives. For instance:
- Replacing Keccak with Poseidon hash function accelerates hashing by over 100x — up to 2 million hashes per second on a laptop versus Keccak’s 15,000.
- Adopting binary Merkle trees instead of Patricia tries simplifies state proofs.
These changes could reduce non-execution overhead by half. But that still leaves block_execution as the dominant cost, and only a more efficient virtual machine can solve this.
RISC-V excels here because:
- It uses a register-based architecture, which maps naturally to modern CPUs and ZK circuits.
- Its simple, extensible ISA allows specialized opcodes for common blockchain operations.
- It supports strong typing and memory safety, reducing edge cases during verification.
In short, RISC-V isn’t just faster — it’s provable faster, which matters most in trustless systems.
Three Implementation Paths: Balancing Innovation and Compatibility
Vitalik outlined three realistic pathways forward — each balancing backward compatibility with long-term evolution:
Option 1: Dual VM Coexistence (Low Risk)
Allow contracts to choose between EVM and RISC-V. Both runtimes interoperate seamlessly, sharing state and gas mechanics. This path maximizes developer flexibility while enabling gradual migration.
Option 2: RISC-V-Native EVM Interpreter (Radical Upgrade)
All EVM contracts are executed inside a RISC-V-based interpreter. This unifies the底层 execution stack under one architecture, improving optimization opportunities and circuit design consistency.
Option 3: Protocol-Level VM Module (Middle Ground)
Introduce a pluggable “virtual machine module” at the protocol level. Initially implemented with RISC-V running an EVM interpreter, it opens the door for future VMs — such as those supporting Move or other languages — without hard forks.
All three paths share a key benefit: simpler specification, easier auditing, and enhanced transparency for verifiers, especially in ZK contexts.
Developer Perspectives: Move vs. Multi-Language Philosophy
Not everyone agrees on the ideal path forward. Sam Blackshear, co-founder of Mysten Labs (creators of Sui), commented that while RISC-V makes sense for Ethereum due to legacy constraints, he’d choose Move language for any new blockchain.
“If I were building a new chain from scratch, I’d go with Move — not multi-language support. Sui’s advantages come from using strongly typed objects as a unified abstraction across the entire stack.”
This highlights a philosophical divide:
- New chains like Sui prioritize full-stack integration, leveraging Move’s ownership model and compile-time safety to prevent common bugs.
- Ethereum, constrained by history and ecosystem size, values backward compatibility and evolutionary upgrades.
Still, Kyrie, Growth Lead at Typus Finance, recalls a telling conversation with Vitalik at EthTaipei:
“I asked him if Move’s object-oriented model improves blockchain security. He said, ‘I don’t think it changes anything — projects get hacked regardless of language.’”
But Kyrie pushed back: “Move reduces coding errors, is easier than Rust for beginners, and limits blast radius. When a contract is compromised, losses can be contained — not infinite.”
While Vitalik didn’t concede then, his openness to RISC-V suggests a subtle shift — recognizing that language and execution design do influence security and efficiency, even in mature ecosystems.
👉 Explore how future-proof architectures are shaping secure blockchain development.
Frequently Asked Questions (FAQ)
Q: Will existing smart contracts stop working if EVM is replaced?
A: No. Under all proposed paths, legacy EVM contracts remain functional through compatibility layers or dual VM support.
Q: Is RISC-V used in real-world blockchains today?
A: Yes. Several projects, including FOAM and certain ZK-focused chains, already experiment with RISC-V for provable computation.
Q: Does this mean Solidity will become obsolete?
A: Not at all. Solidity can be recompiled to target RISC-V bytecode, preserving developer workflows.
Q: How soon could this change happen?
A: It’s still early stage. Research and prototyping are ongoing; deployment would likely take years and require broad community consensus.
Q: Could other VMs like WASM or Move replace EVM instead?
A: WASM has been considered but faces challenges in determinism and circuit efficiency. Move offers safety benefits but lacks EVM’s ecosystem depth.
Q: What are the risks of switching to RISC-V?
A: Main risks include implementation complexity, testing gaps, and potential fragmentation during transition — mitigated by phased rollout strategies.
Ethereum’s potential shift from EVM to RISC-V marks more than a technical upgrade — it reflects a maturing vision of what a scalable, secure, and future-ready blockchain should be. By embracing open standards and hardware-aligned design, Ethereum may finally achieve the clean-slate efficiency it needs — without abandoning its past.