chore: update upgrade docs (#1037)

Author: Zblocker64

src/content/Docs/node-operators/network-upgrades/index.md

@@ -15,14 +15,14 @@ This section contains comprehensive upgrade guides for node operators and valida
 
 ## Current Network Upgrade
 
-### [Mainnet 15 - Akash v1.1.0](/docs/node-operators/network-upgrades/mainnet-15)
+### [Mainnet 16 - Akash v1.2.0](/docs/node-operators/network-upgrades/mainnet-16)
 
 **Status:** Upcoming  
-**Upgrade Height:** 24,332,547  
-**Estimated Time:** Monday, November 24th, 2025 at 14:10 UTC  
-**Binary Version:** v1.1.0
+**Upgrade Height:** 25,789,395  
+**Estimated Time:** Wednesday, March 4th, 2025 at 14:00 UTC  
+**Binary Version:** v1.2.0
 
-Complete upgrade guide including Cosmovisor and manual upgrade instructions, build from source guide, and troubleshooting.
+Complete upgrade guide including Cosmovisor and manual upgrade instructions, build from source guide, and troubleshooting. This upgrade includes store migrations for the deployment and market modules; 128GB RAM with swap is recommended.
 
 ---
 
@@ -42,12 +42,11 @@ Complete upgrade guide including Cosmovisor and manual upgrade instructions, bui
 ## Best Practices
 
 **Before Every Upgrade:**
-1. **Read the complete upgrade guide
-2. **Backup your validator keys
-3. **Test the upgrade on a non-validator node first
-4. **Monitor Discord channels for announcements
-5. **Verify binary checksums
-6. **Be available during the upgrade window
+1. **Read the complete upgrade guide**
+2. **Backup your validator keys**
+3. **Monitor Discord channels for announcements**
+4. **Verify binary checksums**
+5. **Be available during the upgrade window**
 
 **Recommended Setup:**
 - Use Cosmovisor for automatic upgrades

…ors/network-upgrades/mainnet-15/index.md …ors/network-upgrades/mainnet-16/index.mdsrc/content/Docs/node-operators/network-upgrades/mainnet-15/index.md renamed to src/content/Docs/node-operators/network-upgrades/mainnet-16/index.md src/content/Docs/node-operators/network-upgrades/mainnet-15/index.md renamed to src/content/Docs/node-operators/network-upgrades/mainnet-16/index.md

@@ -2,29 +2,39 @@
 categories: ["Node Operators", "Network Upgrades"]
 tags: ["Mainnet", "Upgrade", "Cosmovisor"]
 weight: 1
-title: "Mainnet 15 - Akash v1.1.0"
-linkTitle: "Mainnet 15"
-description: "Complete upgrade guide for Mainnet 15 (Akash v1.1.0)"
+title: "Mainnet 16 - Akash v1.2.0"
+linkTitle: "Mainnet 16"
+description: "Complete upgrade guide for Mainnet 16 (Akash v1.2.0)"
 ---
 
-**Upgrade guide for Akash Network Mainnet 15 upgrade to v1.1.0.**
+**Upgrade guide for Akash Network Mainnet 16 upgrade to v1.2.0.**
 
-This guide provides step-by-step instructions for upgrading your node to Akash v1.1.0 using both Cosmovisor (recommended) and manual upgrade methods.
+This guide provides step-by-step instructions for upgrading your node to Akash v1.2.0 using both Cosmovisor (recommended) and manual upgrade methods.
 
 ---
 
 ## Upgrade Details
 
 **Upgrade Information:**
-- **Upgrade Name:** Mainnet15
-- **Binary Version:** `v1.1.0`
-- **Block Height:** 24,332,547
-- **Estimated Time:** Monday, November 24th, 2025 at 14:10 UTC
-- **Expected Duration:** 10-15 minutes of network downtime
+- **Upgrade Name:** Mainnet16
+- **Binary Version:** `v1.2.0`
+- **Block Height:** 25,789,395
+- **Estimated Time:** Wednesday, March 4th, 2025 at 14:00 UTC
+- **Expected Duration:** 10–15 minutes of network downtime (longer possible due to store migrations)
 - **Binary Release:** Available approximately 10 hours before the upgrade
-- **Binary Links:** [GitHub Releases](https://github.com/akash-network/node/releases/tag/v1.1.0)
+- **Binary Links:** [GitHub Releases](https://github.com/akash-network/node/releases/tag/v1.2.0)
 
->  **Note:** Block times have high variance. Please monitor the block countdown for more precise timing estimates.
+> **Note:** Block times have high variance. Please monitor the chain or block explorer for more precise timing estimates.
+
+---
+
+## Upgrade Features
+
+
+- **CometBFT Tachyon advisory fix** – Public rollout of CSA-2026-001: Tachyon (previously distributed as binary-only to validators).
+- **Deployment and market module store migrations** – Migrate from manual KVStore key encoding to `cosmossdk.io/collections`. `IndexedMap` replaces hand-rolled prefix keys with type-safe, indexed collections.
+- **Secondary indexes** – State, Owner, and Provider indexes enable efficient filtered queries without full-store iteration.
+- **Lease closed reason** – `MsgCloseBid` now records why a lease was closed (e.g. Unstable). The reason is persisted on the lease and returned in query responses.
 
 ---
 
@@ -34,7 +44,7 @@ To ensure a network upgrade with minimal downtime, Akash Validators should be av
 
 **Timeline:**
 - **One hour prior to upgrade** - Available and monitoring the Akash Discord server's `#validators` and `#validator-announcements` channels for any late-breaking guidance
-- **During upgrade window** - Available throughout the expected 10-15 minutes of network downtime
+- **During upgrade window** – Available throughout the expected downtime (may be longer than usual due to store migrations)
 - **One hour post upgrade** - Available and monitoring Discord channels for any possible revised strategies or updates deemed necessary
 
 ### Emergency Coordination
@@ -47,10 +57,11 @@ In the event of issues during the upgrade, coordinate via the **#validators chan
 
 ## Hardware Requirements
 
-This upgrade does not carry significant state changes and is relatively lightweight.
+This upgrade performs **store migrations** for the deployment and market modules, re-encoding all deployments, groups, orders, bids, and leases into the new collections format.
 
 **Recommended Specifications:**
-- **RAM:** 64 GB minimum (with swap enabled)
+- **OS:** Ubuntu 24.04 recommended
+- **RAM:** 128 GB minimum (with swap enabled)
 - **CPU:** 8+ cores recommended
 - **Storage:** Sufficient space for blockchain data (1 TB+ recommended)
 
@@ -72,7 +83,7 @@ The following instructions assume the `akash` and `cosmovisor` binaries are alre
 
 > **Note:** Cosmovisor v1.5.0 or higher is required.
 
-Validators supervised by Cosmovisor with `DAEMON_ALLOW_DOWNLOAD_BINARIES=true` will automatically download upgrade binaries from the upgrade info file.
+Validators and RPCs supervised by Cosmovisor with `DAEMON_ALLOW_DOWNLOAD_BINARIES=true` will automatically download upgrade binaries from the upgrade info file (info.json).
 
 ### Step 1: Configure Cosmovisor
 
@@ -125,7 +136,7 @@ WantedBy=multi-user.target
 
 **Important Environment Variables:**
 
-- `DAEMON_ALLOW_DOWNLOAD_BINARIES=false` - It's recommended to manually place the binary (set to `true` for auto-download)
+- `DAEMON_ALLOW_DOWNLOAD_BINARIES=false` – It's recommended to manually place the binary (set to `true` for auto-download from upgrade info)
 - `UNSAFE_SKIP_BACKUP=true` - Set to `false` if you want automatic backup before upgrade
 - `DAEMON_SHUTDOWN_GRACE=15s` - Grace period for cleanup before shutdown
 
@@ -149,7 +160,7 @@ sudo systemctl status akash
 
 > **Note:** Skip this step if you have enabled `DAEMON_ALLOW_DOWNLOAD_BINARIES=true` in your Cosmovisor configuration.
 
-Download the Akash v1.1.0 binary for your platform from the [GitHub releases page](https://github.com/akash-network/node/releases/tag/v1.1.0).
+This upgrade uses an info.json file that references the correct release with pre-built binaries. Download the Akash v1.2.0 binary for your platform from the [GitHub releases page](https://github.com/akash-network/node/releases/tag/v1.2.0).
 
 **Select your platform:**
 - Linux AMD64
@@ -165,25 +176,25 @@ Create the folder for the upgrade and copy the binary:
 
 ```bash
 # Create the upgrade directory
-mkdir -p $HOME/.akash/cosmovisor/upgrades/v1.1.0/bin
+mkdir -p $HOME/.akash/cosmovisor/upgrades/v1.2.0/bin
 
 # Copy the downloaded binary (adjust path to your download location)
-cp /path/to/downloaded/akash $HOME/.akash/cosmovisor/upgrades/v1.1.0/bin/akash
+cp /path/to/downloaded/akash $HOME/.akash/cosmovisor/upgrades/v1.2.0/bin/akash
 
 # Make it executable
-chmod +x $HOME/.akash/cosmovisor/upgrades/v1.1.0/bin/akash
+chmod +x $HOME/.akash/cosmovisor/upgrades/v1.2.0/bin/akash
 
 # Verify the version
-$HOME/.akash/cosmovisor/upgrades/v1.1.0/bin/akash version
+$HOME/.akash/cosmovisor/upgrades/v1.2.0/bin/akash version
 ```
 
-**Expected output:** `v1.1.0`
+**Expected output:** `v1.2.0`
 
 ### Step 5: Wait for Upgrade
 
-At the proposed block height (24,332,547), Cosmovisor will automatically:
-1. Stop the current binary (v1.0.0)
-2. Set the upgrade binary as the new current binary (v1.1.0)
+At the proposed block height (25,789,395), Cosmovisor will automatically:
+1. Stop the current binary
+2. Set the upgrade binary as the new current binary (v1.2.0)
 3. Restart the node
 
 **Monitor the upgrade:**
@@ -206,7 +217,7 @@ Using Cosmovisor to perform the upgrade is not mandatory. Node operators can man
 
 ### Manual Upgrade Steps
 
-**1. Wait for the chain to halt** at block height 24,332,547
+**1. Wait for the chain to halt** at block height 25,789,395
 
 **2. Stop your node** (if not already stopped):
 
@@ -216,13 +227,13 @@ sudo systemctl stop akash
 
 **3. Install the new binary:**
 
-Either download the precompiled binary from [GitHub releases](https://github.com/akash-network/node/releases/tag/v1.1.0) or build from source (see [Build Binary From Source](#build-binary-from-source)).
+Either download the precompiled binary from [GitHub releases](https://github.com/akash-network/node/releases/tag/v1.2.0) or build from source (see [Build Binary From Source](#build-binary-from-source)).
 
 **4. Verify the binary version:**
 
 ```bash
 akash version
-# Should output: v1.1.0
+# Should output: v1.2.0
 ```
 
 **5. Restart your node:**
@@ -251,7 +262,7 @@ Ensure the following dependencies are installed before building:
 
 | Dependency | Minimum Version | Notes |
 |------------|-----------------|-------|
-| golang | >= 1.25.4 | Required for compiling Go code |
+| golang | >= 1.26 | Required for compiling Go code |
 | direnv | latest | Environment management - [direnv.net](https://direnv.net) |
 | docker | latest | Required for containerized builds |
 | make | latest | Build automation |
@@ -284,7 +295,7 @@ git clone https://github.com/akash-network/node.git
 cd node
 
 # Checkout the release tag
-git checkout v1.1.0
+git checkout v1.2.0
 
 # Allow direnv to set up the environment
 direnv allow
@@ -316,17 +327,17 @@ The directory structure will look like:
 
 ```bash
 .cache/goreleaser/main/<YOUR_OS_ARCH>/akash version
-# Should output: v1.1.0
+# Should output: v1.2.0
 ```
 
 ### Using the Built Binary
 
 **For Cosmovisor:**
 
 ```bash
-mkdir -p $HOME/.akash/cosmovisor/upgrades/v1.1.0/bin
-cp .cache/goreleaser/main/<YOUR_OS_ARCH>/akash $HOME/.akash/cosmovisor/upgrades/v1.1.0/bin/akash
-chmod +x $HOME/.akash/cosmovisor/upgrades/v1.1.0/bin/akash
+mkdir -p $HOME/.akash/cosmovisor/upgrades/v1.2.0/bin
+cp .cache/goreleaser/main/<YOUR_OS_ARCH>/akash $HOME/.akash/cosmovisor/upgrades/v1.2.0/bin/akash
+chmod +x $HOME/.akash/cosmovisor/upgrades/v1.2.0/bin/akash
 ```
 
 **For manual upgrade:**
@@ -345,15 +356,15 @@ akash status | jq '.sync_info'
 
 **Important fields:**
 - `catching_up: false` - Node is synced
-- `latest_block_height` - Current block (should be > 24,332,547)
+- `latest_block_height` – Current block (should be > 25,789,395)
 
 ### Check Binary Version
 
 ```bash
 akash version
 ```
 
-**Expected output:** `v1.1.0`
+**Expected output:** `v1.2.0`
 
 ### Check Validator Status
 
@@ -381,6 +392,7 @@ sudo journalctl -u akash -n 100 --no-pager
 - Binary not executable: `chmod +x /path/to/akash`
 - Wrong binary version: Verify with `akash version`
 - Permission issues: Check user/group settings in systemd service
+- Store migration taking longer: Ensure 128GB RAM and swap; monitor memory and disk
 
 ### Node Out of Sync
 
@@ -399,7 +411,7 @@ If low peer count, add peers from:
 **Verify upgrade binary exists:**
 
 ```bash
-ls -la $HOME/.akash/cosmovisor/upgrades/v1.1.0/bin/akash
+ls -la $HOME/.akash/cosmovisor/upgrades/v1.2.0/bin/akash
 ```
 
 **Check Cosmovisor logs:**