A new, more performant and stable sequencer is now live on Polygon zkEVM Mainnet Beta!

This is a big technical achievement that will have ramifications not only for Polygon zkEVM builders and dApps, but for chains built with Polygon CDK, too.

After a 10-day timelock, the Eggfruit upgrade is now live on Polygon zkEVM Mainnet Beta.

So what does this mean for developers? 

• More tps: New sequencer = better transaction ordering. Built by Gateway, the team behind the widely used Ethereum Erigon client, the cdk-erigon sequencer is optimized to create a more stable, higher-throughput network. Stay tuned for updates as onchain activity provides real-world metrics. 
• Stability: Polygon PoS can handle enormous influxes of traffic without blinking (think 16M/transcriptions in a day); the Eggfruit upgrade brings more stability to the beta version of Polygon zkEVM, giving developers peace of mind.
• Double the zkCounters: zkCounters provide a ceiling on the amount of computation that can be used to generate a proof. With 2x more zkCounters, the Eggfruit upgrade makes more complex transactions possible. 
• Deprecating the legacy RPC Node: Last month, the RPC Node built by Gateway became the network’s recommended Node. Following the Eggfruit upgrade, all infra providers will need to begin running the cdk-erigon RPC Node, if they haven’t already. 

For devs who want to verify the upgrade: Because Eggfruit touches the PolygonZkEVM.sol consensus contract, the timelock was set for the security and protection of all devs and users, following the network’s governance model. The intention was to give sufficient time to withdraw funds, if desired, before the upgrade was implemented. 

Here’s how you can independently verify that the source code, available on GitHub, matches the code deployed on the network:

• Verify deployment of proof verifier smart contract

What’s in (an) Eggfruit?

The Eggfruit upgrade includes a new, performance-optimized sequencer that will play a crucial role not only in Polygon zkEVM Mainnet Beta, but all chains built with Polygon CDK as well.

Polygon zkEVM

By harnessing cdk-erigon’s efficiency for the task of ordering and batching transactions, Polygon zkEVM’s sequencing has become that much faster. 

As a result, expect network throughput to increase, providing a better user and developer experience. 

This upgrade follows last month’s rollout of cdk-erigon as the network’s recommended RPC Node.

With Eggfruit upgrade live on mainnet, all infra providers will need to begin running the cdk-erigon RPC Node, if they haven’t already. 

Here is how.

For chains built with Polygon CDK, the cdk-erigon RPC provides 150x faster synchronization speed. 

Will infrastructure providers need to perform upgrades?

Short answer: Yes.

Infrastructure providers responsible for maintaining the Polygon zkEVM network will need to update to the latest versions now that the upgrade is live on mainnet.

Find the latest release on GitHub, v1.2.24, here, and the Docker link, here. 

Do dApps on mainnet beta need to do anything?

Short answer: No. Existing dApps on Polygon zkEVM do not need to take any action. 

But developers should see how the upgrade improves network performance!

The Eggfruit has been eaten. Onward to a more performant future for Polygon zkEVM!

Tune into the blog and our social channels to keep up with updates about Polygon.

The future of Web3 is aggregated.

Website | Farcaster | X (Twitter) | Forum | Telegram | Discord | Instagram | LinkedIn | Polygon Knowledge Layer