According to the IPFS community news, the IPFS governance layer adopts the EVM mechanism, which will be completed in the near future, when FILW will have a complete smart contract function.
 
According to the developers of the IPFS community:
· The choice of VM is an important issue. I wanted to use EVM at the beginning, but before that, EVM will become the mainstream standard or whether other VMs (such as WASM or JS-based VMs) will replace it, it is still unclear.
· Multi-virtual machine approach. The recommended method in the past few months is to enable support for the most important VMs in FILW (such as hypervisors).
· Start with EVM. EVM has become the ETH virtual machine standard. Although EVM has other very exciting competitors, I think we should start by adding EVM. This will connect well with all Dapps that already use IPFS and FILW, as well as most NFTs and Oracles.
· After JS and WASM. Pay close attention to WASM and JS-based VMs. A system like Agoric is enriching its functions and may become a very compelling smart contract system for FILW.
· Verified virtual machine. Also, pay attention to the formally validated virtual machine. The validated system has many compelling benefits, such as Tezos and Michelson.
 
When EVM or other VMs successfully join the FILW network, FILW will have a complete smart contract function. The full name of VM is Virtual Machine, which translates to virtual machines. The virtual machine is considered to be the infrastructure in the field of blockchain technology, and is the most critical and core technology to realize the smart contract system.
 
What is the relationship between smart contracts and virtual machines?
We can understand the blockchain as a system. The system runs on a computer. This computer is a virtual machine. Smart contracts are codes that run on this computer. The virtual machine provides an operating environment for the operation of smart contracts.
 
Take ETH as an example. Ethereum has its own virtual machine EVM, ETH's smart contract runs on the EVM virtual machine, and the DAPP application on ETH runs on the Ethereum smart contract. The Ethereum ecosystem has achieved breakthrough development many times in just a few years. To a large extent, it is because Ethereum has good enough virtual machines to support sufficiently open and powerful smart contracts. Developers can build their own applications on the Ethereum smart contract and issue their own tokens.
 
Why does FILW use EVM?
According to reports, FILW will first use Ethereum's virtual machine EVM, other VMs such as WASM and JS, or self-developed VMs, and follow up. Although it takes time and effort to develop a virtual machine alone, the strength of the IPFS team is not difficult. So why does FILW still use Ethereum's virtual machine EVM?
 
For FILW, it is an inevitable choice to use a virtual machine first, because when FILW truly has its own smart contract, it can interact with developers at a deeper level, and the FILW network is expected to give birth to a DAPP giant. By then, not only can this DAPP attract a large amount of traffic with its own characteristics, and enhance the visibility of FILW. Moreover, when the application and popularity on the FILW network become higher and higher, the FILW network needs to store more and more data, and the FILW stores more and more data, the value of FILW will become higher and higher, and FILW can truly become a distributed network that stores important information of human society.
 
What's more noteworthy is that the various products in the blockchain world are not closed, but open. FILW and ETH have always been good brothers. FILW uses EVM to help cross-chain communication and exchanges between the two ecosystems. , This will help all Dapps that already use IPFS and ETH and most NFTs to achieve a good connection. This is not only conducive to deepening the cooperation between FILW and ETH, but also conducive to the long-term development of many parties.