Post-HF Release Notes <Actual title will go here>

gistfile1.txt

<Welcome, hype & explainer text!>

Mina's ecosystem partner, O(1) Labs, is continuously working on improvements to the core protocol and today we are very excited and proud to finally announce the final stage in the Berkeley Upgrade release! This release signifies a major milestone in the Mina journey as it ushers in the new Berkeley era allowing for vastly extended functionality, performance and stability on the Mina mainnet network.

## What changed

Where to begin?

#### Complete CHANGELOG since <1.4.1rev> in:

GitHub Compare: <1.4.1rev>...<hfrev>

#### 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 `stable` 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) stable" | sudo tee /etc/apt/sources.list.d/mina.list
sudo apt-get update
```

Then, install the package or packages that you need:

- Mina Daemon `sudo apt-get install -y mina-mainnet=<tag>-<hfrev>`
- Mina Archive `sudo apt-get install -y mina-archive=<tag>-<hfrev>`
- zkApps Test Transaction CLI `sudo apt-get install -y mina-zkapp-test-transaction=<tag>-<hfrev>`
- [zkApps Transaction CLI README](https://github.com/MinaProtocol/mina/blob/ecbb3d490dce0f199894ebdf787a03b8fec64bd4/src/app/zkapp_test_transaction/README.md)

**Archive Node DB Migration

Upgrading require archive node operators to perform some migration efforts to make their current databases compatible with the new Berkeley era.

**Provide exact user steps here!**

**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:<tag>-<hfrev>-CODENAME-mainnet](http://gcr.io/o1labs-192920/mina-daemon:<tag>-<hfrev>-CODENAME-mainnet)
- Mina Archive: [gcr.io/o1labs-192920/mina-archive:<tag>-<hfrev>-CODENAME](http://gcr.io/o1labs-192920/mina-archive:<tag>-<hfrev>-CODENAME)
- Mina Rosetta: [gcr.io/o1labs-192920/mina-rosetta:<tag>-<hfrev>-CODENAME](gcr.io/o1labs-192920/mina-rosetta:<tag>-<hfrev>-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/mainnet_seeds.txt`

If you are running the correct version on the correct network the expected output of the `mina client status` command is:

```
Git SHA-1: <hfrev>
Chain ID: <chainID>
```

## Rosetta Steps

**Full Changelog**: https://github.com/MinaProtocol/mina/compare/1.4.1...<tag>