Mainnet Beta Release 3.3.0-beta1 #18050
amc-ie
announced in
Announcements
Replies: 1 comment
-
|
Maybe the default file /usr/lib/systemd/user/mina.service content also needs some parameter changes. |
Beta Was this translation helpful? Give feedback.
0 replies
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
3.3.0-beta1is ready to test on Mainnet! This release includes a significant number of additions and improvements that will form the basis of the upcoming Mesa Upgrade. We have made significant performance improvements to the archive node process which should lower resource consumption considerably. We have also extended our operating system support based on your feedback to include Ubuntu 22.04 LTS (Jammy Jellyfish) and experimental ARM64 support for Ubuntu 24.04LTS (Noble) and Debian 12 (Bookworm).If you run into any issues, please include
Release: 3.3.0-beta1in the name of any issues you create. Please report any issues you encounter here or join the discussion!Some highlights of what has changed
New Features
Improvements
Bug fixes
Complete Changelog since 3.2.0:
3.2.0...3.3.0-beta1
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 has now reached EOL we will phase this out in future releases🚨
Upgrading & Connecting to Mainnet
Debian Packages:
Debian Repository: First, set up and update the
betaDebian 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=3.3.0-beta1-5b0a889Mina Archive:
sudo apt-get install --allow-downgrades -y mina-archive=3.3.0-beta1-5b0a889Mina Archive Schema: create_schema.sql
Config File:
var/lib/coda/config_5b0a8898.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:
gcr.io/o1labs-192920/mina-daemon:3.3.0-beta1-5b0a889-CODENAME-mainnetMina Archive:
gcr.io/o1labs-192920/mina-archive:3.3.0-beta1-5b0a889-CODENAME-mainnetMina Rosetta:
gcr.io/o1labs-192920/mina-rosetta:3.3.0-beta1-5b0a889-CODENAME-mainnetFor experimental ARM64 docker images replace
CODENAMEin the images below with your choice ofnobleorbookwormto select the desired image.Mina Daemon:
gcr.io/o1labs-192920/mina-daemon:3.3.0-beta1-5b0a889-CODENAME-mainnet-arm64Mina Archive:
gcr.io/o1labs-192920/mina-archive:3.3.0-beta1-5b0a889-CODENAME-mainnet-arm64Mina Rosetta:
gcr.io/o1labs-192920/mina-rosetta:3.3.0-beta1-5b0a889-CODENAME-mainnet-arm64Note: for ARM64 builds the GIT SHA-1 will be
9c856a80763d55a2de765bac6c96f4c776f7887b, this is due to changes in our build pipeline during the beta1 release. This is for the beta1 release only.Step 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 Mainnet Beta Release 3.3.0-beta1.
Beta Was this translation helpful? Give feedback.
All reactions