This Mesa upgrade release contains everything you need to automatically upgrade to the Mesa era on Devnet. The new approach will allow for much faster and seamless hard forks\upgrades for Mina in future and we are very excited to share it with you!
If you would prefer to handle the upgrade manually (i.e. in two parts), we recommend that you use our legacy stop slot build. This will require an additional upgrade after the Mesa Devnet netwokr starts; this will be made after the HF takes place.
For this release we have temporarily enabled node status tracking by default to help us track the successful progress towards the devnet upgrade. This behaviour can be turned off by starting the node using the --disable-node-status flag.
For detailed instructions on the upgrade schedule and recommended connection parameters, please refer to our upgrade documentation.
If you run into any issues, please include Release: 4.0.0-devnet in the name of any issues you create. Please report any issues you encounter here or join the discussion!
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 Devnet
Debian Packages:
Debian Repository: First, set up and update the alpha 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) alpha" | sudo tee /etc/apt/sources.list.d/mina-alpha.list
sudo apt-get update
Then, install the package(s) that you need:
Mina Daemon: sudo apt-get install --allow-downgrades -y mina-devnet=3.4.0-alpha1-22d9374
Mina Archive: sudo apt-get install --allow-downgrades -y mina-archive=3.4.0-alpha1-22d9374
Mina Archive Schema: create_schema.sql
Config File: var/lib/coda/config_22d93743.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: gcr.io/o1labs-192920/mina-daemon:3.4.0-alpha1-22d9374-CODENAME-devnet
Mina Archive: gcr.io/o1labs-192920/mina-archive:3.4.0-alpha1-22d9374-CODENAME-devnet
Mina Rosetta: gcr.io/o1labs-192920/mina-rosetta:3.4.0-alpha1-22d9374-CODENAME-devnet
For experimental ARM64 docker images replace CODENAME in the images below with your choice of noble or bookworm to select the desired image.
Mina Daemon: gcr.io/o1labs-192920/mina-daemon:3.4.0-alpha1-22d9374-CODENAME-devnet-arm64
Mina Archive: gcr.io/o1labs-192920/mina-archive:3.4.0-alpha1-22d9374-CODENAME-devnet-arm64
Mina Rosetta: gcr.io/o1labs-192920/mina-rosetta:3.4.0-alpha1-22d9374-CODENAME-devnet-arm64
Step by Step Guide:
Docker only Make sure to run with:
-peer-list-url https://storage.googleapis.com/o1labs-gitops-infrastructure/devnet/seed-list-devnet.txtor addPEER_LIST_URL=https://storage.googleapis.com/o1labs-gitops-infrastructure/devnet/seed-list-devnet.txtto 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://storage.googleapis.com/o1labs-gitops-infrastructure/devnet/seed-list-devnet.txt
Check out our documentation for complete instructions on using this version to connect to Devnet.
If you are running the correct version on the correct network DEVNET, mina client status will show:
Chain id: 29936104443aaf264a7f0192ac64b1c7173198c1ed404c1bcff5e562e05eb7f6
Git SHA-1: 22d93743f507e364492c2380fe1b06c2032b3b1c