Skip to main content

Upgrade

Starting at the stop-network-slot the network will not produce nor accept new blocks, resulting in halting the network. During the upgrade period, o1Labs will use automated tooling to export the network state based on the block at the slot just before the stop-transaction-slot. The exported state will then be baked into the new Mesa build, which will be used to initiate the upgraded network. It is during the upgrade window that the Mesa network infrastructure will be bootstrapped, and seed nodes will become available. o1Labs will also finalize the archive node upgrade and publish the PostgreSQL database dumps for import by the archive node operators who wish to bootstrap their archives in a trustful manner.

There is a tool available to validate that the Mesa node was built from the pre-upgrade network state. To validate, follow the instructions provided in this location.

Block Producers and SNARK Workers​

info

If you are using Automode, your node handles this phase automatically. It will transition to the Mesa network without manual intervention. Skip to Post-Upgrade for monitoring guidance.

If you are using Manual mode:

  1. During the upgrade phase (between stop-network-slot and the publishing of the Mesa release), block producers can shut down their nodes.
  2. After the publication of the Mesa node release, block producers and SNARK workers should upgrade their nodes and be prepared for block production at the genesis timestamp, which is the slot when the first Mesa block will be produced.
  3. It is possible to continue using the same libp2p key after the upgrade. Remember to adjust the new flag to pass the libp2p key to the node.

Archive Node Operators and Rosetta Operators​

  1. Upon publishing the archive node Mesa release, archive node operators and Rosetta operators should upgrade their systems. There will be both Docker images and archive node releases available to choose from.
  2. Depending on the chosen upgrade method:
    • Trustless
      • Operators should direct their Mesa archive process to the previously upgraded database.
    • Trustful
      • Operators shall import the SQL dump file provided by o1Labs to a freshly created database.
      • Operators should direct their Mesa archive process to the newly created database.

Exchanges​

  1. Exchanges shall disable MINA deposits and withdrawals during the entirety of the upgrade downtime, since the stop-transaction-slot until the Mainnet Mesa network is operational.
  2. After the Mesa releases are published, exchanges should upgrade their nodes and prepare for the new network to start block production.