Original title: Baby Alpha Has Arrived!
Source: Matter Labs
Original article by Shazia, Matter Labs
MarsBit
Today, we reached the new Baby Alpha milestone and have now begun our march to Fair Onboarding Alpha and Full Launch Alpha, a significant achievement made possible by the dedication and support of our team, our ecosystem program, and our community. We have reached the Baby Alpha milestone and we want to take a moment to review what we have done and what we have ahead of us.
Our previous roadmap, shared earlier this year, outlined key milestones leading to the main Web. Below are the milestones for each commitment and delivery.
After releasing our first version of testnet in February 2022 and running it for a few months, we learned many new things that led us to make significant improvements to zkEVM, which gave us better scalability, performance, and security, and laid the foundation for future functionality. This includes significant architectural changes that significantly enhance the default EVM behavior and the implementation of account abstraction, which separates the object that holds the token (the account) from the object that authorizes the movement of the token (the signer) so that the development team can turn the account into a smart contract with its own logic.
The dynamic fee milestone includes a new fee model, an update to add payment supervisor support to the account abstraction, and EIP-1559 support. The costs of running the L2 protocol are high, and transaction fees must cover these costs. Although fees must be charged, we aim to keep them as low as possible. Dynamic charges allow users to pay only for their actual use of zkEVM. We are continuing to work to make those costs lower and lower. Read more here.
We opened up project registration by October, and have seen very interesting projects coming online and eager to deploy on zkSync. We can't wait to see the innovation of the teams that take advantage of the zkRollup feature. Haven't registered your project yet?And now here it isRegistration.
Our validators run on Ethereum TestNet (Goerli) and ensure state of the art cryptographic security. Forget game theory and rely on proof of fraud. We will continue to work to improve performance as we reach this milestone. These proofs provide assurance that the program is executing correctly (and the blockchain transitions from state to state) when a user transacts with zkSync 2.0. The system publishes these proofs into our smart contract on Ethereum, which allows us to verify the correctness of the proofs.Here,Read more.
Our work on zkSync 2.0 is just beginning. Here are details about what's ahead.
This milestone includes the deployment of the end-to-end system to the main network. At this stage, there are no external projects or users, so we can run a series of real money stress tests on the system to help us verify that it works and performs as expected. Safety is our top priority and we want to reduce the risk to the entire ecosystem.
At this stage, we will:
· Stress test the system with multiple use cases.
· Run security audits with top auditors.
· Run contests and bug bounty programs. The first oneIt's live now on Code4rena.
· Make sure that ourBlocks to browseProvides first-class information about transactions, blocks, and more.
· Improved zkSync 2.0 technologyThe document.
· Improve our tutorials and examples to make it as easy as possible for developers to get on board.
· Release SDKS in multiple languages, allowing the creation of more diverse applications.
At this stage, we have prioritized completing the end-to-end system, but have not tried to optimize performance -- particularly the system or the verifier -- or reduce costs. For this reason, it is not expected to provide a high performance (high TPS) system during Baby Alpha, but a fully functional system.
After we have completed our work for the Baby Alpha project, we will carefully implement the fair entry process. Fair entry means that we welcome all of our ecosystem projects and will not be involved in picking winners or favorites. At this stage, the system will be closed to the user.
To ensure the safety of zkSync and its users, Fair Onboarding Alpha will provide the project with the opportunity to test the system and conduct additional audits. At this stage, we will:
· Enable registered projects to deploy their contracts.
· Conduct more security audits, contests, and bug bounty programs.
· Extended developer tools, including improvements to our Hardhat plugin.
· Expand the set of programming languages in our SDK.
· Enable token bridging for testing and deployment purposes only.
· Expand our documentation and tutorials to include more information for end users and publish FAQs built on community feedback.
· Strive to improve prover performance to improve TPS. We communicate each time we make improvements and will share our work and findings publicly.
Once we have completed the previous set of security audits, contests, and bug bounties, and our ecosystem has fully tested their project on the system, zkSync 2.0 will be available to all users. More than 150 projects from across the ecosystem have been committed to launch on zkSync 2.0.
While we aim to achieve full Alpha launch by the end of this year, we will put safety first and consider extending the Fair Onboarding phase to 2023, ensuring we open the system to the community in the safest possible environment. At this stage, we will:
· Make zkSync 2.0 available to all projects and users.
· Expand bridging capabilities and announce bridging projects.
· Run additional security audits.
· Strive to reduce the overall cost of contract deployment and transactions.
· Implement the infrastructure of external reading nodes run by third parties.
· Improve TPS performance to at least an order of magnitude higher than Ethereum.
Going live with zkSync 2.0 is a key milestone, but we'll be doing a lot more in 2023.
As a result of the feedback we have received from both the closed and open phases of zkSync 2.0, we are committed to providing a better experience for both builders and end users. At this stage, we will:
· Significantly optimize protocols to reduce performance and cost.
· Support more common development tools, such as Truffle, Waffle, Foundry, Tenderly, etc.
· Create plug-ins for ides such as Remix and VSCode.
· Open our Block Explorer API for external use.
· Release our transaction debugger to the public. With it, developers can re-run transactions and follow instructions to track what is happening at the zkEVM level one by one.
· Improve the tap experience. Create zkCheckout for zkSync 2.0.
· Start zkSync v1 and v2 Bridges.
· There is more to be defined based on community feedback.
Layer 2 is the first step toward extensibility, developer experience, and user experience. zkSync's EVM-compatible Layer 3 proof-of-concept "opportunity" will materialize in the first quarter of 2023, bringing a 10x starry moment to Ethereum. We will provide:
A Layer 3 HyperChain prototype built on top of Layer 2 allows the ecosystem to study and experiment with it. Development of Kickstart developer tools, including the CLI and SDK, to strip away and interact with your layer 3.
To support Ethereum's mission, we will decentralize the zkSync 2.0 protocol, including proof generation, block production, and transaction verification. We are already thinking about how to decentralize parts of the system and will provide clear instructions on how to run the nodes.
The original link
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