Partnered With:

EOS established EVM+ Working Group to achieve EVM compatibility

Read this article in 62 Minutes

The EVM+ working group will work directly on development and product delivery to achieve EVM compatibility at the EOS smart contract level more quickly.

Original source: EOS Network Foundation

An overview of the

EOS is bringing the community together to develop key projects that are needed to further the recovery of EOS ecology. We have talented developers, community leaders who can make a significant contribution, and the EOS Network Foundation, which is very responsible and driven.

EOS is blazing its own path forward and ushering in a new era of collaboration.

At present, six Core working groups funded by the EOS Network Foundation are running at a high speed, each playing an important role in its field. Among them, API+, Core+, Wallet+ and Audit+ blue papers are nearing completion. Each blue paper is an important research result that will detail development goals. Feasible strategies for success in their respective fields.

Today, we will introduce you to the EVM+ Core Working Group. Before the formal introduction, we will have an overview of the six core working groups.

Six core working groups are introduced

Currently, there are six core working groups sponsored by the EOS Network Foundation:

, & have spentAPI+: Mainly responsible for providing data interfaces to help applications outside the EOS ecosystem better integrate the EOS network.

, & have spentCore+: Mainly responsible for maintaining the EOS system to make IT more suitable for running various types of applications.

, & have spentWallet+: Mainly responsible for integrating EOS into external applications with software.

· Audit+ : Mainly responsible for providing security analysis tools and overall framework for contract Audit for EOS applications.

· EVM+ : mainly responsible for achieving compatibility with EVM and exploring economic incentives for EOS feasibility.

· Recovery+ : Mainly responsible for establishing the crisis management framework and helping EOS projects deal with the crisis and recover lost assets in a more reasonable and effective way after being attacked by hackers by developing emergency contact, response mechanism, DAO insurance and white hat incentive.

The Core Working Group will work with the most experienced individuals and organizations in the EOS ecosystem to play an important role in implementing the EOS Roadmap. This will be a great opportunity to assess the current state of the EOS ecosystem, identify potential issues and develop a roadmap for future development.

Each working group received $200,000 to $250,000 in grants from the EOS Network Foundation, and an additional $100,000 was spent by the EOS Network Foundation to establish a monitoring group to monitor the overall progress of the working group.

But because of community voices and ecological needs, the EVM+ working group has a slightly different workflow than other working groups. inEOS ArgentinaThe EVM+ working group will take a more agile approach to development under the leadership of

Instead of writing a blue book, the EVM+ working group went straight to development and product delivery to achieve EVM compatibility at the EOS smart contract level more quickly. In addition, the EVM+ Working Group has an initial budget of $200,000.

EVM+ Working Group introduction

One of the most important issues EOS is currently facing is blockchain interoperability.

The most common problem in the blockchain field is to focus on inward development while neglecting to learn from each other's strengths and weaknesses through outward compatibility, which is evident in EOS. Developers often fall into the logic that EOS has the best technology, so EOS is the best place to be, even if the rest of the public chain ecosystem doesn't realize the potential of EOS yet.

Such thinking would isolate EOS from the wider blockchain world, making it easy to sit back and miss many opportunities. Many developers are leaving EOS for Ethereum because ethereum, while flawed, has better compatibility.

This is why we established the EVM+ Working Group and accelerated the work in this area. The deployment of Ethereum virtual machine on EOS is a very important work. We need to promote THE integration of EOS into the broader blockchain ecosystem, and continue to bring in, go out, inclusive and rapid development.

From a technical and business perspective, achieving EVM compatibility could play a vital role in unlocking the potential of EOS. We need more Ethereum developers and users to join the EOS ecosystem, and helping EOS achieve EVM compatibility is the best way to attract them.

Stand on the shoulders of success and attract development talent

The EVM+ working group is led by EOS Creation Block producersEOS ArgentinaAnd so does the teamEvodexandEOS MetamaskThe developer behind the wallet.

