❗ This release is only for UMT testing ❗

This is the final release in the UMT testing phase which concludes the execution of the upgrade mechanism. This release marks a new upgraded network with all of the Berkeley functionality
that will feature on Mainnet when subsequently upgraded. This version of the daemon is not compatible with the previous builds and as such it is necessary to either install this on a clean system or to remove the previous builds and artifacts. The steps on how to do this are contained within the release notes.

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

Removing previous builds

mina client stop
sudo apt remove mina-devnet=1.0.1umt-stop-slot-992168e 
sudo mv /tmp/coda_cache_dir /tmp/coda_cache_dir_bak
sudo mv $HOME/.mina-config $HOME/.mina-config_bak   

Connecting to the UMT network

Debian Packages:

Debian Repository:
First, set up and update the umt 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) umt" | 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-devnet-hardfork=2.0.0umt-hardfork-automation-umt-eb0a6d0
Mina Archive: sudo apt-get install --allow-downgrades -y mina-archive=2.0.0umt-hardfork-automation-umt-eb0a6d0
Mina Archive Schema:
create_schema.sql
zkapp_tables.sql
Config File: var/lib/coda/config_eb0a6d00.json

Ledger Verification Tool

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: gcr.io/o1labs-192920/mina-daemon:2.0.0umt-hardfork-automation-umt-eb0a6d0-CODENAME-devnet-hardfork
Mina Archive: gcr.io/o1labs-192920/mina-archive:2.0.0umt-hardfork-automation-umt-eb0a6d0-CODENAME
Mina Archive Schema:
create_schema.sql
zkapp_tables.sql
Mina Rosetta: gcr.io/o1labs-192920/mina-rosetta:2.0.0umt-hardfork-automation-umt-eb0a6d0-CODENAME
Mina Archive Migration Tooling gcr.io/o1labs-192920/mina-archive-berkeley-archive-migration:1.0.0umt-tooling
Mina Archive Migration Documentation https://docs2-git-archivemigration-minadocs.vercel.app/berkeley-upgrade/migrating-archive-database-to-berkeley

Step by Step Guides:

Upgrade Package verification:

Documentation:
https://github.com/MinaProtocol/mina/blob/berkeley/docs/upgrading-to-berkeley.md

Further usage details are documented inside the script itself as its help message: https://github.com/MinaProtocol/mina/blob/berkeley/scripts/mina-verify-packaged-fork-config.

State exported off of pre-upgrade network can be found here:
https://storage.googleapis.com/tmp-hardfork-testing/fork-umt-02-29-2024.json.gz

Mina Archive Node

1. Start the archive node using the migrated DB. You can migrate your database as instructed in the doc https://docs2-git-archivemigration-minadocs.vercel.app/berkeley-upgrade/migrating-archive-database-to-berkeley using the migration tool gcr.io/o1labs-192920/mina-archive-berkeley-archive-migration:1.0.0umt-tooling

2. Alternatively you can import the migrated db dump from https://storage.googleapis.com/mina-archive-dumps/o1labs-umt-post

Mina Daemon

This version connects and functions only on the UMT testnet.

1. Create a libp2p key pair for a node the first time and persist it.
   mina libp2p generate-keypair -privkey-path <path-to-the-key-file>
2. Set the environment variable MINA_LIBP2P_PASS with the password set for the libp2p key pair in the previous step.
3. Run mina daemon with:
   -libp2p-keypair <path-to-the-key-file> and --peer-list-url https://storage.googleapis.com/o1labs-gitops-infrastructure/o1labs-umt-post-fork-run-1/seeds-o1labs-umt-post-fork-run-1.txt

For more information please refer to the Launching UMT Mina Nodes document provided to those participating in the program.

If you are running the correct version on the correct network, mina client status will show:

Chain id:     ded2784524f624295e63cede1a4ab9348fbcde7160876c4d55f1481b9d3ef542
Git SHA-1:    eb0a6d00675756972f4f22ecaa10532bae601c59