Mina Devnet 4.0.0 Automode Upgrade Release #19214
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.
❗ This release is only to be used as part of the Devnet Automode upgrade process ❗
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-devnetin the name of any issues you create. Please report any issues you encounter here or join the discussion!Complete Changelog since 3.4.0/Berkeley:
3.4.0...4.0.0-devnet
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
alphaDebian 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-devnet-automode=4.0.0-devnet-2dc9218Mina Archive:
sudo apt-get install --allow-downgrades -y mina-archive-devnet=3.5.0-devnet-stop-slot-849edfaMina Archive Schema: create_schema.sql
Config File:
var/lib/coda/config_2dc9218f.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-devnet-2dc9218-CODENAME-devnetMina Archive:
minaprotocol/mina-archive:3.5.0-devnet-stop-slot-849edfa-CODENAME-devnetMina Rosetta:
minaprotocol/mina-rosetta:3.5.0-devnet-stop-slot-849edfa-CODENAME-devnetStep 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.txtCheck 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 statuswill show:This discussion was created from the release Mina Devnet 4.0.0 Automode Upgrade Release.
All reactions