Upcoming Astar zkEVM Upgrade & Maintenance

Hello Astar Community,

Mark your calendars for the Astar zkEVM upgrade, set to enhance functionality and performance across zKyoto testnet and Astar zkEVM mainnet.

The Astar zkEVM network will be put under maintenance for a few hours to be upgraded from Fork ID 7 to Fork ID 9 (Polygon CDK version Elderberry v2). The native bridge will be unavailable for 2 hours before the maintenance and during maintenance.

Event Details:

:white_small_square: zKyoto Testnet Update

  • Date: Apr-08-2024
  • Time: 12 PM UTC
  • Duration: ~ 2 hours

:white_small_square: Astar zkEVM Mainnet Update

  • Date: Apr-10-2024
  • Time: 12 PM UTC
  • Duration: ~ 2 hours

Projects please update the nodes after the Astar zkEVM upgrade is finished.

Node version: 0.6.4-cdk.2

Instructions to update nodes

1.Stop the RPC, Synchronizer and Executor components;
2. Update node (RPC and Synchronizer) to 0.6.4-cdk.2;
3. Update Prover/Executor to v6.0.0 (Elderberry 2);
4. Start the components in this order:

  1. Executor
  2. Synchronizer
  3. RPC

:point_right: Things to note :point_left:

  • This update is for the migration from Fork ID7 to Fork ID9 (zkEVM)
  • Upgrade to Polygon CDK version Elderberry v2 (Fork ID 9) for enhanced features and fixes.
  • Please note that both the network and bridge will be unavailable during the upgrade process. (~ 2 hours)
  • After the update, dApp developers and end users will not be required to take any action. However, infrastructure developers will need to take the necessary steps.

For inquiries or assistance, refer to this forum post and Astar Discord.

12 Likes

This information is extremely important! Our job now will be to communicate it on all our platforms.

1 Like

zKyoto Network Upgrade

We will perform an upgrade of the zKyoto tesntet today (April 10, 2024) at 12:00 PM UTC to migrate the network from Fork ID7 to Fork ID9 (Polygon CDK version Elderberry v2).

zKyoto network and the native bridge won’t be available during a period of around 2 hours.

Projects please update the nodes after the Astar zkEVM upgrade is finished.

Node version: 0.6.4-cdk.5

Instructions to update nodes

1.Stop the RPC, Synchronizer and Executor components;
2. Update node (RPC and Synchronizer) to 0.6.4-cdk.5;
3. Update Prover/Executor to v6.0.0 (Elderberry 2);
4. Start the components in this order:

  • Executor
  • Synchronizer
  • RPC
5 Likes

Hello Builders

As part of our ongoing commitment to security and performance excellence, we are issuing an immediate call to action for all projects utilizing Astar zkEVM mainnet permission-less RPC nodes!

It is critical that you update your nodes to the latest version at the earliest opportunity. This update is necessary to ensure optimal functionality, security, and compatibility with upcoming enhancements.

Update Details for Astar zkEVM mainnet:
Please update your Node and Prover/Executor versions to the following:

Action Required:

  1. Stop all nodes
  2. Delete all data of the state_db (all content of /var/lib/zkevm/statedb if you installed following the documentation)
  3. Download and apply the latest versions of the zk node and prover (=executor) as specified above.
  4. Restart the nodes
  5. For those utilizing indexers/subgraphs or maintaining local Astar zkEVM on-chain databases, we recommend re-synchronization via Startale/Gelato RPC from Transaction batch #17883 to ensure accurate data representation and prevent user-facing errors.

We appreciate your prompt attention to this matter and your cooperation in keeping our network secure and efficient!

Let us know if you have any further questions!

5 Likes