Mainnet Beta Release 1.3.0beta5
Pre-releaseThe O(1) Labs team is proud to announce that results from the latest beta tests have been great, but we have even more improvements available in beta5! This 1.3.0beta5 includes all of the extensive improvements from beta4 as well as improved performance when serving bootstrap requests (great for seed nodes!) and additional optimizations to rosetta and mina-archive for fast retrieval of historical account nonces. Below is a summary of some of the more critical changes, and links to further information about the extensive changes since 1.2.2.
If you run into any issues, please include Release: 1.3.0beta5
in the name of any issues you create. Please report any issues you encounter here or join the Discussion!
Bug Fixes:
- Fix account unlocking so that the password does not get rewritten when the key is unlocked #9720 fixed by#10190
- Remove verifier memory stats logging to save resources #10236
- Fix super catchup async loop to avoid busy waiting #10237
- Cache intermediate ledger hashes to improve bootstrap resource usage #10297
New Features:
- Simpler optimization for staged ledger diff application (and revert buggy PRs from alpha2) #10121
- This version supports both MINA_ environment variables and the old CODA_ prefix, but the 1.3.X will be the last releases to support CODA_. We recommend you take this opportunity to use MINA_ everywhere going forward (example: MINA_PRIVKEY_PASS, MINA_CLIENT_TRUSTLIST, etc.)
- New command
mina advanced runtime-config
and relatedruntimeConfig
graphQL query for returning the configuration the daemon is using #8648 - Upgrade to Ocaml 4.11.2 #8898
- Upgrade to Rust 1.52.1 #9076
- Remove deprecated feature for swapping block producer keys at runtime to simplify daemon startup and fix demo mode #10139
- Housekeeping #10148 #10149 #10161
- Testing Improvements #10133 #10159 #10201 #10209 #10230
- Support for a variety of Ubuntu and Debian platforms, with docker images for each of them #10213 #10194:
- Debian 9 Codename "stretch" (always supported)
- Debian 10 Codename "buster" (supported since 1.3.0alpha1)
- Debian 11 Codename "bullseye" NEW
- Ubuntu 18.04 Codename "bionic" (originally shared with stretch, now fully supported)
- Ubuntu 20.04 Codename "focal" NEW
- To use the appropriate package for your platform:
- First uninstall mina-mainnet:
sudo apt-get remove mina-mainnet
- Then determine your release codename from the list above or by running
lsb_release -cs
- Use this name instead of
stretch
in the debian instructions below
- First uninstall mina-mainnet:
- New
--node-status-url
,--node-error-url
, and--contact-info
parameters to enable pushing node status and crash logs to a backend url. The contact info parameter is optional but allows you to provide discord or email contact in case we need further information about a crash. #9980- The first version of each backend is up for testing at:
--node-status-url https://us-central1-o1labs-192920.cloudfunctions.net/node-status-collection
--node-error-url https://us-central1-o1labs-192920.cloudfunctions.net/node-error-collection
- The first version of each backend is up for testing at:
- Support $PEER_LIST_URL, $LOG_LEVEL, $FILE_LOG_LEVEL, and a new flag $VERBOSE in the dockerfile entrypoint #10242 #10245
Archive Node:
- New archive node schema for optimized balance queries #9859
Rosetta Support:
- New docker image mina-rosetta-ubuntu which includes the mina daemon, mina-archive, and mina-rosetta along with entrypoint scripts to fill the archive database with blocks back to genesis and start all 3 daemons in tandem.
- Replace pending status with null or empty #10219 #10257
- Index nonces with the replayer for fast archive retrieval #10258
- Rosetta work has been ongoing for some time, and it has taken 26 pull requests to get all of the features supported and the kinks ironed out, but we are happy with the result. See the README for more about working with mina-rosetta.
- Those 26 PRs: #9797 #9802 #9811 #9839 #9841 #9848 #9859 #9871 #9880 #9881 #9884 #9890 #9896 #9899 #9904 #9908 #9911 #9885 #9954 #9967 #9969 #9965 #10019 #10044 #9932 #10104
Complete Changelog since 1.2.2:
The change set is far too large for github to display, but the github comparison still shows the immense scale of 1.3.0 and why we are so excited to get it out into your hands to test.
1.2.2...1.3.0beta5
For more information about the changes included in more recent updates like 1.3.0beta4, see the previous release notes
Upgrading & Connecting to Mainnet
Debian Packages:
Debian Repository:
First, set up and update the beta
Debian Repository for your platform. Replace the word CODENAME
with the appropriate codename for your machine, one of bionic
, focal
, stretch
, buster
, or bullseye
and run:
echo "deb [trusted=yes] http://packages.o1test.net CODENAME beta" | sudo tee /etc/apt/sources.list.d/mina-beta.list
sudo apt-get update
Then, install the package(s) that you need:
Mina Daemon: sudo apt-get install -y mina-mainnet=1.3.0beta5-18ab1dc
Mina Archive: `sudo apt-get install -y mina-archive=1.3.0beta5-18ab1dc
New Mina Archive Schema: create_schema.sql
Docker Images:
Every docker image is built for each of the supported platforms, replace CODENAME
in the images below with your choice of bionic
, focal
, stretch
, buster
, or bullseye
to select the base docker image.
Mina Daemon: minaprotocol/mina-daemon:1.3.0beta5-18ab1dc-CODENAME-mainnet
Mina Archive: minaprotocol/mina-archive:1.3.0beta5-18ab1dc-CODENAME
New Mina Archive Schema: create_schema.sql
Mina Rosetta: minaprotocol/mina-rosetta:1.3.0beta5-18ab1dc-CODENAME
Sandbox Node: For testing in an isolated, single-node network without snarks
As of 1.2.0, the demo functionality is built into the standard daemon container, via the environment variable RUN_DEMO=true
.
Just docker run -it --name mina-demo -e RUN_DEMO=true minaprotocol/mina-daemon:1.3.0beta5-18ab1dc-CODENAME-devnet
and go!
Step by Step Guide:
Check out our documentation for complete instructions on using this version to connect to Mainnet. Docker only 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 MAINNET, mina client status
will show:
Chain id: 5f704cc0c82e0ed70e873f0893d7e06f148524e3f0bdae2afb02e7819a0c24d1
Git SHA-1: 18ab1dc105bb6b0d5efa2ad97632f0fb676646bd