Skip to content

Mainnet Stable Stop Slot Release 2.0.0

Compare
Choose a tag to compare
@amc-ie amc-ie released this 21 May 12:28
· 18408 commits to develop since this release
039296a

This release is the first phase of the Mina Mainnet upgrade that specifies the stop slots in the codebase that formally begins the upgrade process.


Node operators MUST upgrade to this version as soon as possible, starting immediately and before 27 May, 2024 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 2.0.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.


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 in just 2 weeks on upgrade day: June 4th, 2024, and thereby kicking off the upgrade process.

Stop Transaction Slot: At Tue Jun 4 9:00 UTC, this slot will be initiated. Blocks produced by upgraded stakeholders will be empty, and no transactions will be accepted.

Stop Network Slot: 5 hours after the stop-transaction-slot, 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 regading these milestones please see our high level plan here

After these two important stop slots, we’ll publish the post-upgrade Berkeley package. We’ll be working very closely with the community and the archive node operators during this time to migrate data from the network and validate the ledger state.


Supported environments include macOS, Linux (Debian 10, 11 and Ubuntu 20.04 LTS), and any host machine with Docker.

Complete Changelog since 1.4.1:

1.4.1...2.0.0

Connecting to the Mainnet network

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
sudo 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=2.0.0-039296a

Mina Archive:
sudo apt-get install --allow-downgrades -y mina-archive=2.0.0-039296a

Mina Archive Schema: create_schema.sql
Config File: var/lib/coda/config_039296a2.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, buster, or bullseye to select the base docker image.

Mina Daemon: minaprotocol/mina-daemon:2.0.0-039296a-CODENAME-mainnet
Mina Archive: minaprotocol/mina-archive:2.0.0-039296a-CODENAME
Mina Archive Schema: create_schema.sql
Mina Rosetta: minaprotocol/mina-rosetta:2.0.0-039296a-focal

Step by Step Guide:

Run mina daemon with the following seed list parameter:
--peer-list-url https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt

If you are running the correct version on the correct network, mainnet will show:

Chain id:     5f704cc0c82e0ed70e873f0893d7e06f148524e3f0bdae2afb02e7819a0c24d1
Git SHA-1:    039296a260080ed02d0d0750d185921f030b6c9c

Optional: For this release we have temporarily enabled node status tracking by default to help us track successful upgrade progress. This behaviour can be turned off by starting the node using the --disable-node-status flag.