In the past week, the race to launch an EVM-compatible ZK rollup has been heating up:
zkSync launched their zkEVM mainnet (just two days later!)
Why's this happening? WTF is a zkEVM? How do I use one?
Let's dive into it.
Wait, what's wrong with Ethereum?
Ethereum Mainnet is able to process roughly 15 transactions per second. We all know what this means; huge gas prices and long finality times, leading to a grim user experience.
Depending on how deep down the rabbit hole you are at this point, you may already be familiar with solutions to address this; sidechains, layer 2s, rollups... all that good stuff.
These were all built because Ethereum is currently too popular for what it is capable of handling. Despite this, the Ethereum Foundation has agreed they are not going to sacrifice security/decentralization to improve scalability.
This balance between decentralization, security, and scalability is known as the scalability trilemma. The long-term vision of Ethereum is to achieve all three of these qualities.
Why should we improve scalability?
Scalability refers to how well Ethereum can handle the demand for transactions to be processed. If more transactions can be processed faster, two things happen:
Gas prices go down
Finality (how fast your transactions are finalized) gets faster
So, if we're not going to sacrifice decentralization, how do we make Ethereum more scalable? There are multiple different solutions that are either already being used today, in the research/testing phase, or recently shipped to mainnet 😉.
Let's explore some of the existing solutions first, why they have problems of their own, and then dive into ZK EVMs as the potential "final boss" of scaling solutions.
What's been built to address this so far?
Most solutions built to address the scalability of Ethereum usually come with some kind of sacrifice in the other two qualities in the scalability trilemma.
"it scales better... buuuuuut <insert downside here>", is usually how it goes*.*
Let's take a closer look at each of them.
Sidechains
A sidechain is a completely separate blockchain from Ethereum, with different histories, roadmaps, and even consensus algorithms.
In order for a side-chain to actually be a side-chain, it is required to have a two-way bridge connecting it with Ethereum Mainnet, where data can be transferred between the two chains.
Polygon's PoS (proof-of-stake) is the most popular example of a sidechain.
Polygon PoS boasts a ~10,000x lower gas fee per transaction, and ~450x increase in transactions per second than Ethereum. Polygon PoS is awesome. Some of the biggest brands in the world have chosen Polygon as their partner; Adidas, Meta, Stripe, Reddit, and more.
However, sidechains sacrifice some measure of decentralization or security to achieve this higher throughput.
You can dive deeper into the risk assessment of scaling solutions on sites such as L2BEAT. For example, if we take a look at Polygon PoS, we can see this:
In addition, despite these sacrifices, Polygon PoS has had struggles with scalability several times in the past.
For example, in 2022, a play-to-earn game called Sunflower Farmers sent gas prices skyrocketing after the game took up over 40% of the network's gas fees.
PhABC@phabcd
Looks like a bunch of @0xPolygon validators (~11%) are failing to submit blocks with this sudden surge in demand. If you are delegating to one of these failing validators, better contact them ASAP.
Full @DuneAnalytics dashboard here; dune.xyz/phabc/Polygon-…06:23 AM - 05 Jan 2022
More recently, transactions were failing from users' wallets due to incorrect gas estimations, as a result of the high demand on Polygon PoS.
Mikko Ohtamaa 🐮@moo9000Polygon finds out EVM does not scale, no matter how many hardforks you do12:23 PM - 16 Feb 2023
Rollups
Rollups are different from sidechains in the sense that they're not "separate" from Ethereum. Instead, they publish transaction results onto Ethereum mainnet; allowing them to derive the full benefits of Ethereum's security in the process.
Rollups work by allowing operators to bundle multiple off-chain transactions together outside the main EVM, and then submit them all together to Ethereum; achieving 10 to 100 times improvements in terms of scalability.
On a technical level, these batches are submitted to a "rollup" smart contract that is stored on Ethereum mainnet; which keeps track of the rollup's state.
There are two kinds of rollups that exist today:
Optimistic rollups
Zero Knowledge (ZK) Rollups
A bridge allows you to transfer funds or data between Ethereum mainnet and a rollup.
Optimistic Rollups
Optimistic rollups such as Optimism and Arbitrum One are called "optimistic" because they assume the transactions that they roll up are valid by default.
They don't post any proof that the transactions are valid to Ethereum. Instead, transactions are "innocent until proven guilty", which includes a fraud-proving scheme that enables the detection of invalid transactions.
A "challenge period" is available for parties to contest the results of a rollup transaction by submitting a fraud-proof that can see whether or not a fraudulent transaction took place in that rollup.
If one is detected, the transactions are re-executed and the state of the rollup is updated. The party who submits the fraudulent transactions incur a penalty, creating an incentive mechanism within the ecosystem.
Okay, this sounds great. What's the downside?
Because of this challenge period, (usually around 7 days), you must wait until the challenge period is over before you can perform this withdrawal to Ethereum mainnet over the bridge.
There's also some level of reliance that at least one honest person is checking for fraudulent transactions to challenge the state of the rollup.
ZK Rollups
Alright, we're almost at the juicy part.
ZK rollups, unlike optimistic rollups, do post validity proofs to prove the correctness of the changes they post to Ethereum mainnet.
These validity proofs are "zero-knowledge proofs"; meaning the details of the statement that the rollup provides can be proven as true, without revealing the actual contents of that statement, using either zk-SNARKs or zk-STARKs.
Learn more about how validity proofs work in zk-rollups.
This removes the requirement for a challenge period, as the transactions are provably true as soon as the rollup contract verifies the validity proof. This means you can withdraw funds from ZK rollups to Ethereum mainnet without waiting!
Awesome, but what's the catch?
Unlike the other solutions we've talked about so far, ZK Rollups are not compatible with the EVM. This means you can't just point your Solidity contract at a ZK Rollup and ship it, which you can do with all of the other solutions we've described.
Whereas, with other solutions, you can simply change the URL of your deployment script and deploy the exact same code to Ethereum, Polygon PoS, Optimism, Arbitrum, etc.
That's the catch. You cannot do this with ZK Rollups... Until now!
Enter, zkEVMs.
What is a zkEVM?
The main reason ZK rollups are not utilized is that they have not been EVM-compatible in the past, making it extremely difficult to actually build anything on them.
If I've done a good job explaining things so far, the name "zkEVM" is hopefully self-explanatory to you... A zkEVM is a zero-knowledge rollup, that is EVM compatible.
zkEVMs enable all the benefits of a ZK Rollup, with the same developer experience of building on any other EVM chain like Polygon or Ethereum. Combining the best of both worlds, and potentially providing an answer to the scalability trilemma.
This technology unlocks all existing web3 dapps to simply change their deployment scripts to a different RPC URL and ship directly to the zkEVM, exactly the same way they do now.
zkEVMs handle the batching of transaction execution and post cryptographic proof that the result of those transactions is correct to Ethereum mainnet, all while maintaining EVM compatibility.
This means that every smart contract on Ethereum or Polygon PoS can now also be deployed to a zkEVM. Drastically improving the scalability of the smart contracts and the dapps that use them.
"In the medium to long term, ZK rollups will win out in all use cases as ZK-SNARK technology improves." - Vitalik Buterin
How do I build on a ZK EVM?
With all of the hype and releases of ZK EVMs, how do you actually build on one?
At thirdweb (where I currently work), we just shipped support for any EVM chain, including all the zkEVMs such as Polygon zkEVM, zkSync, Scroll and more.
Consider checking out the below guide I helped review by my awesome colleague and friend @Avneesh Agarwal, which shows you how to:
Add a ZK EVM network to your wallet
Bridge funds from Ethereum to the ZK Rollup
Deploy your Solidity smart contract to a ZK EVM
How to Deploy a smart contract to Polygon zkEVM Testnet
Learn how to create and deploy a smart contract to the Polygon zkEVM testnet. Write a smart contract in solidity and deploy using thirdweb.
blog.thirdweb.com
Or check out this 3-minute video to shipping an NFT collection on Polygon's zkEVM:
Challenge accepted. Here's how you can create an NFT Drop on Polygon zkEVM in 3 minutes: twitter.com/Crypto_Texan/s…04:10 AM - 20 Feb 2023Crypto Texan | Polygon DeFi 🦇🔊💜 @Crypto_Texanimagine being the first NFT project to deploy on @0xPolygon’s zkEVM legendary, historic
Wrapping Up
That's it! I've tried my best to condense the past few weeks of reading about Ethereum scaling solutions into a 5 minute read for you :)
What do you think? Are zkEVMs the holy grail for scaling Ethereum? Or are we just getting started? Let me know!
If you enjoyed this article, there'll be many more just like it coming soon. Consider following me to get notified when those are released!
Top comments (0)