This release is the first phase of the Mina Mainnet Mesa upgrade that specifies the stop slot in the codebase that formally begins the Mesa upgrade process.
Node operators using the manual upgrade process MUST upgrade to this version as soon as possible, starting immediately and before 3rd September, 2026 to ensure we have a maximum percentage of stake running on this new version to successfully continue with the planned upgrade.
It is crucial for block producers to continue running their nodes with version 3.5.0 until the stop network slot is reached so that the network reaches consensus on which block to upgrade from. The team at o1Labs will also be collecting network data from these nodes for the post-upgrade release build.
If you would prefer an easier upgrade experience, we recommend that you use our new automode upgrade mechanism that allows for a hands free, seamless transition to the new era and only requires one upgrade.
If you run into any issues, please include Release: 4.0.0-mainnet in the name of any issues you create. Please report any issues you encounter here or join the discussion!
This release will set the stage for the upcoming Mainnet upgrade by defining the stop slots in the codebase. This stop slot will take effect on upgrade day: September 3rd, 2026, and thereby kicking off the upgrade process.
Stop Transaction Slot: Thursday September 3rd 10:00 UTC, this slot will be initiated. Blocks produced by upgraded stakeholders will be empty, and no transactions will be accepted.
Stop Network Slot: Thursday September 3rd 15:00 UTC, nodes in the Mina network will stop creating new blocks, marking a pause in block production. This is intentional and necessary for the upgrade to occur smoothly.
For more information regarding these milestones please see our high level plan here
After these two important stop slots, we’ll publish the post-upgrade Mesa package.
Note - For this release we have temporarily enabled node status tracking by default to help us track the successful progress towards the mainnet upgrade. This behaviour can be turned off by starting the node using the --node-status-url "" flag.
Supported environments include macOS, Linux (Debian 11, 12 and Ubuntu 20.04 LTS, Ubuntu 22.04 LTS & Ubuntu 24.04 LTS), and any host machine with Docker.
Upgrading & Connecting to Mainnet
Debian Packages:
Debian Repository: First, set up and update the stable Debian Repository for your platform with the following commands:
sudo rm /etc/apt/sources.list.d/mina*.list
echo "deb [trusted=yes] http://packages.o1test.net $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/mina.list
sudo apt-get update
Then, install the package(s) that you need:
Mina Daemon: sudo apt-get install --allow-downgrades -y mina-mainnet=3.5.0-mainnet-stop-slot-5e100ee
Mina Archive: sudo apt-get install --allow-downgrades -y mina-archive=3.5.0-mainnet-stop-slot-5e100ee
Mina Archive Schema: create_schema.sql
Config File: var/lib/coda/config_5e100ee6.json
Docker Images:
Every docker image is built for each of the supported platforms, replace CODENAME in the images below with your choice of focal, jammy, noble, bullseye or bookworm to select the base docker image.
Mina Daemon: minaprotocol/mina-daemon:3.5.0-mainnet-stop-slot-5e100ee-CODENAME-mainnet
Mina Archive: minaprotocol/mina-archive:3.5.0-mainnet-stop-slot-5e100ee-CODENAME-mainnet
Mina Rosetta: minaprotocol/mina-rosetta:3.5.0-mainnet-stop-slot-5e100ee-CODENAME-mainnet
Step by Step Guide:
Docker only Make sure to run with:
--peer-list-url https://bootnodes.minaprotocol.com/networks/mainnet.txt or add PEER_LIST_URL=https://bootnodes.minaprotocol.com/networks/mainnet.txt to your .mina-env.
(note - the older https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt is still functional but we advise users to migrate to the newer one when possible).
Run mina daemon with:
mina daemon --peer-list-url https://bootnodes.minaprotocol.com/networks/mainnet.txt
Check out our documentation for complete instructions on using this version to connect to Mainnet.
If you are running the correct version on the correct network MAINNET, mina client status will show:
Chain id: a7351abc7ddf2ea92d1b38cc8e636c271c1dfd2c081c637f62ebc2af34eb7cc1
Git SHA-1: 5e100ee61cde1b35efc9642dbc6df84259a64c41