Skip to main content

Pre-Upgrade

During the Pre-Upgrade phase, node operators prepare their infrastructure for the Mesa hard fork. Select your role below and work through each item on the checklist.

Readiness Checklist​

Infrastructure​

  • Server meets hardware requirements
  • Port 8302 (or custom --external-port) is open and reachable from the internet
  • If behind NAT/firewall, --external-ip is set to your public IP
  • Node is configured for auto-restart (systemd or equivalent)

Keys and Credentials​

  • Block producer key file is accessible and backed up
  • libp2p keypair is accessible (same key can be reused from before the upgrade)

Software Upgrade​

  • Chosen an upgrade mode: automode (recommended) or manual
  • Upgraded node to the current stable version
  • Installed stop-slot release 3.x.x before the stop-transaction-slot
  • If using automode: installed both mina-{network}-prefork-mesa and mina-{network}-postfork-mesa packages (or the automode Docker image)
  • If using manual mode: installed mina-mainnet=3.x.x (stop-slot release only)

Verification​

  • Node is running and synced after the upgrade
  • Node status shows correct version: mina client status

Detailed Steps​

Block Producers and SNARK Workers​

  1. Provision servers that meet the minimum hardware requirements, including 32 GB RAM and support for AVX and BMI2 CPU instructions.
  2. Upgrade nodes to the stop-slot release version 3.x.x, which has built-in stop slots.

If you are using Automode, no further action is needed until the Post-Upgrade phase — your node will handle the transition automatically.

Archive Node Operators and Rosetta Operators​

Two upgrade processes are available: trustless and trustful. If you want to perform the trustless upgrade, follow the steps below; otherwise, proceed to the Upgrade phase. The trustful approach relies on o1Labs database exports and Docker images and doesn't require any actions at this stage.

  1. Trustless upgrade:
    • Perform the archive node schema upgrade. Since Mainnet is a long-lived network, the upgrade process is a very fast operation and boils down to running the upgrade script against your archive. It should not take more than 1 minute, depending on your server specification and infrastructure.
    • For more information on the archive node upgrade process, please refer to the Archive Upgrade section.
  2. Provision servers that meet the minimum hardware requirements, primarily 32 GB RAM.
  3. Upgrade all nodes to the stop-slot release 3.x.x before the pre-defined stop-transaction-slot.

Exchanges​

  1. Make sure to test your system integration with Mesa's new features. Pay special attention to:
    • If you rely on the archive node SQL database tables, please review the schema changes in the Appendix.
  2. Provision servers that meet the minimum hardware requirements, particularly 32 GB RAM.
  3. Upgrade all nodes to the stop-slot release 3.x.x before the pre-defined stop-transaction-slot.