The main task of the virtual machine is to run smart contracts, which is essentially a code operating environment.
A brief history of the evolution of blockchain virtual machines:
Blockchain 1.0 era:
Provide simple technical support for different currency transactions in the Bitcoin pioneering period.
Blockchain 2.0 era:
The development of smart contracts on Ethereum and Turing’s complete EVM marks that the virtual machine at this time has been gradually improved.
Blockchain 3.0 era:
Characterized by large-scale DApp landing applications, large-scale tests require virtual machines to complete.
The importance of blockchain virtual machines:
In order to ensure that there are no problems with their DApp, developers need to test on a virtual machine before running on the public chain.
After testing that the DApp is indeed a stable and safe product, users can directly use the developer’s DApp on the mainnet of the public chain.
In the era of blockchain 3.0, the competition of virtual machines has become another track for public chain projects. This is almost the only way for blockchain to move towards large-scale commercial use.
The BSC, HECO, Polygon, HSC, OKExChain and other public chains we often use are all developed based on the Ethereum EVM (virtual machine), so there is a certain degree of compatibility. For example, security tools such as the private key, mnemonic address, etc. can all be used in common. (You can import or use these security tools from each other, but do not directly transfer tokens!)