Following the post from last week, the 10-day timelock for upgrading Polygon zkEVM Mainnet Beta was initiated at 1PM CET. The transaction containing the proposal for Elderberry and the upgraded contract can be checked here:
The changelogs for the node and prover can be found here:
The timelock concludes on March 07.
Here’s what’s included in Elderberry, how to use it on testnet, and what you’ll need to do once it’s live on Polygon zkEVM Mainnet Beta. If you have questions, though, post them below and we’ll get the gigabrains on the Polygon zkEVM team to reply.
What’s in Elderberry? Important optimizations to the ROM that will reduce certain out of counter errors on the network and some additional fixes to last month’s Etrog upgrade. The ROM interprets the execution logic of all transactions and all opcodes for Polygon zkEVM—it is to Polygon zkEVM what the EVM Interpreter is to Ethereum. (For more on the ROM, see the Polygon Knowledge Layer.)
How can you independently verify the upgrade? Instructions can be found on GitHub.
The Elderberry upgrade is available on the Cardona (Sepolia) testnet. Here’s how to connect:
- Network Name: Polygon zkEVM Cardona Testnet
- Bridge UI: https://bridge-ui.cardona.zkevm-rpc.com
- RPC URL: https://rpc.cardona.zkevm-rpc.com
- Chain ID: 2442
- Currency symbol: ETH
- Block Explorer: https://cardona-zkevm.polygonscan.com/
- Faucet: https://faucet.polygon.technology/
When will Elderberry go live on mainnet? Assuming the network is stable, Elderberry will likely go live on mainnet around March 07.
Do I need to do anything once it’s live? It depends. If you’re an infra dev that helps maintain network infrastructure, you’ll need to update to the latest versions of the node, prover, and bridge service. We’ll update this post with those links, once they’re available. If you’re a dApp dev or end user, you won’t need to take any action. Everything from your perspective will be the same.
We’ll update this post once the Elderberry upgrade is live on mainnet.