MinaProtocol/mina 4.0.1

Mina Mainnet & Devnet Stable 4.0.1 Release

on GitHub

🎉 The o1Labs team is proud to announce that the 4.0.1 Stable Release is now ready and available for Mainnet & Devnet! 🎉

4.0.1 is a maintenance release for the Mesa networks. It improves peer discovery, adds health-check tools for the daemon, the archive node and Rosetta and fixes archive block insertion when blocks are inserted concurrently.

If you run into any issues, please include Release: 4.0.1 in the name of any issues you create. Please report any issues you encounter here or join the discussion!

What's Included in 4.0.1?

Networking

• Peer discovery: nodes keep discovering peers over the DHT for as long as they run. Nodes behind NAT without a forwarded port benefit most and hold noticeably more peers. Read more
• Peer scoring: a gossiped block or transaction whose validation times out is dropped without lowering the score of the peer that sent it, so a node no longer disconnects from its fastest peers. Read more

Daemon

• Block producers: the daemon warns at startup when --minimum-block-reward is above the coinbase amount, because the node would then produce empty blocks. Read more
• mina-healthcheck: a CLI for sync, peer and readiness probes (Kubernetes, Docker HEALTHCHECK, scripts). Read more

Archive node

• Concurrent block insertion: blocks that are inserted at the same time and share data (a zkApp command, a public key, a token) no longer fail with a database uniqueness error.
• mina-archive-healthcheck: probes that read archive health directly from PostgreSQL (database, server port, block recency, missing and unparented blocks). Read more
• mina-missing-blocks-auditor counts missing blocks from the lowest block in the archive, so a hard-fork archive no longer reports the blocks below the fork point as missing.

Rosetta

• /block and /search/transactions include nonce and memo in the metadata of payments, delegations and zkApp commands. Read more
• rosetta-healthcheck and rosetta-client: readiness probes and a CLI for every Rosetta Data and Construction endpoint. Read more

Complete Changelog since 4.0.0:

4.0.0-mainnet-mesa...4.0.1

Supported environments include Linux (Debian 12, Ubuntu 22.04 LTS & Ubuntu 24.04 LTS), and any host machine with Docker.

🚨NOTE - Ubuntu 20.04 (focal) and Debian 11 (bullseye) have reached EOL and are no longer supported. This release ships no packages or images for them.🚨

Upgrading & Connecting to Mainnet

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
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=4.0.1-1e9d141
Mina Archive: sudo apt-get install --allow-downgrades -y mina-archive-mainnet=4.0.1-1e9d141
Mina Rosetta: sudo apt-get install --allow-downgrades -y mina-rosetta-mainnet=4.0.1-1e9d141
Mina Archive Schema: create_schema.sql
Config File: /var/lib/coda/config_1e9d1419.json

Docker Images:

Every docker image is built for each of the supported platforms, replace CODENAME in the images below with your choice of jammy, noble, or bookworm to select the base docker image.

Mina Daemon: minaprotocol/mina-daemon:4.0.1-1e9d141-CODENAME-mainnet
Mina Archive: minaprotocol/mina-archive:4.0.1-1e9d141-CODENAME-mainnet
Mina Rosetta: minaprotocol/mina-rosetta:4.0.1-1e9d141-CODENAME-mainnet

Step by Step Guide:

Docker only Make sure to run with:

--peer-list-url https://bootnodes.minaprotocol.com/networks/mainnet.txt or add PEER_LIST_URL=https://bootnodes.minaprotocol.com/networks/mainnet.txt to your .mina-env.

Run mina daemon with:

mina daemon --peer-list-url https://bootnodes.minaprotocol.com/networks/mainnet.txt

Check 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 status will show:

Chain id:     0718f61ab88f9d0fa643ff4dc3a3d5998dd6d51a6008b2b0339b0dbb26133886
Git SHA-1:    1e9d1419466c54dd2cee38dce85945b7346e98a4

Upgrading & Connecting to Devnet

Use the same Debian repository setup as above, then install:

Mina Daemon: sudo apt-get install --allow-downgrades -y mina-devnet=4.0.1-1e9d141
Mina Archive: sudo apt-get install --allow-downgrades -y mina-archive-devnet=4.0.1-1e9d141
Mina Rosetta: sudo apt-get install --allow-downgrades -y mina-rosetta-devnet=4.0.1-1e9d141
Config File: /var/lib/coda/config_1e9d1419.json

Docker Images:

Mina Daemon: minaprotocol/mina-daemon:4.0.1-1e9d141-CODENAME-devnet
Mina Archive: minaprotocol/mina-archive:4.0.1-1e9d141-CODENAME-devnet
Mina Rosetta: minaprotocol/mina-rosetta:4.0.1-1e9d141-CODENAME-devnet

Run mina daemon with:

mina daemon --peer-list-url https://bootnodes.minaprotocol.com/networks/devnet.txt

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

Chain id:     ebfce0d570bc22eb041e1a7b0a46bbc3ed5d0a1030ef2ab5e36eef908b93eba8
Git SHA-1:    1e9d1419466c54dd2cee38dce85945b7346e98a4