Releases: MinaProtocol/mina
Berkeley Testnet Release 2.0.0rampup5 (ITN)
Mina's ecosystem partner, O(1) Labs, is continuously working on improvements to the core protocol and today we are excited to announce an updated unstable release 55b7818 that is ready to test on the Testworld 2.0 testnet! Please report any issues in the comments on this post or tag any issues you create with berkeley-rampup and include berkeley 55b7818 in the issue title.
What changed
Bug Fixes
- Fix non-determinism in scan state representation #13435
- Fix hashtbl usages #13511
- Fix snark pool long async cycles #13556
- Fix block producer long async cycle #13654
- Fix bootstrap long async cycle #13885
- Sort list of equivalence class elements #13592
- Upgrade libp2p and Go version #14085
- Add chain id to node status report #13982
- Rename global slot in fork config #14014
- Support larger ledgers in IPC communication #11973
Features
- New protocol versioning #14227
- Disable rate limitting for snark works #14174
- CLI command to dump libp2p keys #14169
Improvements
- Remove duplicate account inclusion checks #13422
- Reduce delay in broadcasting blocks #13551
- Hardcode number of oversized logs #14286
- Remove constructors for account precondition #14117
- Remove some oversized logs #14054
- Node performance improvement by batching transactions when writing to persistent frontier #13557
- Stop printing accounts from runtime config #1407
Complete CHANGELOG since 14047c5 in:
GitHub Compare: 14047c5...55b7818
SnarkyJS CHANGELOG
https://github.com/o1-labs/snarkyjs/blob/main/CHANGELOG.md
Installation
Supported environments include macOS, Linux (Debian 10, 11, 12 and Ubuntu 20.04 LTS), and any host machine with Docker.
When installing Mina Archive node, use the following schema files from the release commit:
- https://github.com/MinaProtocol/mina/blob/55b78189c46e1811b8bdb78864cfa95409aeb96a/src/app/archive/create_schema.sql
- https://github.com/MinaProtocol/mina/blob/55b78189c46e1811b8bdb78864cfa95409aeb96a/src/app/archive/zkapp_tables.sql
Note: zkApps Test Transaction CLI tool is not supported to create token accounts in this release.
Upgrading and Connecting to Testworld 2.0
Debian Packages
First, set up and update the rampup Debian Repository for your platform.
Replace CODENAME with the appropriate codename for your machine (focal
, buster
, or bullseye
), and run:
sudo rm /etc/apt/sources.list.d/mina*.list
echo "deb [trusted=yes] http://packages.o1test.net/ CODENAME rampup" | sudo tee /etc/apt/sources.list.d/mina-rampup.list
sudo apt-get update
Then, install the package or packages that you need:
- Mina Daemon
sudo apt-get install -y mina-berkeley=2.0.0rampup5-55b7818
- Mina Archive
sudo apt-get install -y mina-archive=2.0.0rampup5-55b7818
- zkApps Test Transaction CLI
sudo apt-get install -y mina-zkapp-test-transaction=2.0.0rampup5-55b7818
- zkApps Transaction CLI README
Docker Images
Every docker image is built for each of the supported platforms.
To select the base docker image, replace CODENAME with the codename appropriate for your machine (focal
, buster
, or bullseye
):
- Mina Daemon: gcr.io/o1labs-192920/mina-daemon:2.0.0rampup5-55b7818-CODENAME-berkeley
- Mina Archive: gcr.io/o1labs-192920/mina-archive:2.0.0rampup5-55b7818-CODENAME
Step-by-Step Guide
This version connects and functions only on the newly launched Testworld 2.0.
- 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>
- Set the environment variable
MINA_LIBP2P_PASS
with the password set for the libp2p key pair in the previous step. - Run mina daemon with:
-libp2p-keypair <path-to-the-key-file>
andhttps://storage.googleapis.com/seed-lists/testworld-2-0_seeds.txt
If you are running the correct version on the correct network, Testworld 2.0, the expected output of the mina client status
command is:
Git SHA-1: 55b7818
Chain ID: 332c8cc05ba8de9efc23a011f57015d8c9ec96fac81d5d3f7a06969faf4bce92
Berkeley Testnet Release 2.0.0rampup4
Mina's ecosystem partner, O(1) Labs, is continuously working on improvements to the core protocol and today we are excited to announce an updated unstable release 14047c5 that is ready to test on the Berkeley testnet! Please report any issues in the comments on this post or tag any issues you create with berkeley-rampup and include berkeley 14047c5 in the issue title.
What changed
Bug Fixes
- Fix verification key mismatch in zkapp transactions with non-proof authorization #13394
- Fix the ordering of accounts in zkApp transaction application result impacting scan state hash #13435
- Don’t ban nodes for block created in early catchup #13538
- Fix transaction and snark work rebroadcast #13535
Features
- Remove snark pool persistence #13409
- Crash daemon if stuck in bootstrap for more than 2hrs #13747
- Create network-specific domains for account update hashes #13880
- Add genesis timestamp to genesis constants in GraphQL #14013
Improvements
- Replayer app improvements: #13406 #13460
#13600 #13620 - Improve node boot up time #13470
- Reduce delay in broadcasting produced block #13551
- Improve mempool performance #13560
- Improve block producer performance #13671
- Snark coordinator performance improvement #13950
- Snarky JS - reduce the startup time o1-labs/o1js#1073
Complete CHANGELOG since bfd1009 in:
GitHub Compare: bfd1009...14047c5
SnarkyJS CHANGELOG
https://github.com/o1-labs/snarkyjs/blob/main/CHANGELOG.md
Installation
When installing Mina Archive node, use the following schema files from the release commit:
- https://github.com/MinaProtocol/mina/blob/14047c55517cf3587fc9a6ac55c8f7e80a419571/src/app/archive/create_schema.sql
- https://github.com/MinaProtocol/mina/blob/14047c55517cf3587fc9a6ac55c8f7e80a419571/src/app/archive/zkapp_tables.sql
Note: zkApps Test Transaction CLI tool is not supported to create token accounts in this release.
Upgrading and Connecting to Berkeley Testnet
Debian Packages
First, set up and update the rampup Debian Repository for your platform.
Replace CODENAME with the appropriate codename for your machine (focal
, buster
, or bullseye
), and run:
sudo rm /etc/apt/sources.list.d/mina*.list
echo "deb [trusted=yes] http://packages.o1test.net/ CODENAME rampup" | sudo tee /etc/apt/sources.list.d/mina-rampup.list
sudo apt-get update
Then, install the package or packages that you need:
- Mina Daemon
sudo apt-get install -y mina-berkeley=2.0.0rampup4-14047c5
- Mina Archive
sudo apt-get install -y mina-archive=2.0.0rampup4-14047c5
- zkApps Test Transaction CLI
sudo apt-get install -y mina-zkapp-test-transaction=2.0.0rampup4-14047c5
- zkApps Transaction CLI README
Docker Images
Every docker image is built for each of the supported platforms.
To select the base docker image, replace CODENAME with the codename appropriate for your machine (focal
, buster
, or bullseye
):
- Mina Daemon: gcr.io/o1labs-192920/mina-daemon:2.0.0rampup4-14047c5-CODENAME-berkeley
- Mina Archive: gcr.io/o1labs-192920/mina-archive:2.0.0rampup4-14047c5-CODENAME
Step-by-Step Guide
This version connects and functions only on the newly launched Berkeley Testnet.
- 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>
- Set the environment variable
MINA_LIBP2P_PASS
with the password set for the libp2p key pair in the previous step. - Run mina daemon with:
-libp2p-keypair <path-to-the-key-file>
and--peer-list-url https://storage.googleapis.com/seed-lists/berkeley_seeds.txt
If you are running the correct version on the correct network, BERKELEY TESTNET, the expected output of the mina client status
command is:
Chain id: 3c41383994b87449625df91769dff7b507825c064287d30fada9286f3f1cb15e
Git SHA-1: 14047c5
Mainnet Stable Release 1.4.0
The O(1) Labs team is proud to announce that 1.4.0 is ready for production use on Mainnet! This release includes a set of bugfixes, Feature improvements, CI improvements and code cleanup that we have applied to 1.4.0 to ensure minimal changes between releases.
Supported environments include macOS, Linux (Debian 10, 11 and Ubuntu 20.04 LTS), and any host machine with Docker.
If you run into any issues, please include Release: 1.4.0
in the name of any issues you create. Please report any issues you encounter here or join the discussion below!
New Features:
- Faster ledger export #13316
- Logging for low_fill_rate debugging #12902
- logproc package #12827
- Demote network pool batch size logs to debug #12846
Complete Changelog since 1.3.1.2:
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 -y mina-mainnet=1.4.0-c980ba8
Mina Archive: sudo apt-get install -y mina-archive=1.4.0-c980ba8
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 focal
, buster
, or bullseye
to select the base docker image.
Mina Daemon: minaprotocol/mina-daemon:1.4.0-c980ba8-CODENAME-mainnet
Mina Archive: minaprotocol/mina-archive:1.4.0-c980ba8-CODENAME
Mina Archive Schema: create_schema.sql
Mina Rosetta: minaprotocol/mina-rosetta:1.4.0-c980ba8-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.4.0-c980ba8-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
or add PEER_LIST_URL=https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt
to your .mina-env
.
If you are running the correct version on the correct network MAINNET, mina client status
will show:
Chain id: 5f704cc0c82e0ed70e873f0893d7e06f148524e3f0bdae2afb02e7819a0c24d1
Git SHA-1: c980ba87c3417f40a7081225dfe7478c5ee70fd7
Berkeley Testnet Release 2.0.0rampup3
Mina's ecosystem partner, O(1) Labs, is continuously working on improvements to the core protocol and today we are excited to announce an updated unstable release bfd1009 that is ready to test on the Berkeley testnet! Please report any issues in the comments on this post or tag any issues you create with berkeley-rampup and include berkeley bfd1009 in the issue title.
Improvements, Features, and Bug fixes
- Internal tracing implementation (internal tracing PR 1 of 3) #12703
- Internal tracing for prover and verifier (internal tracing PR 2 of 3) #12874
- Bump action limit #12981
- Set delegate in new accounts #13043
- Fix transaction pool permission checks #13048
- Remove last vrf output #13120
- Split Global_slot.t into since-genesis and since-hard-fork types #13143
- Well-formedness check #13266
- Faster ledger export (berkeley) #13336
- Remove token_id from local state #13370
- Unbox slot types #13382
- Updated genesis timestamp #13522
When installing Mina Archive node, use the following schema files from the release commit:
- https://github.com/MinaProtocol/mina/blob/bfd1009abdbee78979ff0343cc73a3480e862f58/src/app/archive/create_schema.sql
- https://github.com/MinaProtocol/mina/blob/bfd1009abdbee78979ff0343cc73a3480e862f58/src/app/archive/zkapp_tables.sql
Note: zkApps Test Transaction CLI tool is not supported to create token accounts in this release.
Complete CHANGELOG since b1facec in:
GitHub Compare: b1facec...bfd1009
SnarkyJS CHANGELOG
https://github.com/o1-labs/snarkyjs/blob/main/CHANGELOG.md
Upgrading and Connecting to Berkeley Testnet
Debian Packages
First, set up and update the rampup Debian Repository for your platform.
Replace CODENAME with the appropriate codename for your machine (focal
, buster
, or bullseye
), and run:
sudo rm /etc/apt/sources.list.d/mina*.list
echo "deb [trusted=yes] http://packages.o1test.net/ CODENAME rampup" | sudo tee /etc/apt/sources.list.d/mina-rampup.list
sudo apt-get update
Then, install the package or packages that you need:
- Mina Daemon
sudo apt-get install -y mina-berkeley=2.0.0rampup3-bfd1009
- Mina Archive
sudo apt-get install -y mina-archive=2.0.0rampup3-bfd1009
- zkApps Test Transaction CLI
sudo apt-get install -y mina-zkapp-test-transaction=2.0.0rampup3-bfd1009
- zkApps Transaction CLI README
Docker Images
Every docker image is built for each of the supported platforms.
To select the base docker image, replace CODENAME with the codename appropriate for your machine (focal
, buster
, or bullseye
):
- Mina Daemon: gcr.io/o1labs-192920/mina-daemon:2.0.0rampup3-bfd1009-CODENAME-berkeley
- Mina Archive: gcr.io/o1labs-192920/mina-archive:2.0.0rampup3-bfd1009-CODENAME
Step-by-Step Guide
This version connects and functions only on the newly launched Berkeley Testnet.
- 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>
- Set the environment variable
MINA_LIBP2P_PASS
with the password set for the libp2p key pair in the previous step. - Run mina daemon with:
-libp2p-keypair <path-to-the-key-file>
and--peer-list-url https://storage.googleapis.com/seed-lists/berkeley_seeds.txt
If you are running the correct version on the correct network, BERKELEY TESTNET, the expected output of the mina client status
command is:
Chain id: 667b328bfc09ced12191d099f234575b006b6b193f5441a6fa744feacd9744db
Git SHA-1: bfd1009
Mainnet Beta Release 1.4.0beta3
The O(1) Labs team is proud to announce that 1.4.0beta3 is ready to test on Mainnet! This release includes a set of minor bugfixes, RFCs and new documentation, major testing and CI improvements, and code cleanup. The change has significant performance improvement on ledger export on user experience but include months of work to improve testing, processes, and code quality.
If you run into any issues, please include Release: 1.4.0beta3
in the name of any issues you create. Please report any issues you encounter here or join the Discussion!
Improvements/Features:
- Faster ledger export #13316
Complete Changelog since 1.3.1.2:
Upgrading & Connecting to Mainnet
Debian Packages:
Debian Repository:
First, set up and update the beta
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) 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.4.0beta3-1a8adfa
Mina Archive: sudo apt-get install -y mina-archive=1.4.0beta3-1a8adfa
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
, buster
, or bullseye
to select the base docker image.
Mina Daemon: minaprotocol/mina-daemon:1.4.0beta3-1a8adfa-CODENAME-mainnet
Mina Archive: minaprotocol/mina-archive:1.4.0beta3-1a8adfa-CODENAME
New Mina Archive Schema: create_schema.sql
Mina Rosetta: minaprotocol/mina-rosetta:1.4.0beta3-1a8adfa-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.4.0beta3-1a8adfa-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
or add PEER_LIST_URL=https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt
to your .mina-env
.
If you are running the correct version on the correct network MAINNET, mina client status
will show:
Chain id: 5f704cc0c82e0ed70e873f0893d7e06f148524e3f0bdae2afb02e7819a0c24d1
Git SHA-1: 1a8adfa0d00f88c955e503f5f6eaef775f30e2be
Retiring
We are retiring support on stretch
.
Berkeley Testnet Release 2.0.0rampup2
Mina's ecosystem partner, O(1) Labs, is continuously working on improvements to the core protocol and today we are excited to announce an updated unstable release 42d2005 that is ready to test on the Berkeley testnet! Please report any issues in the comments on this post or tag any issues you create with berkeley-rampup and include berkeley 42d2005 in the issue title.
Improvements / features:
- Lucy genesis ledger and keys refactor #12391
- Print debian releases #12800
- Demote network pool batch size logs to debug #12846
- logproc package #12827
- Logging for low_fill_rate debugging #12902
- Snarkyjs: run circuits without failing assertions #12911
- fix conflicts from compatible #13006
Bug fixes:
- Fix Archive : All columns for block subchain query #12997
When installing Mina Archive please use the following schema files from the release commit:
https://github.com/MinaProtocol/mina/blob/42d2005d04b59d14aacf4eef5ccee353e9a531b7/src/app/archive/create_schema.sql
https://github.com/MinaProtocol/mina/blob/42d2005d04b59d14aacf4eef5ccee353e9a531b7/src/app/archive/zkapp_tables.sql
Note: zkApps Test Transaction CLI tool cannot be used to create token accounts in this release.
Complete Changelog since b1facec in:
Github Compare: b1facec...42d2005
SnarkyJS change log:
https://github.com/o1-labs/snarkyjs/blob/main/CHANGELOG.md
Upgrading & Connecting to Berkeley Testnet
Debian Packages:
First, set up and update the rampup 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:
sudo rm /etc/apt/sources.list.d/mina*.list
echo "deb [trusted=yes] http://packages.o1test.net/ CODENAME rampup" | sudo tee /etc/apt/sources.list.d/mina-rampup.list
sudo apt-get update
Then, install the package(s) that you need:
Mina Daemon: sudo apt-get install -y mina-berkeley=2.0.0rampup2-42d2005
Mina Archive: sudo apt-get install -y mina-archive=2.0.0rampup2-42d2005
zkApps Test Transaction CLI: sudo apt-get install -y mina-zkapp-test-transaction=2.0.0rampup2-42d2005
zkApps Transaction CLI Documentation
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: gcr.io/o1labs-192920/mina-daemon:2.0.0rampup2-42d2005-CODENAME-berkeley
Mina Archive: gcr.io/o1labs-192920/mina-archive:2.0.0rampup2-42d2005-CODENAME
Step by Step Guide:
This version will only connect and function properly on the newly launched Berkeley Testnet.
-
Create a libp2p keypair for a node the first time and persist it
mina libp2p generate-keypair -privkey-path <path-to-the-key-file>
-
Run mina daemon
Set environment variableMINA_LIBP2P_PASS
with the password set for the libp2p keypair in previous step.
Make sure to run the daemon with-libp2p-keypair <path-to-the-key-file>
and--peer-list-url https://storage.googleapis.com/seed-lists/berkeley_seeds.txt
.
If you are running the correct version on the correct network BERKELEY TESTNET
, mina client status will show:
Chain id: 8c4908f1f873bd4e8a52aeb4981285a148914a51e61de6ac39180e61d0144771
Git SHA-1: 42d2005
Berkeley Testnet Release 2.0.0rampup1-b1facec
Mina's ecosystem partner, O(1) Labs, is continuously working on improvements to the core protocol and today we are excited to announce an updated unstable release b1facec that is ready to test on the Berkeley testnet! Please report any issues in the comments on this post or tag any issues you create with berkeley-rampup and include berkeley b1facec in the issue title.
Improvements/features:
- Rename sequence_state to action_state #12715
- Add last VRF output and subwindow densities to blocks in archive #12750
- Protocol version in archive db #12847
- Fix for berkeley chain halt. The issue was an underflow not handled correctly when computing balance for accounts with vesting schedule #12805
There are archive schema changes in this release. Please use the following schema files from the release commit:
https://github.com/MinaProtocol/mina/blob/b1facecde934ce3969771c34962b878d75321ca7/src/app/archive/create_schema.sql
https://github.com/MinaProtocol/mina/blob/b1facecde934ce3969771c34962b878d75321ca7/src/app/archive/zkapp_tables.sql
Note: zkApps Test Transaction CLI tool cannot be used to create token accounts in this release.
Complete Changelog since 68fa3fa in:
Github Compare: 68fa3fa...b1facec
SnarkyJS change log:
https://github.com/o1-labs/snarkyjs/blob/main/CHANGELOG.md
Upgrading & Connecting to Berkeley Testnet
Debian Packages:
First, set up and update the unstable 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 unstable" | sudo tee /etc/apt/sources.list.d/mina-unstable.list
sudo apt-get update
Then, install the package(s) that you need:
Mina Daemon: sudo apt-get install -y mina-berkeley=2.0.0rampup1-rampup-b1facec
Mina Archive: sudo apt-get install -y mina-archive=2.0.0rampup1-rampup-b1facec
zkApps Test Transaction CLI: sudo apt-get install -y mina-zkapp-test-transaction=2.0.0rampup1-rampup-b1facec
zkApps Transaction CLI Documentation
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: gcr.io/o1labs-192920/mina-daemon:2.0.0rampup1-rampup-b1facec-CODENAME-berkeley
Mina Archive: gcr.io/o1labs-192920/mina-archive:2.0.0rampup1-rampup-b1facec-CODENAME
Step by Step Guide:
This version will only connect and function properly on the newly launched Berkeley Testnet.
-
Create a libp2p keypair for a node the first time and persist it
mina libp2p generate-keypair -privkey-path <path-to-the-key-file>
-
Run mina daemon
Set environment variableMINA_LIBP2P_PASS
with the password set for the libp2p keypair in previous step.
Make sure to run the daemon with-libp2p-keypair <path-to-the-key-file>
and--peer-list-url https://storage.googleapis.com/seed-lists/berkeley_seeds.txt
.
If you are running the correct version on the correct network BERKELEY TESTNET
, mina client status will show:
Chain id: 8c4908f1f873bd4e8a52aeb4981285a148914a51e61de6ac39180e61d0144771
Git SHA-1: b1facec
Mainnet Beta Release 1.4.0beta2
The O(1) Labs team is proud to announce that 1.4.0beta2 is ready to test on Mainnet! This release includes a set of minor bugfixes, RFCs and new documentation, major testing and CI improvements, and code cleanup. The changes should have a minor effect on user experience but include months of work to improve testing, processes, and code quality.
If you run into any issues, please include Release: 1.4.0beta2
in the name of any issues you create. Please report any issues you encounter here or join the Discussion!
New Features:
- Logging for low_fill_rate debugging #12902
- logproc package #12827
- Demote network pool batch size logs to debug #12846
Complete Changelog since 1.3.1.2:
Upgrading & Connecting to Mainnet
Debian Packages:
Debian Repository:
First, set up and update the beta
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) 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.4.0beta2-e976627
Mina Archive: sudo apt-get install -y mina-archive=1.4.0beta2-e976627
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.4.0beta2-e976627-CODENAME-mainnet
Mina Archive: minaprotocol/mina-archive:1.4.0beta2-e976627-CODENAME
New Mina Archive Schema: create_schema.sql
Mina Rosetta: minaprotocol/mina-rosetta:1.4.0beta2-e976627-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.4.0beta2-e976627-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
or add PEER_LIST_URL=https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt
to your .mina-env
.
If you are running the correct version on the correct network MAINNET, mina client status
will show:
Chain id: 5f704cc0c82e0ed70e873f0893d7e06f148524e3f0bdae2afb02e7819a0c24d1
Git SHA-1: e976627007d99415932392a84983de4e4a8db38f
Mainnet Beta Release 1.4.0beta1
The O(1) Labs team is proud to announce that 1.4.0beta1 is ready to test on Mainnet! This release includes a set of minor bugfixes, RFCs and new documentation, major testing and CI improvements, and code cleanup. The changes should have a minor effect on user experience but include months of work to improve testing, processes, and code quality.
If you run into any issues, please include Release: 1.4.0beta1
in the name of any issues you create. Please report any issues you encounter here or join the Discussion!
Complete Changelog since 1.3.1.2:
Upgrading & Connecting to Mainnet
Debian Packages:
Debian Repository:
First, set up and update the beta
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) 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.4.0beta1-baac5fd
Mina Archive: sudo apt-get install -y mina-archive=1.4.0beta1-baac5fd
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.4.0beta1-baac5fd-CODENAME-mainnet
Mina Archive: minaprotocol/mina-archive:1.4.0beta1-baac5fd-CODENAME
New Mina Archive Schema: create_schema.sql
Mina Rosetta: minaprotocol/mina-rosetta:1.4.0beta1-baac5fd-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.4.0beta1-baac5fd-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
or add PEER_LIST_URL=https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt
to your .mina-env
.
If you are running the correct version on the correct network MAINNET, mina client status
will show:
Chain id: 5f704cc0c82e0ed70e873f0893d7e06f148524e3f0bdae2afb02e7819a0c24d1
Git SHA-1: baac5fdddc441d0862d72fa5a74ac96297477d12
Devnet Pre-Release 1.4.0alpha1
The O(1) Labs team is proud to announce that 1.4.0alpha1 is ready to test on Devnet! This release includes a set of minor bugfixes, RFCs and new documentation, major testing and CI improvements, and code cleanup. The changes should have a minor effect on user experience but include months of work to improve testing, processes, and code quality.
If you run into any issues, please include Release: 1.4.0alpha1
in the name of any issues you create. Please report any issues you encounter here or join the Discussion!
Complete Changelog since 1.3.1.2:
Upgrading & Connecting to Mainnet
Debian Packages:
Debian Repository:
First, set up and update the alpha
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) alpha" | sudo tee /etc/apt/sources.list.d/mina-alpha.list
sudo apt-get update
Then, install the package(s) that you need:
Mina Daemon: sudo apt-get install -y mina-devnet=1.4.0alpha1-da12bcf
Mina Archive: sudo apt-get install -y mina-archive=1.4.0alpha1-da12bcf
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.4.0alpha1-da12bcf-CODENAME-devnet
Mina Archive: minaprotocol/mina-archive:1.4.0alpha1-da12bcf-CODENAME
New Mina Archive Schema: create_schema.sql
Mina Rosetta: minaprotocol/mina-rosetta:1.4.0alpha1-da12bcf-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.4.0alpha1-da12bcf-CODENAME-devnet
and go!
Step by Step Guide:
Step by Step Guide:
Check out our documentation for complete instructions on using this version to connect to Devnet.
Docker only Make sure to run with --peer-list-url https://storage.googleapis.com/seed-lists/devnet_seeds.txt
. or add PEER_LIST_URL=https://storage.googleapis.com/seed-lists/devnet_seeds.txt
to your .mina-env
.
If you are running the correct version on the correct network DEVNET, mina client status
will show:
Chain id: b6ee40d336f4cc3f33c1cc04dee7618eb8e556664c2b2d82ad4676b512a82418
Git SHA-1: da12bcf65fc6b37d81b237e57ab9284270d339ef