Optimism will launch the latest version of OVM2.0 that is fully compatible with EVM in October, and has taken a big step toward the goal of bringing native Ethereum to L2.
Original Title: “Optimistic Ethereum’s Next Major Update”
Written by: Optimism
Translation: ETH Chinese Station
It seems that a century has passed since we released unipig . In this article, we will announce the most important update since the establishment of Optimistic Ethereum.
After the release of this updated version, we have taken another big step towards our goal of bringing native Ethereum to L2. Developers will be able to deploy contracts with one click, and tools that everyone is accustomed to can also run on Layer 2. And all of these are built around Ethereum’s most secure client code base.
Updates will begin rolling out in a few weeks.
More than EVM compatibility
Building the core infrastructure is not easy, and testing of new technologies takes a certain amount of time-just ask any experienced Ethereum developer to know that the current tools have evolved a lot compared to the early days.
The challenge of building an EVM-compatible rollup is even greater: supporting the entire Ethereum stack in the new technology. The cost of re-implementing the secure EVM function is high; every additional line of code brings the risk of vulnerabilities.
This is why we keep asking ourselves: “How can we scale Ethereum with the fewest lines of code?” When a contributor replaced our 5,000-line translator with 300 lines of code, we were obsessed for the first time Delete the code . Now, Feng Shui takes turns until we delete his code.
With years of in-depth knowledge of the Ethereum Virtual Machine (EVM), we spent some time re-evaluating our initial assumptions to see what could be improved. The final result we got is: Our rollup is not only compatible with EVM, but also can be upgraded to the same effect as EVM. By strictly implementing the Ethereum Yellow Paper , any code written based on Geth can now be deployed on rollup without changes – even for advanced features such as tracking and gas. This upgrade removed our custom compiler, and also removed 25,000+ other lines of code in order to simply use the existing code.
Our minimalist philosophy also provides unique scalability on the social layer. By building on top of the existing Ethereum client (Geth), we inherited any improvements made to the Ethereum client code, and vice versa-this is a win-win for the entire Ethereum ecosystem. Our ultimate goal is to make alternative node implementations (such as OpenEthereum or Erigon) possible within 1000 lines of code.
What does this update mean?
This means that we will implement one-click deployment in October, here is the complete change settings. We will announce the final release date on twitter and discord next week, so stay tuned.
Those projects that have always wanted to deploy but cannot be run with a custom compiler will be able to deploy directly without modifying their code. In addition, any tool that can run on Ethereum will be able to run on Optimistic Ethereum. This means that developers can use DappTools, Vyper, Tenderly, Hardhat, etc. on L2.
In this version, there will be no changes to our current security model-OE will still operate as a single sequencer. If readers want to decentralize the protocol with us, then you should…
Build the future of Ethereum with us
This upgrade also marks the beginning of a new chapter in Optimistic Ethereum. The method of deleting code can only be executed correctly after you understand it, but we don’t just want everyone to understand-we want you to contribute!
Our development code has always been public, but after this upgrade, we will implement development transparency into the R&D stack. The newly created specification library optimistic-specs repo will serve as the latest source of facts for our agreement. There, everyone can search for specifications, ongoing research and development roadmaps, and anyone is welcome to contribute their own strength!
Thank you very much for the valuable expertise and early contributions of the Protolambda, Lightclient, and Magmo teams, who have written some PoCs and specifications.
Source link: medium.com
Disclaimer: As a blockchain information platform, the articles published on this site only represent the author’s personal views, and have nothing to do with the position of ChainNews. The information, opinions, etc. in the article are for reference only, and are not intended as or regarded as actual investment advice.
