Original title: "One article to understand the roadmap of L2 solution zkSync 2.0, which is planned to be launched in August"< blockquote>Translation of the original text: Babbitt
After a year of total self-isolation (and taking many precautions), we are delighted to have our team together for a week in Dubai, which is safer from COVID-19 .

The team had plenty of discussions, workshops and brainstorming to refine the final aspects of the zkSync 2.0 design. The result of this week is our updated development roadmap. Today, we are excited to share these plans with you.

EVM-based programming model and composability
From a user and developer perspective, the design of zkSync 2.0 is actually no different from the EVM:
Portability of existing Solidity source code
We have made progress in implementing the new Turing-complete ZincVM Great progress. In addition to the existing Zinc programming language, anything capable of generating an intermediate representation in Yul (hello, Solidity!) can now be compiled.
It is worth noting that ZincVM is based on LLVM, so we're taking advantage of optimizations and tooling for it. In the future, it will also allow us to easily support other programming languages, such as the native Rust language.
We expect most Solidity contracts to compile with no or minimal changes.
Native support for all Ethereum wallets
zkSync 2.0 will natively support Ethereum’s ECDSA signature scheme (thanks to efficient loop implementation of PLONK based lookup tables). This means that all Ethereum wallets can be used out of the box, without signing keys in the browser and without special integration work.
20,000 + TPS — Scalability beyond zk Rollup
This is what we are very excited about thing! The NFT boom hints at imminent mainstream adoption. Unfortunately, attracting millions of new mainstream users is a difficult problem that neither Rollup (whether zk Rollups nor Optimistic Rollups) can handle alone due to the inherent limitations of on-chain data availability.
Recognizing this, zkSync 2.0 will introduce a new overall architecture that provides a mix of zkRollup and zkPorter accounts (users are free to choose, And fully interoperable):
We will share more in a separate post later.
We fully understand that many projects will not last until this summer. This is why parts of our team continue to develop the battle-tested zkSync 1.x to support more use cases earlier.
For payment use cases, zkSync 1.x is the clear winner among all existing Rollups today in terms of fees and user experience. In the recent 9th round of Gitcoin grants, 82% of donation payments were made via zkSync.
More and more wallets have announced support for zkSync, including Argent and imToken. We will also continue to work on integrating exchanges to bypass L1 and directly access L2 funds in and out experience.
Fungible token trading functionality (via atomic swaps/limit orders) will be available directly on L2 in April, with the assistance of liquidity providers - We are working with liquidity providers. Early on, we decided not to implement AMM functionality directly in zkSync: that's easy to do in v2.0 (see Curve on closed testnet), and we fundamentally don't want to compete with projects looking to adopt zkSync. On the other hand, anyone can offer transactions via atomic swaps, which will greatly expand the capabilities of existing zkSync 1.x users.
The most interesting update is that zkSync 1.x will soon support native minting, transfers and atomic swaps of NFTs with the full security guarantee of zkRollup! The NFT functionality should go live on mainnet in May.
We are accepting partners, the number is limited, they can use NFT and swap/limit order function early.
Original link blockquote>
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia