Mina Mainnet Stable 4.0.0 Mesa Release #19337
amc-ie
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🎉The o1Labs team is proud to announce that the 4.0.0 Mesa Stable Release is now ready and available for Mainnet! 🎉
This release represents the final stage in the Mainnet manual upgrade process which concludes the execution of the upgrade mechanism for this network. This mina daemon release only applies if you are using the legacy stop slot version or are joining the network for the first time. If so, you will not be able to connect to the network without using this version. The mina daemon upgrade is not necessary for those having used the automode version for the upgrade.
If you run into any issues, please include
Release: 4.0.0-mainnet-mesain the name of any issues you create. Please report any issues you encounter here or join the discussion!What’s Included in the Mesa Upgrade?
The Mesa Upgrade encompasses four Mina Improvement Proposals (MIPs) and one upgrade mechanism enhancement:
Complete Changelog since 3.4.0/Berkeley:
3.4.0...4.0.0-mainnet-mesa
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.
🚨NOTE - as Ubuntu 20.04 and Debian 11 have reached EOL we will not support these platforms in future releases🚨
Upgrading & Connecting to Mainnet
Debian Packages:
Debian Repository: First, set up and update the
stableDebian Repository for your platform with the following commands:Then, install the package(s) that you need:
Mina Daemon:
sudo apt-get install --allow-downgrades -y mina-mainnet=4.0.0-6850301Mina Archive:
sudo apt-get install --allow-downgrades -y mina-archive=4.0.0-6850301Mina Archive Schema: create_schema.sql
Config File:
var/lib/coda/config_68503010.jsonDocker Images:
Every docker image is built for each of the supported platforms, replace
CODENAMEin the images below with your choice offocal,jammy,noble,bullseyeorbookwormto select the base docker image.Mina Daemon:
minaprotocol/mina-daemon:4.0.0-6850301-CODENAME-mainnetMina Archive:
minaprotocol/mina-archive:4.0.0-6850301-CODENAME-mainnetMina Rosetta:
minaprotocol/mina-rosetta:4.0.0-6850301-CODENAME-mainnetStep by Step Guide:
Docker only Make sure to run with:
--peer-list-url https://bootnodes.minaprotocol.com/networks/mainnet.txtor addPEER_LIST_URL=https://bootnodes.minaprotocol.com/networks/mainnet.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://bootnodes.minaprotocol.com/networks/mainnet.txtCheck 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 statuswill show:This discussion was created from the release Mina Mainnet Stable 4.0.0 Mesa Release.
All reactions