On April 20th, co-founder of Ethereum (ETH) Vitalik Butein presented a proposal that could translate the technical core of a network. Replace Ethereum Virtual Machines (EVMs) with RISC-V, a virtual machine architecture designed to be used in a more general context.
The change, described by Bugelin itself as a long-term solution to the challenges of Ethereum’s scalability and simplicity, is seeking to optimize the execution of intelligent contracts and improve network efficiency.
The precedent for the proposal made by Buterin is at Polkadot Red (DOT). According to users who call themselves “Drago Mist” and X’s polka dot developer “Fabsverse”, RISC-V on that network allowed for a 100x improvement in “transactional speed (transactional)) and performance of zero knowledge test (ZK proof), privacy and scale criticism.”
What is EVM? Why is it so important to Ethereum?
Ethereum Virtual Machine is a computer program that automates contracts or transactions when certain conditions are met, and certain conditions are met for intelligent network contracts. EVM acts as a “virtual computer” that processes the code for these contracts, ensuring that all operations are performed Uniform method across all nodes in the Ethereum networkproviding confidence and security to users.
EVM uses a language called “OpCodes” (basic instructions such as adding data, storing it, or calling another contract). Process transactions and intelligent contracts in this environment require a lot of computational resources; Generate bottlenecks with scalabilitythat is, the network’s ability to handle increased manipulation without being triggered.
Additionally, EVM is both the execution environment for intelligent contracts in its ecosystem and the component that defines its low-level language, bytecode, which compiles high-level languages such as Soliviti and Vyper. Not only does EVM perform its bytecode (not only human-readable, but more efficient for execution by EVM) on every node in a deterministic way, but it also establishes rules and options that interact with the state of the network to determine contract structure and programme. Therefore, your role will be covered Both execution and definition of contract programmatic form.
What is RISC-V? How does it differ from EVM?
RISC-V, on the other hand, is an open source source instruction set (and EVM). This means that anyone can use it and change it without any restrictions. Unlike EVMs designed specifically for Ethereum, the RISC-V is More general standards It is used in a variety of applications, from microprocessors of electronic devices to embedded systems (integrated computing devices or systems designed to perform specific functions within a network).
The acronym RISC-V comes from “Reduce instruction set computers” (The computer with instructions reduced is set up), which indicates that the working approach under simple instructions allows Faster processing and reduce resource consumption.
In the context of Ethereum, RISC-V is used as an alternative virtual machine for performing intelligent contracts. Buterin’s proposal suggests that developers can continue writing contracts in popular languages such as Solidity, but these are edited directly into RISC-V instructions rather than EVM opcodes. This reduces the intermediate complexity that EVMs expect, and according to Butterin, it significantly improves processing efficiency.
Purpose of replacing EVM with RISC-V
Buterin identifies that in the long run, bottlenecks are related to their ability to efficiently certify and execute contracts.
An important aspect of the proposal is the optimization of zero knowledge tests (ZK Proof), types of technologies that can verify transactions Without revealing all the underlying datawhich is essential to maintain privacy and reduce the size of data a node needs to process.
The following table, presented by Buterin, details the cycles required to test different parts of the EVM execution. Four situations consume most of the processing time:
- Input data deerialization (“Deserialize_inputs”).
- Initializing the witness database (‘initialize_witness_db’).
- Calculating the state route (‘state_root_computation’).
- Block execution (“block_execution”).
These data show that Approximately 50% of processing time is dedicated to blocking executionsincludes interpretation and processing of intelligent contract instructions. By replacing EVM with RISC-V, contracts can be significantly reduced this time, as they run directly in a more efficient environment and eliminate the middle tier representing EVM.
Furthermore, the proposal seeks to simplify the Ethereum protocol. With certain options and rules, EVMs accumulate complexity over time, making it difficult to make changes and improvements without breaking compatibility with existing contracts.
When adopting RISC-V, Bugerin suggests that the protocol can be reduced to Much simpler specificationsfacilitating network maintenance and implementing new features more easily in the future.
The advantage of efficiency? Butarine’s goal
One of the most powerful arguments in the proposal is the possibility of improving the efficiency of zero-knowledge tests. Currently, ZK-EVM works by compiling EVM code into RISC-V and verifying the process of adding layers of complexity. By allowing contracts to be written and executed directly in RISC-V, the intermediate steps are eliminated.
Buterin presents data that compares the performance of different interpreters (software) when performing intensive mathematical operations, such as the calculation of Fibonacci numbers, a common task of measuring computational efficiency.
The results of Ethereum co-founders show what the RISC-V (such as REVM) programs (such as REVM) show. They’re much faster Based on traditional EVM or other technologies such as WebAssembly (WASM).
These data suggest that processing efficiency increases and may be generated The impact on Ethereum’s ability to handle complex transactions.
However, Bugerin makes it clear that actual profits depend on how the gas costs are adjusted (the fees the user performs the operation) to reflect the test times of RISC-V. Can discourage you from using more expensive operationsand many resources consume certain pre-competitive calculations, such as the ones that pre-competitive calculations that are consumed today.
How will this change be implemented?
The transition from EVM to RISC-V is not immediate or simple, but Bugelin has proposed several strategies to make it viable. The most destructive option is to allow Both coexistence environments: Contracts can be written in EVM or RISC-V, and both types are interoperable.
A more fundamental alternative is to convert all existing EVM contracts into contracts that use the EVM interpreter written in RISC-V. In this scenario, when the EVM contract receives a call, the RISC-V program executes the original code and returns the result.
The third intermediate option is to establish a formal mechanism in the protocol Supports multiple virtual machinesstart with EVM and RISC-V, but leave the door open to others, such as those used in other networks.
Current costs of EVM: obstacles to scalability
To understand why this change is necessary, Buterin also provides data on the computational costs of the most common operations in EVMs measured with “gas,” a unit representing Ethereum’s computational efforts.
The following image reflects operations such as copying data (“CallDatacopy”) or call another contract (“Sender”) consumes a considerable amount of cycles (“Average cycle”), what I know It leads to higher costs for users Lower network capacity to process transactions.
These costs reflect limitations inherent to the EVM architecture. Adopting RISC-V, Ethereum was able to optimize these operations, according to Buitterin’s proposal. Reduces both user processing time and cost,This allows the network to process more transactions.