The EVM+ working group was also assisted by Syed Jafri, a renowned developer of EOS Ecology, who won block. one's EVM Challenge in 2020 with EOSIo. EVM, Eosio. EVM enables Solidity developers to quickly start and run applications up to 100 times faster and for less than 1000 times the cost on EOSIO. It can be said that Syed Jafri is very experienced in helping EOS achieve EVM compatibility.

EVM is a much-needed innovation for EOS. One of the major problems the EOS Common chain has faced in the past few years is lack of funding. Let's make a comparison with Taifang Ecology:

· Ethereum is slower, less efficient and Gas costs are very high, but there are higher network effects and token liquidity between Ethereum and other EVM-based public chains. On the other hand, some developers on Ethereum can make big money by creating modular, reusable, secure and open source smart contracts based on Solidity, while others canOpenZeppelinAccess to a wealth of development tools and tutorials. There is no denying the fact that developer tools, code bases, and open source code available to dApp developers in the EVM ecosystem are growing rapidly.

· In contrast to the EOS ecosystem, developers have to build many code bases from scratch using less mature tools. An inappropriate analogy is: Whereas the developers of the Ethereum ecosystem built cars like building blocks, splicing together off-the-shelf wheels, steering wheels, engines, etc., the developers of EOS Ecosystem wanted to build cars by building wheels.

Other working groups sponsored by the EOS Network Foundation are focusing on improving the EXPERIENCE for EOS developers and providing more locally available tools, but all will take some time to fully implement.

Therefore, we and the community believe that we can tap into the potential of the EOS ecosystem by leveraging the talent and resources that already exist in EVM and bringing them to EOS through EVM compatibility.

As EOS enters an extremely important year, two major challenges remain:

· On the one hand, EOS must demonstrate its great potential and value to potential developers;

· On the other hand, EOS must remove barriers to developers' entry into the ecosystem, lowering the barriers as much as possible to attract more developers to join.

Even if the project or developer believes THAT EOS is better, the project or developer will not join if the process of entering the EOS ecosystem is long and cumbersome. Therefore, it is more effective to help other public chain developers to deploy, migrate, or clone projects into the EOS ecosystem in a barrier-free, low-barrier manner.

EVM+ Working Group: Bridge EVM and EOSIO

The overall goal of EVM+ is to make EOS a compatible EVM platform from a developer and user perspective. To that end, the following are the key issues being addressed by the Working Group:

· Smart contract-level compatibility and local node implementation: EOS Argentina is working to develop a smart contract-based solution that will enable EVM to run properly when EOS VM WASM is running. This will allow the EOS network to upgrade EVM operations without a protocol upgrade (no fork required).

· ETH precompiled contract: this not only benefits EVM on EOS, but also smart contract developers. Like other chains, EOS has a limited transaction execution time (150 ms for protocol and 30 ms for BP). Despite the EOS VM's power and speed, there are still some types of operations performed in Web assembly that lack the optimization they can do in native code. To speed things up, the EVM+ working group is looking to implement ETH precompiled as EOS intrinsic functions (native code).

· Full RPC compatibility: Plans for this area are still under development, but the EVM+ team aims to support at least most RPCS to allow the use of a common tool/development environment on ETH. This will be one of the programme's most important jobs.

· Deterministic Gas consumption/billing: THE EOS chain uses three resources: CPU (subjective measure/variable price), NET (objective measure/variable price), and RAM (objective measure/variable price) billing. The challenge in this area is to provide users with deterministic Gas consumption and competitive Gas prices, while preventing misuse of the Web3 API.

· Metamask support: This means that the EOS Ecosystem will support the Metamask Wallet for interaction between EOS local contracts and EVM contracts written using Solidity.

The EVM+ Working Group will move forward rapidly along these lines to create the best solution for EVM compatibility for EOS and aim to have a workable solution by summer 2022.

The current six working groups are building a framework that will make it easier for developers and users to participate in EOS, facilitate the growth of the EOS network and make the EOS ecosystem more attractive. The future of EOS has never been brighter. We invite you to join us to create the return story of the blockchain world's greatest public chain.