Ethereum-News: New “Turbo upgrade” could increase the pace of the process by a factor of 100
- According to an upgrade proposal von Vitalik Buterin Could an exchange of the VM of the system The execution layer of Ethereum one accelerate 100 times.
- The replacement of the EVM with a RISC-V system would Operation of smart contracts simplify, without disturbing the workflows of the developers.
Ethereum inventor Vitalik Buterin Has the Proposalto redesign the functionality of Ethereum. He looks like The EVM (Ethereum Virtual Machine), which is currently for the Execution of Smart Contracts is usedby a new system based on RISC-V replace .
The changeover would have a positive effect on the network, since it would not only be light -hearted, but also relatively easy to wait. In the narrower sense Is it a butterin around the Elimination of bottlenecksThe one Slow down the performance of Ethereum.
By taking over RISC-V (Reduced Instructation Set V), a simple, source-open command rate that is usually used in traditional data processingEthereum could reduce the runtime and the CPU load.
The proposal would The structure of smart contracts changewhile the basic organizational system is retained by accounts, contract storage and functional calls. What is changed is that Language of the backend that performs the smart contracts.
Such a change Programmers give the opportunity to stay with the familiar languages that they are used to, for example Solidity or Vyperand even Rust. The users become however Despite the change in the underlying technology no Noticeable change in development.
He also wanted to make it clear that The contracts that In the past with the EVM were writtencontinue to work without any problems and run on the new RISC-V as if nothing had changed.
Execution efficiency can reach new heights
The problem of scalability From Ethereum Is primarily on the way trace , how transactions are processed and verified. Vitalik Buterin mentioned that a significant part of the Computing power from Ethereum forThe operation such as data conversion or data storage must be used.
These tasks are mostly proof cycles, of which tens of thousands are required. As a result, the CPU performance significantly drops.
Buterin’s proposal would cause more than 50% of the existing tasks to include operations that change the condition, such as reading and overwriting the blockchain. One way to achieve better results is to change the architectures in such a way that they are easier and use more modern hash functions.
For example, Poseidon, an advanced hash algorithm, could replace Keccak, which allows over millions of hashes per second, compared to the current 15,000 per second.
The greatest Difference lies however In the change of the EVM itself. ZK-EVMS become already At the time of your verification On Risc-V convertedso that the developers must have direct access to RISC-V.
Buterin says, This method minimizes inefficiencies. Some of the tests have even shownthat die Efficiency in certain parts of the execution by 100 times increased can.
Risk-V would Ethereumkernel-Performance revolutionize
Buterin places some of the possibilities how Ethereum can make this change. The simplest method would be, as well as The current EVM as well as the new RISC-V area Pto run arallel. In such a scenario, the developers are free New contracts contracts in both environments to createand both Contracts continue to exchange data.
One More daring alternative would be to program RISC-V-based interpreter routines that can carry out the existing EVM-Contracts. With this approach becomes The entire Contract logic of the contracts on the new RISC-V System veragedwithout the old contracts having to be rewritten so that the change can take place during operation.
An even more systematic version could be RISC-V-Interpreter officially im Ethereum protocol name and Space For the creation future interpreter in other languages allow .
One of the greatest advantages This change is that you die technical side simplify by Ethereum can. However, the proposal is still in the Phase of the first Discussion and the schedule became not yet confirmed.
No Comments