Vitalik Buterin has stepped back from managing the day-to-day operations of the Ethereum Foundation and returned to what he does best, research. His latest ideas focus on improving Ethereum’s execution speed and protecting user privacy.
One proposal suggests replacing Ethereum’s current virtual machine with RISC-V, a simpler and more efficient system.
Another offers a clear path for better privacy without needing to change Ethereum’s core structure. In this article, we break both of these down so they are easy to understand, even without a technical background.
What is RISC-V and Why Might Ethereum Use It?
To understand RISC-V, it helps to begin with how Ethereum currently works. Every time someone uses Ethereum, whether they are sending funds, interacting with a decentralised application, or running a smart contract, the network relies on something called the Ethereum Virtual Machine, or EVM.
The EVM is Ethereum’s execution engine. It is what processes instructions, carries out contract logic, and ensures the results are recorded on the blockchain. You can think of it as Ethereum’s built-in computer.
However, after nearly a decade of updates and new features, the EVM has grown complicated. This makes it harder to maintain, slower to upgrade, and inefficient when paired with newer technologies like zero-knowledge proofs.
These proofs allow for more private and secure transactions, but they demand a lot of computational effort, an effort that the EVM struggles to handle efficiently.
RISC-V, by contrast, is an open instruction set architecture used in hardware and software worldwide.
It is clean, modern, and much easier to optimise. Think of it as a more streamlined language that computers find easier to understand.
Vitalik proposes that Ethereum switch to RISC-V for executing contracts, either alongside or instead of the EVM, to simplify the system and dramatically improve performance.
However, replacing Ethereum’s core execution engine is not something to do lightly. Thousands of applications and millions of users depend on it.
So, how can Ethereum make the change without causing disruption? Vitalik suggests three different implementation paths, each using real-world comparisons to explain what they would feel like in practice.
First Option: Running EVM and RISC-V Together
This option is the most conservative. Ethereum would keep its current EVM running as usual, but also introduce RISC-V as a second option. Developers could choose whether to write contracts using the old system or the new one.
This is like owning a computer that lets you switch between two operating systems. Imagine having both Windows and Linux installed, you can use either one depending on what you are trying to do.
Ethereum would work the same way. Contracts built in RISC-V could still talk to contracts built in EVM, and vice versa. No applications would break, and developers could adopt RISC-V at their own pace.
Second Option: Running EVM Inside RISC-V
The second approach is a little more technical, but still clear with the right analogy. In this setup, Ethereum would stop using the EVM directly.
Instead, the EVM would be run through a program written in RISC-V. All existing contracts would still work, but they would now be interpreted inside a RISC-V environment.
This is like using a PlayStation emulator on a modern laptop. You are still playing the same game, but it is being processed by a layer that translates old commands into something the new system understands. The game works, but behind the scenes, it is being powered by a completely different engine.
Third Option: Making Ethereum a Multi-Format Console
The third path is the most ambitious. Instead of just running EVM or translating EVM into RISC-V, Ethereum would become a universal platform that supports many different execution formats.
The EVM would be just one of many options, and others, like the Move language used by newer blockchains, could also be supported in the future.
To explain this, think of Ethereum as a modern console that plays games from multiple systems. Not just PlayStation or Xbox, but also Nintendo and old arcade systems, too.
This would make Ethereum highly flexible, as developers would not be limited to a single format. However, building such a system would be more complex and take longer to implement.
Whichever option is chosen, the goals are the same which is to simplify Ethereum’s execution layer, improve performance, and prepare for the future.
But RISC-V is not the only idea Vitalik has shared recently. His other focus is something many Ethereum users care about, which is privacy.
Vitalik’s Roadmap for a More Private Ethereum
Alongside the RISC-V discussion, Vitalik published a privacy roadmap that outlines nine steps Ethereum can take to protect its users’ data. His goal is to give people better privacy without needing to make drastic changes to Ethereum’s base layer.
This roadmap focuses on four areas, which are making payments private, separating activities across applications, protecting data requests, and preventing network-level tracking. Let us go through the nine ideas using everyday analogies to make them clear.
1. Add a Private Option to Wallets
Today, sending ETH privately often requires using a separate application or advanced tool. Vitalik wants standard wallets, like MetaMask, to include a private balance option.
This is like having two accounts in your mobile banking app, one regular, one private. When you send funds, you can choose to use the private one, and it should feel just as easy as sending a normal transaction.
2. Use a Unique Address for Each Application
Most people use the same Ethereum address across all their apps. This makes it easy for others to link your activities together. Vitalik recommends that wallets automatically create a new address for each application.
It is like using a different username or email for each website to keep your online identities separate.
3. Keep Transfers Between Your Wallets Private
Sometimes, you move ETH from one of your addresses to another. These transfers might seem harmless, but they can still leak data. To fully support unique addresses per application, Vitalik says that sending funds to yourself should be private by default.
4. Prevent Censorship of Private Transactions
Some network operators refuse to handle transactions that involve privacy tools. To fix this, Vitalik suggests using Ethereum standards that guarantee private transactions can be broadcast without interference. Think of it as a secure postal service that delivers every letter, even if it is sealed.
5. Use Secure Hardware for Wallet Communications
When your wallet checks your balance or fetches data, it talks to servers known as RPC nodes. These servers can see what your wallet is doing. Vitalik wants wallets to use secure hardware to protect these interactions, like placing a privacy screen over your messages.
6. Switch to Cryptographic Tools in the Future
Hardware solutions are useful, but not perfect. A tool called private information retrieval, or PIR, allows wallets to fetch data without revealing what they are looking for.
Although not yet ready for large-scale use, PIR offers stronger protection and should replace hardware solutions over time.
7. Connect to Multiple Servers at Once
Using the same server for all your apps creates a clear profile of your activity. Vitalik suggests that wallets should use different servers for each application, and route these through networks that scramble traffic. It is like taking different paths to the same destination, so no one knows your full route.
8. Bundle Private Transactions Together
Sending private transactions usually costs more. To lower these costs, users should be able to combine their actions with others in one transaction. This is like carpooling for blockchain, which is that everyone goes to the same place, and the fuel cost is shared.
9. Allow Wallet Upgrades Without Revealing Links
Upgrading your wallet’s security usually reveals a connection to your old address. Vitalik proposes a system where these upgrades can happen quietly, without anyone knowing the old and new addresses belong to the same person. It is like changing your phone number without telling anyone except your contacts.
Conclusion
Vitalik Buterin’s proposals show a clear desire to simplify Ethereum’s technology while improving the user experience. Replacing the EVM with RISC-V would modernise Ethereum’s execution layer, making it more efficient and easier to develop for.
At the same time, his privacy roadmap addresses real concerns from users about how visible their data is when using Ethereum applications.
For now, these ideas remain in the research stage. They have not yet been implemented and have not impacted the price of ETH, which continues to face low transaction volumes and cautious sentiment.
Still, the direction of these proposals is important. They are not about chasing trends, but about addressing Ethereum’s long-term challenges. As Ethereum evolves, ideas like RISC-V and built-in privacy could help it remain relevant and resilient for years to come.