fix(docs): update CLI commands and versions for v7.2.0

glandua · claude · glandua · commit 883140a09dd9 · 2026-02-07T21:41:09.000-05:00
Replace deprecated `regen config` syntax with new confix-based subcommands (`regen config set/view/get`), update binary versions from v6.0.0 to v7.2.0, update Go requirement to 1.23, remove rosetta references, and add CLI migration documentation. Fixes #2311, fixes #2312. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
diff --git a/docs/.vuepress/config.ts b/docs/.vuepress/config.ts
@@ -195,7 +195,7 @@ export default defineUserConfig({
             { text: 'regen migrate', link: '/commands/regen_migrate' },
             { text: 'regen query', link: '/commands/regen_query' },
             { text: 'regen rollback', link: '/commands/regen_rollback' },
-            { text: 'regen rosetta', link: '/commands/regen_rosetta' },
+
             { text: 'regen start', link: '/commands/regen_start' },
             { text: 'regen status', link: '/commands/regen_status' },
             { text: 'regen tendermint', link: '/commands/regen_tendermint' },
diff --git a/docs/README_commands.md b/docs/README_commands.md
@@ -1,5 +1,7 @@
 # Commands
 
+<!-- TODO: Regenerate command docs from the v7.2.0 binary to reflect new config subcommands and removed rosetta command -->
+
 The following commands are available using the `regen` binary. The documentation for each command is auto-generated from the help text.
 
 - [regen](regen.md)
@@ -14,7 +16,7 @@ The following commands are available using the `regen` binary. The documentation
 - [regen migrate](regen_migrate.md)
 - [regen query](regen_query.md)
 - [regen rollback](regen_rollback.md)
-- [regen rosetta](regen_rosetta.md)
+
 - [regen start](regen_start.md)
 - [regen status](regen_status.md)
 - [regen tendermint](regen_tendermint.md)
diff --git a/docs/ledger/get-started/README.md b/docs/ledger/get-started/README.md
@@ -8,15 +8,15 @@ If you have not already, check out [Command-Line Interface](../interfaces.md#com
 
 The following instructions are for building and installing the `regen` binary from its source code. This is the recommended way for most users. If you do not have Git, Make, and Go installed, and you would prefer not to install them, you can install the `regen` binary using a [pre-built package](#pre-built-package).
 
-In the following examples we use the latest available version of Regen Ledger (`v6.0.0`), which is the same version used by node operators running [Regen Mainnet](regen-mainnet.md) and [Regen Testnet](regen-testnet.md).
+In the following examples we use the latest available version of Regen Ledger (`v7.2.0`), which is the same version used by node operators running [Regen Mainnet](regen-mainnet.md) and [Regen Testnet](regen-testnet.md).
 
 ### Prerequisites
 
 In order to build the `regen` binary from source, you'll need the following: 
 
 - [Git](https://git-scm.com) `>=2` .
 - [Make](https://www.gnu.org/software/make/) `>=4`
-- [Go](https://golang.org/) `>=1.21`
+- [Go](https://golang.org/) `>=1.23`
 
 *Note: If you are new to go and installing it for the first time, make sure you include the following `PATH` export in your bash profile: `export PATH=$(go env GOPATH)/bin:$PATH`.*
 
@@ -37,7 +37,7 @@ cd regen-ledger
 Check out the latest stable version:
 
 ```bash
-git checkout v6.0.0
+git checkout v7.2.0
 ```
 
 ### Build Only
@@ -59,7 +59,7 @@ Check to make sure the build was successful:
 You should see the following:
 
 ```bash
-v6.0.0
+v7.2.0
 ```
 
 Are you not seeing the above?
@@ -85,7 +85,7 @@ regen version
 You should see the following:
 
 ```bash
-v6.0.0
+v7.2.0
 ```
 
 Are you not seeing the above?
@@ -99,36 +99,59 @@ The following instructions are for installing the `regen` binary using a pre-bui
 
 ### For Linux Distributions
 
-Download the zip file:
+#### Option A: Standalone Binary
 
-```bash
-curl -LO https://github.com/regen-network/regen-ledger/releases/download/v6.0.0/regen-ledger-6.0.0-linux-amd64.tar.gz
+Download the binary:
 
+```bash
+curl -LO https://github.com/regen-network/regen-ledger/releases/download/v7.2.0/regen-ledger-v7.2.0-linux-amd64
 ```
 
 Verify the checksum:
 
 ```bash
-sha256sum regen-ledger-6.0.0-linux-amd64.tar.gz
+sha256sum regen-ledger-v7.2.0-linux-amd64
 ```
 
 You should see the following:
 
 ```bash
-b50f0bca044a06d7c9e6012c1297bce382ed97facb2dbba6a3a9d7e6399d8c86 regen-ledger-6.0.0-linux-amd64.tar.gz
+953905826b096085f6574a08c8a1b21471cdd8e8a07c6d8e00cf8780061d1634  regen-ledger-v7.2.0-linux-amd64
 ```
 
-Uncompress the tar.gz file:
+Move the binary to your local bin directory:
 
 ```bash
-mkdir regen-ledger-6.0.0-linux-amd64
-tar -xzf regen-ledger-6.0.0-linux-amd64.tar.gz -C regen-ledger-6.0.0-linux-amd64
+sudo mv regen-ledger-v7.2.0-linux-amd64 /usr/local/bin/regen
+sudo chmod +x /usr/local/bin/regen
 ```
 
-Move the binary to your local bin directory:
+#### Option B: Tarball
+
+Download the tarball:
+
+```bash
+curl -LO https://github.com/regen-network/regen-ledger/releases/download/v7.2.0/regen-ledger-v7.2.0-linux-amd64.tar.gz
+```
+
+Verify the checksum:
+
+```bash
+sha256sum regen-ledger-v7.2.0-linux-amd64.tar.gz
+```
+
+You should see the following:
+
+```bash
+c961c27be0f327bfcce0aa2b2dfecb58b3973bf7c95230700ad2eee657f89a57  regen-ledger-v7.2.0-linux-amd64.tar.gz
+```
+
+Uncompress the tar.gz file and move the binary:
 
 ```bash
-sudo mv regen-ledger-6.0.0-linux-amd64/regend /usr/local/bin/regen
+tar -xzf regen-ledger-v7.2.0-linux-amd64.tar.gz
+sudo mv regen-ledger-v7.2.0-linux-amd64 /usr/local/bin/regen
+sudo chmod +x /usr/local/bin/regen
 ```
 
 Check if the installation was successful:
@@ -140,9 +163,9 @@ regen version
 You should see the following:
 
 ```bash
-v6.0.0
+v7.2.0
 ```
 
 ### Additional Packages
 
-Additional packages and checksums are available under "Assets" on the [Release Page](https://github.com/regen-network/regen-ledger/releases/tag/v6.0.0).
+Additional packages and checksums are available under "Assets" on the [Release Page](https://github.com/regen-network/regen-ledger/releases/tag/v7.2.0).
diff --git a/docs/ledger/get-started/local-testnet.md b/docs/ledger/get-started/local-testnet.md
@@ -100,12 +100,18 @@ Now that you have updated the `genesis.json` file, you are ready to start the no
 ## Set the minimum gas price
 
 We need to update the minimum gas price before we can start the node.
-Open the `~/.regen/config/app.toml` file and set the value as:
+You can either edit the `~/.regen/config/app.toml` file directly and set the value as:
 
 ```
 minimum-gas-prices = "0uregen"
 ```
 
+Or use the `config set` command:
+
+```bash
+regen config set app minimum-gas-prices "0uregen"
+```
+
 ## Start Node
 
 Well, what are you waiting for?
diff --git a/docs/ledger/get-started/manage-keys.md b/docs/ledger/get-started/manage-keys.md
@@ -19,13 +19,13 @@ The `test` keyring backend is best for testing, i.e. when security or recovery i
 To check the current configuration, run the following:
 
 ```sh
-regen config
+regen config view client
 ```
 
 To configure the keyring backend for all commands, run the following:
 
 ```sh
-regen config keyring-backend [keyring-backend]
+regen config set client keyring-backend [keyring-backend]
 ```
 
 ## Add Key
diff --git a/docs/ledger/get-started/regen-mainnet.md b/docs/ledger/get-started/regen-mainnet.md
@@ -25,10 +25,10 @@ To interact with a node on Regen Mainnet, we first need to make sure we have `ch
 To view your current configuration, run the following command:
 
 ```bash
-regen config
+regen config view client
 ```
 
-The above command displays the configuration in the `~/.regen/config/client.toml` file. This file can be updated using the same `config` command along with key-value pairs (see below).
+The above command displays the configuration in the `~/.regen/config/client.toml` file. This file can be updated using the `config set` subcommand (see below).
 
 #### Chain ID
 
@@ -37,7 +37,7 @@ The chain ID for Regen Mainnet is `regen-1`. When using the `regen` binary to co
 To configure the chain ID for all commands, run the following:
 
 ```sh
-regen config chain-id regen-1
+regen config set client chain-id regen-1
 ```
 
 #### Node Endpoint
@@ -47,5 +47,5 @@ When interacting with a live network, you need to connect to a remote node or ha
 To configure the node endpoint for all commands, run the following:
 
 ```sh
-regen config node http://mainnet.regen.network:26657/
+regen config set client node http://mainnet.regen.network:26657/
 ```
diff --git a/docs/ledger/get-started/regen-testnet.md b/docs/ledger/get-started/regen-testnet.md
@@ -31,10 +31,10 @@ To interact with a node on Regen Testnet, we first need to make sure we have `ch
 To view your current configuration, run the following command:
 
 ```bash
-regen config
+regen config view client
 ```
 
-The above command displays the configuration in the `~/.regen/config/client.toml` file. This file can be updated using the same `config` command along with key-value pairs (see below).
+The above command displays the configuration in the `~/.regen/config/client.toml` file. This file can be updated using the `config set` subcommand (see below).
 
 #### Chain ID
 
@@ -43,7 +43,7 @@ The chain ID for Regen Testnet is `regen-upgrade`. When using the `regen` binary
 To configure the chain ID for all commands, run the following:
 
 ```sh
-regen config chain-id regen-upgrade
+regen config set client chain-id regen-upgrade
 ```
 
 #### Node Endpoint
@@ -53,5 +53,5 @@ When interacting with a live network, you need to connect to a remote node or ha
 To configure the node endpoint for all commands, run the following:
 
 ```sh
-regen config node https://rpc-regen-upgrade.vitwit.com:443
+regen config set client node https://rpc-regen-upgrade.vitwit.com:443
 ```
diff --git a/docs/ledger/migrations/v7.0-migration.md b/docs/ledger/migrations/v7.0-migration.md
@@ -66,12 +66,12 @@ Response
 
 ##### Denom object format
 
-Old format (DenomTrace)  
+Old format (DenomTrace)
 ``` json
 {
   "base_denom": "uregen",
   "path": "transfer/channel-0/transfer/channel-1"
-}  
+}
 ```
 
 New format (Denom)
@@ -92,3 +92,58 @@ New format (Denom)
 }
 ```
 ---
+
+### CLI Changes
+
+Regen Ledger v7.0 replaces the legacy `regen config` command with a new subcommand structure powered by [confix](https://docs.cosmos.network/main/build/tooling/confix). Several other commands have been added or removed.
+
+#### Configuration Commands
+
+| Old Command (v6.x) | New Command (v7.x) |
+|---------------------|---------------------|
+| `regen config` (view) | `regen config view client` |
+| `regen config <key> <value>` | `regen config set client <key> <value>` |
+| N/A | `regen config get client <key>` |
+| N/A | `regen config set app <key> <value>` |
+| N/A | `regen config view app` |
+| N/A | `regen config migrate <target-version> <config-path>` |
+| N/A | `regen config diff <config-path>` |
+
+#### Removed Commands
+
+- `regen rosetta` — The Rosetta API integration has been removed.
+- `regen tx aux-to-fee` — Replaced by `regen tx simulate`.
+
+#### New Commands
+
+- `regen tx simulate` — Simulate a transaction.
+- `regen query wait-tx` — Wait for a transaction to be included in a block.
+- `regen query blocks` — Query for paginated blocks matching events.
+- `regen query block-results` — Query for block results at a given height.
+
+#### AutoCLI
+
+Many query and transaction commands are now auto-generated using [AutoCLI](https://docs.cosmos.network/main/build/building-modules/autocli). The command interface remains the same, but help text and flag names may differ slightly.
+
+### Configuration File Migration
+
+After upgrading to v7.x, you should migrate your configuration files to the latest format:
+
+```bash
+regen config migrate v0.53 ~/.regen/config/app.toml
+```
+
+You can also check what has changed compared to the defaults:
+
+```bash
+regen config diff ~/.regen/config/app.toml
+```
+
+### Environment Variables
+
+Regen Ledger v7.x supports environment variable overrides following the `REGEN_*` pattern. For example:
+
+- `REGEN_MINIMUM_GAS_PRICES` overrides `minimum-gas-prices` in `app.toml`
+- `REGEN_API_ENABLE` overrides `api.enable` in `app.toml`
+
+Environment variables use the pattern `REGEN_<SECTION>_<KEY>` with dots and hyphens replaced by underscores.
diff --git a/docs/validators/get-started/README.md b/docs/validators/get-started/README.md
@@ -10,7 +10,7 @@ We recommend the following hardware specifications:
 
 ## Setup Instructions
 
-We recommend using Ubuntu 18.04 or 20.04. The following setup instructions are assuming you are using one of these images and the setup may be different if not.
+We recommend using Ubuntu 22.04 or 24.04. The following setup instructions are assuming you are using one of these images and the setup may be different if not.
 
 ### Install Dependencies
 
@@ -31,25 +31,25 @@ sudo apt install git build-essential wget jq -y
 Download Go:
 
 ```bash
-wget https://dl.google.com/go/go1.19.4.linux-amd64.tar.gz
+wget https://dl.google.com/go/go1.23.8.linux-amd64.tar.gz
 ```
 
 Verify data integrity:
 
 ```bash
-sha256sum go1.19.4.linux-amd64.tar.gz
+sha256sum go1.23.8.linux-amd64.tar.gz
 ```
 
 Verify SHA-256 hash:
 
 ```bash
-9df122d6baf6f2275270306b92af3b09d7973fb1259257e284dba33c0db14f1b
+45b87381172a58d62c977f27c4683c8681ef36580abecd14fd124d24ca306d3f
 ```
 
 Unpack Go download:
 
 ```bash
-sudo tar -C /usr/local -xzf go1.19.4.linux-amd64.tar.gz
+sudo rm -rf /usr/local/go && sudo tar -C /usr/local -xzf go1.23.8.linux-amd64.tar.gz
 ```
 
 Set up environment:
diff --git a/docs/validators/get-started/install-regen.md b/docs/validators/get-started/install-regen.md
@@ -1,6 +1,6 @@
 # Install Regen
 
-The following instructions are for building and installing the `regen` binary. In these instructions, we use the same version that was used to start both Regen Mainnet. An alternative to syncing a node from genesis is [Using State Sync](using-state-sync.md) with the latest version.
+The following instructions are for building and installing the `regen` binary. In these instructions, we use the latest version running on Regen Mainnet. An alternative to syncing a node from genesis is [Using State Sync](using-state-sync.md) with the latest version, which is the recommended approach for new validators.
 
 ## Prerequisites
 
@@ -23,7 +23,7 @@ cd regen-ledger
 Check out the genesis version:
 
 ```bash
-git checkout v6.0.0
+git checkout v7.2.0
 ```
 
 Build and install the `regen` binary:
@@ -42,5 +42,5 @@ regen version
 You should see the following:
 
 ```bash
-v6.0.0
+v7.2.0
 ```
diff --git a/docs/validators/upgrades/v7.0-upgrade.md b/docs/validators/upgrades/v7.0-upgrade.md
