While hard at work on the 1.2.0+ releases, the O(1) Labs team discovered an issue with the transaction inclusion logic. In an abundance of caution, we have provided a stable fix on top of the existing 1.1.5 codebase, tagged as 1.1.7 to avoid any confusion with the previous 1.1.6alpha naming convention. The changes have been thoroughly tested, and are limited to the minimal change to prevent future issues. To run this same change on the 1.2.0 beta release version, see 1.2.0beta6.
Complete Changelog since 1.1.5:
Upgrading & Connecting
Daemon Release Artifacts:
Docker Image:
minaprotocol/mina-daemon-baked:1.1.7-d5ff5aa-mainnet
Debian Package:
sudo apt-get install -y mina-mainnet=1.1.7-d5ff5aa
Archive Node Release Artifacts:
Docker Image:
minaprotocol/mina-archive:1.1.7-d5ff5aa
Debian Package:
sudo apt-get install -y mina-archive=1.1.7-d5ff5aa
Schema for initializing postgres:
create_schema.sql
Step by Step Guide:
Check out our documentation for complete instructions on using this version to connect to Mainnet. Make sure to run with --peer-list-url https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt.
If you are running the correct version on the correct network, mina client status will show:
Chain id: 5f704cc0c82e0ed70e873f0893d7e06f148524e3f0bdae2afb02e7819a0c24d1
Git SHA-1: d5ff5aa207e64bcd6862e1ae9a3b83910c1c7b1d