Berkeley RC1

[amc-ie]

Mina's ecosystem partner, O(1) Labs, is continuously working on improvements to the core protocol and today we are excited to announce a brand new Berkely release candidate 1551e2f that is ready to test on the new and updated Berkeley Testnet!

Please report any issues in the comments on this post or tag any issues you create with 2.0.0berkeley_rc1 and include 2.0.0berkeley_rc1 in the issue title.

What changed

This release is the culmination of numerous fixes and additions developed during our previous TestWorld initiative including new features, RFCs, tests, bug fixes and significant performance enhancements. All of the fixes and improvements from the earlier rampup releases are also included in this release.

• Stop txn/network after slot feature [berkeley] Stop txn/network after slot feature #14773
• Don’t timeout if offline or bootstrapping before genesis Don't timeout if offline or bootstrapping before genesis #14328
• Batch to_verifiable ledger operations, and fix caching logic Batch to_verifiable ledger operations, and fix caching logic #14356
• Fix protocol version UNIQUE constraint Fix protocol version UNIQUE constraint #14363
• Hard fork protocol version is 2.0 Hard fork protocol version is 2.0 #14416
• Let discovery step try connections in parallel Let discovery step try connections in parallel #14395
• Feature/verification key update txn version Feature/verification key update txn version #14407
• Rename previous_global_slot to genesis_slot in fork config Merge genesis_slot renaming into compatible #14271
• GraphQL change- use explict field to differentiate slot_since_genesis slot_since_hard_fork use explict field to differentiate slot_since_genesis slot_since_hard_fork #14569
• Configure chain quality grace period for berkeley release Configure chain quality grace period for berkeley release #14776
• Option to limit zkApp Commands Hardcap (Not enabled) Limit zkApp Commands Hardcap #14813
• Disable zkapp commands implementation (Not enabled) RFC: Totally Disable zkApp Commands in case of Emergency #14880
• Integrity verification for S3 retrievals Integrity verification for all S3 retrievals #14973

Complete CHANGELOG since 56fa1db in:

GitHub Compare: 56fa1db...1551e2f

O1JS CHANGELOG

https://github.com/o1-labs/o1js/blob/main/CHANGELOG.md

Installation

Supported environments include macOS, Linux (Debian 10, 11 and Ubuntu 20.04 LTS), and any host machine with Docker.

Upgrading and Connecting to Berkeley

Debian Packages

First, set up and update the berkeley Debian Repository for your platform.

sudo rm /etc/apt/sources.list.d/mina*.list
echo "deb [trusted=yes] http://packages.o1test.net/ $(lsb_release -cs) berkeley" | sudo tee /etc/apt/sources.list.d/mina-berkeley.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.0berkeley-rc1-1551e2f
• Mina Archive sudo apt-get install -y mina-archive=2.0.0berkeley-rc1-1551e2f
• zkApps Test Transaction CLI sudo apt-get install -y mina-zkapp-test-transaction=2.0.0berkeley-rc1-1551e2f
• 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.0berkeley-rc1-1551e2f-CODENAME-berkeley
• Mina Archive: gcr.io/o1labs-192920/mina-archive:2.0.0berkeley-rc1-1551e2f-CODENAME

Step-by-Step Guide

This version connects and functions only on the new version of the Berkeley Testnet.

1. 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>
2. Set the environment variable MINA_LIBP2P_PASS with the password set for the libp2p key pair in the previous step.
3. 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:

Git SHA-1: 1551e2faaa246c01636908aabe5f7981715a10f4
Chain ID: fd7d111973bf5a9e3e87384f560fdead2f272589ca00b6d9e357fca9839631da

Full Changelog: 2.0.0rampup8...2.0.0berkeley_rc1

---

This discussion was created from the release Berkeley RC1.