Virtualization in blockchain systems represents a critical phase – the development and migration of services from public chains to business logic. During this critical phase, most of the blockchain projects that are developing and running are using existing public ledgers. However, many projects require customized solutions to ensure flexibility and security of business products and services.
Current industry shortcomings
The verification mechanism of blockchain technology requires miners to verify the data in individual blocks. In the Bitcoin network, all miners must validate the transaction details in the “ledger” and the results presented at each address in the decentralized database commonly referred to as the “ledger. In the ethereum network, due to the existence of smart contracts, in addition to verifying the ethereum ledger, miners also need to verify the results of smart contract calculations against the smart contract code. These smart contract codes need a system to run it, and this system is the “virtual machine”. The ethereum smart contract calculator is the ethereum virtual machine (EVM). As the use of virtual machines becomes more common, the blockchain space has begun to transition from Bitcoin account consensus to the era of smart contract process consensus.
However, the Ether Virtual Machine (EVM) is only one method of implementing smart contracts, and while it is now generally accepted by the industry, other methods of running smart contracts objectively exist and may be better options. Therefore, the Ethernet network is not based on a VM-centric blockchain technology. Because of this, the architecture of virtual machines is relatively simple and inefficient. Let’s explain why in detail.
Because blockchain VM technology is inherently difficult to implement, current EVMs are less efficient than traditional VMs. eVMs leave many features and key components of their operational model unimplemented, forcing language designers to implement them manually. EVM abandons the defining features of standard VMs, such as scheduling, code introspection, and the provision of standard libraries, which results in an expensive, slow, and insecure execution environment.
Obviously, this is just one of the problems faced by Ethernet VMs. In addition to this, EVMs lack standard library support and lack a proper toolset. However, this paper focuses on the EVM design framework and how Rocket Protocol can provide a solution to this problem.
Problems with the EVM design framework
The flaws in the EVM design framework lead to inefficiencies in running smart contracts. When hardware runs the code, it needs to gradually convert the code in text format to binary code that the hardware can understand.
The machine code used by EVM is 32 bytes in length. Compared to a 4-8 byte Java VM, the machine code of a 32-byte EVM will run relatively slowly; the EVM itself does not support decimal point computation, making it less accurate and unable to implement more functions that require higher accuracy; the EVM uses the Harvard computer architecture, which means that: whenever the VM needs to verify the smart contract results, it must temporarily retrieve and fetch the smart contract code in the block and the data used for the computation before starting the computation. If memory-like space were available to hold the smart contract code, the VM would not need to repeatedly request and read data before each computation, in which case it would run much more efficiently.
Rocket Protocol Solution
Rocket Protocol will be compatible with and optimize the performance of existing Ethernet virtual machines to optimize the difficulty of writing smart contracts as well as their computing power.
Rocket Protocol is already fully compatible with EVM’s Solidity language, which is now the de facto standard for Ethernet programming languages. Many of the best FT (Fungible Tokens), NFT (Non-Fungible Tokens), DeFi (Decentralized Finance) and other related contracts are based on EVM smart contracts, and it is only right that Rocket Protocol should carry on the quality genes of these blockchain technologies. It is only logical that Rocket Protocol should carry on the quality genes of these blockchain technologies.
In Rocket Protocol, we believe that application-level compatibility includes two aspects.
Code compatibility means that current developers don’t need to learn more about new code. Instead, they can use the existing code base already deployed to Rocket Protocol, including existing smart contracts and front-end application code. Data compatibility means that data from contracts already running on Ether (ERC20 and ERC-721 standards) can be migrated to Rocket Protocol.
The technical deployment of EVM compatibility is nearing completion and will be implemented through Rocket Protocol’s cross-chain solution as soon as the third quarter of this year.
Rocket Protocol’s other solution, Rocket Ethereum VM (REVM), takes Rocket Protocol and its EVM-compatible technical feature to a new level: REVM allows original ethereum contracts to be migrated directly to Rocket Protocol without recompiling. Like the Ethernet development toolchain, Rocket Protocol offers toolchains such as Remix (an in-browser editor for developing, debugging, and deploying Solidity contracts) and MetaMask (a cryptocurrency wallet for interacting with the Ethernet blockchain) to support developing, writing, and deploying smart contracts.
REVM, while compatible with EVM, also abstracts operations like cross-chain and NFT protocols and writes them into smart contracts as new smart contract keywords. It introduces Rocket Protocol custom keywords to perform Rocket Protocol functions, such as cross-chain and NFT protocols in a single line of code. Developers who use these keywords in smart contracts can enjoy the unique composability and operability that Rocket Protocol brings.
REVM is used to compile Rocket Protocol smart contracts that use these keywords to generate usable bytecode. The migration of smart contracts is based on transactions and the ABI (Application Binary Interface) system, which defines how to access asset protocols or computational programs in machine code. In addition, in Rocket Protocol, the GAS fees required to execute a smart contract can be paid by multiple parties: the contract invoker or the contract issuer.
Currently, EVM design framework flaws lead to many issues that arise, resulting in poor user experience and inefficiencies that cannot be resolved quickly. Building on the lessons learned from Ether, Rocket Protocol places more emphasis on providing a faster and more secure experience for developers.Rocket Protocol is a blockchain infrastructure that is not only fully compatible with EVM’s Solidity language, but also abstracts cross-chain and NFT protocols into new smart contract keywords for better composability combinability and operability. However, since it inherits the Solidity language, it is difficult to avoid the shortcomings that come with the Solidity language inside Rocket Protocol as well, such as the lack of standard library support. In the following article, we will describe how REVM solves the problems caused by Solidity.
About Rocket Protocol
Rocket Protocol is a blockchain infrastructure for the future of virtual worlds, incubated by MixMarvel. Currently, Rocket Protocol has been upgraded to version 2.0. As a high-performance chain cluster that enables contract-level interoperability across multiple chains in the EVM system, Rocket Protocol 2.0 incorporates and extends the cross-chain protocol, NFT protocol, and EVM protocol, enabling developers to freely create complex decentralized applications adapted to various scenarios while giving users a near Internet-like application experience.
Posted by:CoinYuppie，Reprinted with attribution to:https://coinyuppie.com/rocket-protocol-virtual-machine-technology-i-optimized-and-compatible-with-evm/
Coinyuppie is an open information publishing platform, all information provided is not related to the views and positions of coinyuppie, and does not constitute any investment and financial advice. Users are expected to carefully screen and prevent risks.