Mainnet Beta Release 1.3.0beta5 #10328
lk86
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The 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 below!Bug Fixes:
New Features:
mina advanced runtime-config
and relatedruntimeConfig
graphQL query for returning the configuration the daemon is using Advanced command for dumping the runtime-config #8648*_nonconsensus
libraries to shadow their consensus counterparts #10149 Make Truth.t cases exhaustive #10161sudo apt-get remove mina-mainnet
lsb_release -cs
stretch
in the debian instructions below--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. Feature/node error collection #9980--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
Archive Node:
Rosetta Support:
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 Devnet
Debian Packages:
Debian Repository:
First, set up and update the
beta
Debian Repository for your platform. Replace the wordCODENAME
with the appropriate codename for your machine, one ofbionic
,focal
,stretch
,buster
, orbullseye
and run: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 ofbionic
,focal
,stretch
,buster
, orbullseye
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:This discussion was created from the release Mainnet Beta Release 1.3.0beta5.
Beta Was this translation helpful? Give feedback.
All reactions