Discover and read the best of Twitter Threads about #marchtomainnet
Most recents (5)
There are only 10 days remaining on the #marchtomainnet. Yesterday we achieved a significant milestone, integrating our provers into the system and achieving an end-to-end system running on testnet.
But why do we need a prover? 🧵 (1/5)
But why do we need a prover? 🧵 (1/5)
To inherit layer 1 security, there must be a way that we can reconstruct the layer 2 state transitions directly from Ethereum. Differently from optimistic rollups (that rely on game theory), zkRollups rely on pure math to attest that state transitions are valid.
(2/5)
(2/5)
On our L2, a set of contracts will organize the transactions into batches & generate proofs for them. Those proofs are sent to a smart contract on L1 to verify that they are valid, ensuring that no transactions inside a batch were altered or contained invalid information.
(3/5)
(3/5)
Today, we’re extremely excited to announce that we have successfully completed Milestone 3: Proof Merging. With the integration of validity proofs, zkSync 2.0 is officially the world’s first-ever zkEVM running on a public testnet.
medium.com/@shazia_h/mile…
🧵 (1/5)
medium.com/@shazia_h/mile…
🧵 (1/5)
Many dev teams have been waiting for this: public verification of the validity proofs generated by the rollup & the final piece for the Alpha version of the system. As users transact with zkSync 2.0, these proofs provide a guarantee of the correctness of program execution.
(2/5)
(2/5)
We’ve had fully functional circuits in our dev environment for a while, but this milestone will enable everyone on our testnet to experience our ZK Prover which is fully operational with proof generation, aggregation & verification on-chain happening on the public testnet.
(3/5)
(3/5)
45 days remain on zkSync 2.0’s #marchtomainnet and the next major milestone on our roadmap is Proof Merging. Initial details on what this milestone will include 🧵 (1/5)
The Proof Merging milestone is what many development teams have been waiting for: Zero-knowledge (ZK) proofs to record the validity of transaction blocks on Ethereum.
(2/5)
(2/5)
In this milestone, we will add circuits’ witness generation for L2 blocks, integrate the prover to the current running system, and add proof verification to our L1 contract.
(3/5)
(3/5)
66 days to zkSync 2.0 on mainnet. The Dynamic Fees Milestone will be introduced with a regenesis on August 30, 2022. This takes us one step closer on our #marchtomainnet and our mission to scale Ethereum’s values and security.
🧵 (1/4)
🧵 (1/4)
For a recap on what is included in this milestone:
(2/4)
(2/4)
Friendly reminder: Regenesis will reset transaction history, token balances, and require developers to redeploy contracts. This only applies to zkSync 2.0 testnet and will not affect zkSync 1.0.
(3/4)
(3/4)
73 days to zkSync 2.0 on mainnet. The next roadmap milestone is Dynamic Fees and today we’re releasing a definition of what it’ll include. Next week we’ll release the exact date. Heads up to developers on testnet, this release will be a regenesis event. #marchtomainnet
🧵 (1/7)
🧵 (1/7)
Dynamic Fees
Today, all transactions on zkSync 2.0 testnet cost a fee that's independent of transaction logic & respective L1 cost. Our new fee model is similar to Ethereum's with L2-specific modifications. Each transaction will be priced based on the resources consumed.
(2/7)
Today, all transactions on zkSync 2.0 testnet cost a fee that's independent of transaction logic & respective L1 cost. Our new fee model is similar to Ethereum's with L2-specific modifications. Each transaction will be priced based on the resources consumed.
(2/7)
Dynamic Fees (cont’d)
To differentiate from the standard “gas,” our measurement unit is called “ergs.”
Ergs pay for:
1. Transaction execution & proof generation
2. L1 storage use
3. Proof verification on L1
4. Additional L1 interactions
(3/7)
To differentiate from the standard “gas,” our measurement unit is called “ergs.”
Ergs pay for:
1. Transaction execution & proof generation
2. L1 storage use
3. Proof verification on L1
4. Additional L1 interactions
(3/7)
