docs: updated content for union-testnet-7

site/src/content/docs/docs/infrastructure/node-operators/getting-started.mdx

@@ -37,14 +37,14 @@ Double-check the version and architecture in the link before downloading.
     ```sh frame='none'
     curl --output uniond --location https://github.com/unionlabs/union/releases/download/$UNIOND_VERSION/uniond-release-x86_64-linux
     ```
-    *Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-6'}).current} />*
+    *Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-7'}).current} />*
 
   </TabItem>
   <TabItem label='aarch64-linux'>
     ```sh frame='none'
     curl --output uniond --location https://github.com/unionlabs/union/releases/download/$UNIOND_VERSION/uniond-release-aarch64-linux
     ```
-    *Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-6'}).current} />*
+    *Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-7'}).current} />*
 
   </TabItem>
 </Tabs>
@@ -69,7 +69,7 @@ We also provide containers in our [package registry](https://github.com/orgs/uni
 docker pull ghcr.io/unionlabs/uniond-release:$UNIOND_VERSION
 ```
 
-_Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-6'}).current} />_
+_Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-7'}).current} />_
 
 When running the container, make sure to map a volume to the path passed in `--home` options to ensure data persistence. From here on the guide assumes the usage of a regular binary. The [docker-compose](/docs/infrastructure/node-operators/docker-compose/) section is more suited for docker users.
 
@@ -88,10 +88,10 @@ First, set some environment variables, which are used throughout initialization.
 <Code
   lang='bash'
   code={dedent(`
-    export CHAIN_ID=union-testnet-6
+    export CHAIN_ID=union-testnet-7
     export MONIKER="Unionized Goblin"
     export KEY_NAME=alice
-    export GENESIS_URL="${getSeedsParts('union-testnet-6').address}:26657/genesis"
+    export GENESIS_URL="${getSeedsParts('union-testnet-7').address}:26657/genesis"
   `)}
 />
 
@@ -106,11 +106,11 @@ uniond init $MONIKER --chain-id $CHAIN_ID
 
 Next, edit `~/.union/config/config.toml`. We'll set the seeds to ensure your node can connect to the peer-to-peer network.
 
-For `union-testnet-6` replace `seeds = ""` with:
+For `union-testnet-7` replace `seeds = ""` with:
 
 <Code
   lang='toml'
-  code={`seeds = "${chainVersion({ chainId: 'union-testnet-6' }).seeds}"`} 
+  code={`seeds = "${chainVersion({ chainId: 'union-testnet-7' }).seeds}"`} 
 />
 
 

site/src/content/docs/docs/infrastructure/node-operators/node-configuration.mdx

@@ -21,11 +21,11 @@ Located in `config/client.toml`, this file is host to client settings.
 
 Update this value to ensure that your client is supplied with the correct chain ID.
 
-For the Union Testnet, this value should be `"union-testnet-6"`.
+For the Union Testnet, this value should be `"union-testnet-7"`.
 
 ```toml
 # The network chain ID
-chain-id = "union-testnet-6"
+chain-id = "union-testnet-7"
 ```
 
 ### Host/Port for the Tendermint RPC
@@ -119,11 +119,11 @@ external_address = "example.com:26656"
 
 Located in the `p2p` TOML table under the "P2P Configuration Options" section.
 
-Seed nodes help orchestrate initial connections to the network. For union-testnet-6, the seed nodes are:
+Seed nodes help orchestrate initial connections to the network. For union-testnet-7, the seed nodes are:
 
 <Code
   lang='toml'
-  code={`seeds = "${chainVersion({ chainId: 'union-testnet-6' }).seeds}"`} 
+  code={`seeds = "${chainVersion({ chainId: 'union-testnet-7' }).seeds}"`} 
 />
 
 

site/src/content/docs/docs/joining-testnet/creating-validators.mdx

@@ -69,7 +69,7 @@ Then you can submit this file using the `create-validator` sub-command:
 ```sh frame="none"
 uniond tx staking create-validator $VALIDATOR_JSON_PATH \
 	--from $KEY_NAME \
-	--chain-id union-testnet-6
+	--chain-id union-testnet-7
 ```
 
 _Where `VALIDATOR_JSON_PATH` is the path to your `validator.json`_
@@ -89,7 +89,7 @@ touch ~/.unionvisor/validator.json
 
 uniond tx staking create-validator /.unionvisor/validator.json \
 	--from $KEY_NAME \
-	--chain-id union-testnet-6
+	--chain-id union-testnet-7
 ```
 
 :::

site/src/content/docs/docs/joining-testnet/faq.mdx

@@ -10,7 +10,7 @@ As we continue onboarding validators and expanding the testnet, we'll populate t
 
 We started our testnet with the goal of onboarding 64 validators. The sign-up form for these first 64 slots has been closed.
 
-We have now expanded `union-testnet-6` to support 128 validators. Those interested can submit their Union address to the Subo Survey Bot on [our Discord](https://discord.gg/union-build) to have a chance of being selected as a validator and receiving tokens from the Union team. The Subo "Union Testnet Validator Intake Form" is set to close on February 19th, 2024.
+We have now expanded the Union testnet to support 128 validators. Those interested can submit their Union address to the Subo Survey Bot on [our Discord](https://discord.gg/union-build) to have a chance of being selected as a validator and receiving tokens from the Union team. The Subo "Union Testnet Validator Intake Form" is set to close on February 19th, 2024.
 
 ### Do you have any public REST/RPC/gRPC endpoints?
 

site/src/content/docs/docs/joining-testnet/getting-started.mdx

@@ -4,7 +4,7 @@ sidebar:
   order: 0
 ---
 
-Welcome to the Union Testnet! This guide will instruct you on running a node and creating a validator for `union-testnet-6`.
+Welcome to the Union Testnet! This guide will instruct you on running a node and creating a validator for `union-testnet-7`.
 
 ## Steps
 

site/src/content/docs/docs/joining-testnet/obtaining-uniond.mdx

@@ -23,7 +23,7 @@ To get the `uniond` image, you can visit [our container](https://github.com/orgs
 docker pull ghcr.io/unionlabs/uniond-release:$UNIOND_VERSION
 ```
 
-_Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-6'}).current} />_
+_Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-7'}).current} />_
 
 ## Running uniond
 
@@ -98,7 +98,7 @@ For example, in `zsh`, you can add the following alias to your `.zshrc`:
 alias uniond='docker run -v ~/.union:/.union -v /tmp:/tmp --network host -it ghcr.io/unionlabs/uniond-release:$UNIOND_VERSION --home /.union'
 ```
 
-_Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-6'}).current} />_
+_Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-7'}).current} />_
 
 This will enable you to issue `uniond` sub-commands with such as `uniond keys add` with ease.
 

site/src/content/docs/docs/joining-testnet/unionvisor.mdx

@@ -13,15 +13,15 @@ Unionvisor is a utility for managing `uniond` deployments. It manages running, u
 
 ## Obtaining Unionvisor
 
-We release container images of Unionvisor called bundles. Each bundle contains everything required for running Unionvisor and joining a particular network. The Unionvisor bundle for `union-testnet-6` is `bundle-testnet-6`. You can obtain the Unionvisor bundle for `union-testnet-6` from our [GitHub Container Registry](https://github.com/orgs/unionlabs/packages/container/package/bundle-testnet-6).
+We release container images of Unionvisor called bundles. Each bundle contains everything required for running Unionvisor and joining a particular network. The Unionvisor bundle for `union-testnet-7` is `bundle-testnet-7`. You can obtain the Unionvisor bundle for `union-testnet-7` from our [GitHub Container Registry](https://github.com/orgs/unionlabs/packages/container/package/bundle-testnet-7).
 
 Alternatively, you can run the following command:
 
 ```sh frame="none"
-docker pull ghcr.io/unionlabs/bundle-testnet-6:$UNIONVISOR_VERSION
+docker pull ghcr.io/unionlabs/bundle-testnet-7:$UNIONVISOR_VERSION
 ```
 
-_Where `UNIONVISOR_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-6'}).current} />_
+_Where `UNIONVISOR_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-7'}).current} />_
 
 ## Running Unionvisor
 
@@ -53,10 +53,10 @@ To do this, we'll be using Docker volumes.
     docker run \\
       --volume ~/.unionvisor:/.unionvisor \\
       --volume /tmp:/tmp \\
-      -it ghcr.io/unionlabs/bundle-testnet-6:$UNIONVISOR_VERSION \\
+      -it ghcr.io/unionlabs/bundle-testnet-7:$UNIONVISOR_VERSION \\
       init --moniker $MONIKER \\
-      --network union-testnet-6 \\
-      --seeds "${chainVersion({chainId: 'union-testnet-6'}).seeds}"
+      --network union-testnet-7 \\
+      --seeds "${chainVersion({chainId: 'union-testnet-7'}).seeds}"
   `)}
 />
 _Where `MONIKER` is the preferred moniker you'd like to use on this node._
@@ -85,7 +85,7 @@ After the above command is done running, you should have a `.unionvisor` folder
   - data
     - priv_validator_state.json
 - versions
-  - <FunctionResult result={chainVersion({chainId: 'union-testnet-6'}).current} />- uniond
+  - <FunctionResult result={chainVersion({chainId: 'union-testnet-7'}).current} />- uniond
 
 </FileTree>
 
@@ -116,10 +116,10 @@ To run `uniond` sub-commands, it will be useful to alias the Docker command in y
 For example, in `zsh`, you can add the following alias to your `.zshrc`:
 
 ```sh frame="none"
-alias uniond='docker run -v ~/.unionvisor:/.unionvisor -v /tmp:/tmp --network host -it ghcr.io/unionlabs/bundle-testnet-6:$UNIONVISOR_VERSION --log-level off call --'
+alias uniond='docker run -v ~/.unionvisor:/.unionvisor -v /tmp:/tmp --network host -it ghcr.io/unionlabs/bundle-testnet-7:$UNIONVISOR_VERSION --log-level off call --'
 ```
 
-_Where `UNIONVISOR_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-6'}).current} />_
+_Where `UNIONVISOR_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-7'}).current} />_
 
 :::note
 
@@ -139,7 +139,7 @@ A minimal Docker Compose file for Unionvisor looks like this:
 ```yaml
 services:
   node:
-    image: ghcr.io/unionlabs/bundle-testnet-6:$UNIONVISOR_VERSION
+    image: ghcr.io/unionlabs/bundle-testnet-7:$UNIONVISOR_VERSION
     volumes:
       - ~/.unionvisor:/.unionvisor
       - /tmp:/tmp

site/src/content/docs/docs/joining-testnet/upgrade-history.mdx

@@ -32,8 +32,18 @@ The network `union-testnet-5` has not had any binary upgrades since genesis.
 
 ## union-testnet-6
 
+<Badge text="Deprecated" variant="caution" />
+
 The network `union-testnet-6` has not had any binary upgrades since genesis.
 
 | Upgrade | Height  |
 | ------- | ------- |
 | v0.19.0 | genesis |
+
+## union-testnet-7
+
+The network `union-testnet-7` has not had any binary upgrades since genesis.
+
+| Upgrade | Height  |
+| ------- | ------- |
+| v0.20.0 | genesis |