Learn how to participate in the ConsenSys zkEVM testnet

Original title: "ConsenSys Launches Private Beta zkEVM Testnet To Scale Ethereum》

Original title: "

Original source: ConsenSys

Compilation of the original text: Overnight Porridge

summarize

ConsenSys zkEVM is a new zk-rollup network designed by ConsenSys R&D and operated by ConsenSys. The rollup is the culmination of years of research and provides full Ethereum Virtual Machine (EVM) compatibility, so developers can use familiar tools such as MetaMask, Truffle, and Infura to deploy and manage applications as if they were directly using Ethereum The same as Fang.

open beta

Users will be able to cross-chain assets between the Goerli testnet and the zkEVM, using their familiar tools, infrastructure and wallets to test their smart contracts and dapps. Out-of-the-box integration with existing Ethereum toolchains makes it possible for this L2 to achieve the experience, security, and decentralization of Ethereum, but with significantly lower transaction fees.At DevCon, ConsenSys released a near-complete arithmeticization of zkEVMspecification, and announced plans to launch a private testnet. As of now, ConsenSys has received more than 150,000 registration applications. ConsenSys also recently released the zkEVM to be used inprover scheme

. Next week, ConsenSys will begin internal testing on the testnet. Starting in January, ConsenSys will gradually "allow" external users who register on the network, and allow users to join in batches to ensure the stability and security of the system.

If you want to participate in the beta, but haven't signed up, ConsenSys is already atherehere

Registration reopened.

Here is everything you need to know about the testnet:

ConsenSys：1. Why build this zkEVM?

ConsenSys R&D and others in the ecosystem have been working on a way to wrap EVM computations in zero-knowledge proofs to create zkEVM implementations. This zkEVM handles native EVM bytecode for proofs and verification to allow the execution of Solidity smart contracts and enables developers to reap the benefits of zk-rollup using their familiar developer tools and infrastructure. you can atherehere

Learn more about our goals and specifications.

ConsenSys：Users canherehere

Sign up for our waitlist. The private testnet phase will run for approximately three months to allow our protocol team to receive feedback on the developer and user experience, at which point we will decide on the future of the testnet.

ConsenSys：3. If I have already registered, do I need to re-register?

No, if you have completed one of our previous forms, your details have been captured and there is no need to register again. You may receive an email from Infura regarding next steps. You will need an Infura account to access the private testnet as it is currently licensed. Once you receive the account confirmation email, the ConsenSys zkEVM card will appear in your Infura dashboard.

ConsenSys：4. When can I experience it?

In January 2023, ConsenSys will begin whitelisting registered users in the order in which they were registered. Our goal is to onboard a batch of new users each day, starting small and increasing the size of each batch as we monitor activity. We have received over 150,000 registration applications and expect this number to grow.

With such high demand, it may take several weeks for you to gain access. While our goal is to have all users join the testnet, we may not be able to accommodate everyone on the waitlist.

ConsenSys：5. How does the test work?

We will send you an email when we are ready to add your account to the testnet. This email will be from Infura and will outline how to configure your Infura account, select a ConsenSys zkEVM NIC, and copy your RPC endpoints for import into MetaMask. This will allow you to interact with the zkEVM network.

ConsenSys：6. Do I need to use Infura to participate in the testnet?

Required during the private Beta testnet, users need to have an Infura account to retrieve their unique RPC endpoint to test the network. If you don't have an Infura account, you'll need to create one using the same email address you used to sign up for the testnet. Signing up for an Infura account is free and only takes a few minutes.

This is required because the testnet is currently a private beta testnet and not permissionless.

ConsenSys：7. Which protocols are participating?

We're talking to top protocols in all Web3 segments from Stablecoins, DeFi, NFT Marketplaces, Gaming, Social.

A full list of partners, along with sample applications, will be shared on our upcoming testnet portal. If you would like to submit your project to be deployed to zkEVM and added to the portal, please fill out the form below.

ConsenSys：8. Will it be open source?Yes, the plan is to open source both the specification and the code. You can read our release during DevCon 6arithmetic specification. We will provide updates when this specification and source code are documented and ready to be evaluated by the community. Additionally, we recently published。

prover program

ConsenSys：9. How will you reward early testers?

We're discussing how to reward those who help us test and improve the product, but don't have the details yet.

ConsenSys：10. Will there be tokens?

The network is still in closed beta, so it is too early to talk about launching a token.

ConsenSys：11. What performance should I expect?

We are tuning the testnet to focus on security and performance for a restricted user set, so max throughput is less important at this stage.

ConsenSys：12. What is the difference between our zkEVM product and other available products?There are different types of zkEVM, Vitalik'sblog post

describes the type of zkEVM, our Rollup aims to be a type 2 zkEVM. Type 2 zkEVM is bytecode compatible, which means we are most compatible with Ethereum and the EVM, making it easy for developers to build and maintain applications on Layer 2.

We do not use transpilers or custom compilers to generate zk proofs for Solidity smart contracts. We use compiled Solidity bytecode. We believe this approach reduces the apparent risk of vulnerabilities and hacks.

ConsenSys：13. What opcodes and precompilers are supported?