docs: update chain-id and genesis (#3587)

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

@@ -38,14 +38,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-8'}).current} />*
+    *Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-9'}).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-8'}).current} />*
+    *Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-9'}).current} />*
 
   </TabItem>
 </Tabs>
@@ -70,7 +70,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-8'}).current} />_
+_Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-9'}).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](/infrastructure/node-operators/docker-compose/) section is more suited for docker users.
 
@@ -87,7 +87,7 @@ We'll need to set up a few configuration files and obtain the <DownloadFile file
 First, set some environment variables, which are used throughout initialization.
 
 ```sh title="env.sh"
-export CHAIN_ID=union-testnet-8
+export CHAIN_ID=union-testnet-9
 export MONIKER="Unionized Goblin"
 export KEY_NAME=alice
 export GENESIS_URL="https://union.build/genesis.json"
@@ -103,11 +103,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-8` replace `seeds = ""` with:
+For `union-testnet-9` replace `seeds = ""` with:
 
 <Code
   lang='toml'
-  code={`seeds = "${chainVersion({ chainId: 'union-testnet-8' }).seeds}"`} 
+  code={`seeds = "${chainVersion({ chainId: 'union-testnet-9' }).seeds}"`} 
 />
 
 

docs/src/content/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-8"`.
+For the Union Testnet, this value should be `"union-testnet-9"`.
 
 ```toml
 # The network chain ID
-chain-id = "union-testnet-8"
+chain-id = "union-testnet-9"
 ```
 
 ### Host/Port for the Tendermint RPC
@@ -144,11 +144,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-8, the seed nodes are:
+Seed nodes help orchestrate initial connections to the network. For union-testnet-9, the seed nodes are:
 
 <Code
   lang='toml'
-  code={`seeds = "${chainVersion({ chainId: 'union-testnet-8' }).seeds}"`} 
+  code={`seeds = "${chainVersion({ chainId: 'union-testnet-9' }).seeds}"`} 
 />
 
 

docs/src/content/docs/integrations/cometbft/opening-connection.mdx

@@ -221,7 +221,7 @@ You need to confirm that the connection is opened on both sides:
 
 ```bash frame="none"
 # Query the connection on Union
-uniond query ibc connection end $UNION_CONNECTION_ID --node https://rpc.testnet-8.union.build:443 	
+uniond query ibc connection end $UNION_CONNECTION_ID --node https://rpc.testnet-9.union.build:443 	
 
 # Query the connection on your chain
 $NODE_BIN query ibc connection end $YOUR_CONNECTION_ID --node $YOUR_RPC
@@ -254,7 +254,7 @@ Make sure the `state` of the channel is `OPEN` on both ends:
 
 ```bash frame="none"
 # Query the connection on Union
-uniond query ibc channel end $UCS01_PORT_ID $UNION_CHANNEL_ID --node https://rpc.testnet-8.union.build:443 	
+uniond query ibc channel end $UCS01_PORT_ID $UNION_CHANNEL_ID --node https://rpc.testnet-9.union.build:443 	
 
 # Query the connection on your chain
 $NODE_BIN query ibc channel end transfer $YOUR_CHANNEL_ID --node $YOUR_RPC

docs/src/content/docs/integrations/ucs01/cosmwasm/index.mdx

@@ -46,7 +46,7 @@ cd $HOME
 # determine your system architecture
 RELEASE="uniond-release-$(uname -m)-linux"
 # get the version we want to install
-VERSION="${chainVersion({chainId: 'union-testnet-8'}).current}"
+VERSION="${chainVersion({chainId: 'union-testnet-9'}).current}"
 
 curl --location \\
         https://github.com/unionlabs/union/releases/download/$VERSION/$RELEASE \\
@@ -248,7 +248,7 @@ pub fn execute_transfer(
 You will be using the same RPC url across examples, so good to export it to an environment variable:
 
 ```sh frame="none"
-export RPC_URL="https://rpc.testnet-8.union.build:443"
+export RPC_URL="https://rpc.testnet-9.union.build:443"
 ```
 
 ### Building the Contract
@@ -302,15 +302,15 @@ WALLET_ADDRESS=union1...
 To fund the wallet, we will use the faucet. You can find the faucet [here](https://app.union.build/faucet).
 
 ```sh title="Ensure the wallet is funded"
-curl https://rest.testnet-8.union.build/cosmos/bank/v1beta1/balances/$WALLET_ADDRESS | jq '.balances'[0]
+curl https://rest.testnet-9.union.build/cosmos/bank/v1beta1/balances/$WALLET_ADDRESS | jq '.balances'[0]
 ```
 
 ```sh title="Deploy the contract"
 $HOME/uniond tx wasm store ./build/contract.wasm \
     --from $WALLET_NAME \
     --gas auto \
     --gas-adjustment 1.4 \
-    --chain-id union-testnet-8 \
+    --chain-id union-testnet-9 \
     --keyring-backend test \
     --home /home/$USER/.union \
     --node $RPC_URL --yes
@@ -323,7 +323,7 @@ DEPLOY_TX_HASH=txhash-value-of-previous-command
 
 ... and use it to query the transaction to get the `code_id`:
 ```sh frame="none"
-$HOME/uniond query tx $DEPLOY_TX_HASH --node https://rpc.testnet-8.union.build:443 | rg -C 1 "code_id"
+$HOME/uniond query tx $DEPLOY_TX_HASH --node https://rpc.testnet-9.union.build:443 | rg -C 1 "code_id"
 ```
 
 Record the code-id:
@@ -341,7 +341,7 @@ $HOME/uniond \
     --from $WALLET_NAME \
     --gas auto \
     --gas-adjustment 1.4 \
-    --chain-id union-testnet-8 \
+    --chain-id union-testnet-9 \
     --keyring-backend test \
     --home /home/$USER/.union \
     --node $RPC_URL --yes
@@ -355,7 +355,7 @@ INSTANTIATE_TX_HASH=txhash-value-of-previous-command
 ... and use it to query the transaction to get the `_contract_address` (you'll see it twice):
 
 ```sh frame="none" 
-$HOME/uniond query tx $INSTANTIATE_TX_HASH --node https://rpc.testnet-8.union.build:443 | rg -C 1 "_contract_address"
+$HOME/uniond query tx $INSTANTIATE_TX_HASH --node https://rpc.testnet-9.union.build:443 | rg -C 1 "_contract_address"
 ```
 
 Record the contract address
@@ -392,7 +392,7 @@ $HOME/uniond \
         --from $WALLET_NAME \
         --gas auto \
         --gas-adjustment 1.4 \
-        --chain-id union-testnet-8 \
+        --chain-id union-testnet-9 \
         --keyring-backend test \
         --home /home/$USER/.union \
         --node $RPC_URL --amount 2muno

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

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

docs/src/content/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-8`.
+Welcome to the Union Testnet! This guide will instruct you on running a node and creating a validator for `union-testnet-9`.
 
 ## Steps
 
@@ -18,9 +18,7 @@ You may run the Union node on your own machine or a VPS, please ensure your mach
 
 To begin - you first need to obtain and run the client binary, `uniond`.
 
-Officially, **we only support running the binary as a Docker container**. You're free to extract and run the binary manually, but we won't be providing first class support for issues running `uniond` outside of the Docker images we provide.
-
-We offer two Docker images that are capable of running the client binary.
+We offer both Linux binaries and Docker images that are capable of running the client binary.
 
 #### Unionvisor
 
@@ -32,9 +30,9 @@ For more manual control, we also release each version of `uniond` as a Docker im
 
 ### Getting Testnet Tokens
 
-For validators who were chosen to be in the initial set of 64 validators, please see our [Getting Testnet Tokens](/joining-testnet/getting-tokens/) guide.
+Visit the Testnet Faucet to receive tokens to experiment with the Union Testnet.
 
-For others seeking to become validators, please stay tuned for more information. The best place to get the most recent information is [our Discord](https://discord.union.build).
+If you've been selected as a testnet validator and do not already have a token balance, please reach out in [our Discord](https://discord.union.build)
 
 :::note
 

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

@@ -9,10 +9,6 @@ import { chainVersion } from '#/lib/constants/versions.ts'
 import DownloadFile from "#/components/DownloadFile.astro";
 import FunctionResult from '#/components/FunctionResult.astro'
 
-Currently, we are only officially supporting running the Union Testnet binary (`uniond`) as a Docker container.
-
-It is possible to run the `uniond` binary outside of containers, however, we aren't directly supplying bare-metal binaries at this time.
-
 This guide assumes you have [Docker](https://www.docker.com/get-started/) correctly installed and configured on your system. We provide `uniond` images for Linux on both x86_64 (amd64) and aarch64 (arm64).
 
 ## Getting the Docker Image
@@ -23,7 +19,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-8'}).current} />_
+_Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-9'}).current} />_
 
 ## Running uniond
 
@@ -98,7 +94,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-8'}).current} />_
+_Where `UNIOND_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-9'}).current} />_
 
 This will enable you to issue `uniond` sub-commands with such as `uniond keys add` with ease.
 

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

@@ -14,15 +14,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-8` is `bundle-testnet-8`. You can obtain the Unionvisor bundle for `union-testnet-8` from our [GitHub Container Registry](https://github.com/orgs/unionlabs/packages/container/package/bundle-testnet-8).
+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-9` is `bundle-testnet-9`. You can obtain the Unionvisor bundle for `union-testnet-9` from our [GitHub Container Registry](https://github.com/orgs/unionlabs/packages/container/package/bundle-testnet-9).
 
 Alternatively, you can run the following command:
 
 ```sh frame="none"
-docker pull ghcr.io/unionlabs/bundle-testnet-8:$UNIONVISOR_VERSION
+docker pull ghcr.io/unionlabs/bundle-testnet-9:$UNIONVISOR_VERSION
 ```
 
-_Where `UNIONVISOR_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-8'}).current} />_
+_Where `UNIONVISOR_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-9'}).current} />_
 
 ## Running Unionvisor
 
@@ -54,10 +54,10 @@ To do this, we'll be using Docker volumes.
     docker run \\
       --volume ~/.unionvisor:/.unionvisor \\
       --volume /tmp:/tmp \\
-      -it ghcr.io/unionlabs/bundle-testnet-8:$UNIONVISOR_VERSION \\
+      -it ghcr.io/unionlabs/bundle-testnet-9:$UNIONVISOR_VERSION \\
       init --moniker $MONIKER \\
-      --network union-testnet-8 \\
-      --seeds "${chainVersion({chainId: 'union-testnet-8'}).seeds}"
+      --network union-testnet-9 \\
+      --seeds "${chainVersion({chainId: 'union-testnet-9'}).seeds}"
   `)}
 />
 _Where `MONIKER` is the preferred moniker you'd like to use on this node._
@@ -86,7 +86,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-8'}).current} />- uniond
+  - <FunctionResult result={chainVersion({chainId: 'union-testnet-9'}).current} />- uniond
 
 </FileTree>
 
@@ -122,7 +122,7 @@ You can use the `set-uniond-version` command as follows:
 docker run \
   --volume ~/.unionvisor:/.unionvisor \
   --volume /tmp:/tmp \
-  -it ghcr.io/unionlabs/bundle-testnet-8:$UNIONVISOR_VERSION \
+  -it ghcr.io/unionlabs/bundle-testnet-9:$UNIONVISOR_VERSION \
   set-uniond-version $UNIOND_VERSION
 ```
 *Where `UNIOND_VERSION` is the version of `uniond` used when the snapshot was generated*
@@ -135,10 +135,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-8:$UNIONVISOR_VERSION --log-level off call --'
+alias uniond='docker run -v ~/.unionvisor:/.unionvisor -v /tmp:/tmp --network host -it ghcr.io/unionlabs/bundle-testnet-9:$UNIONVISOR_VERSION --log-level off call --'
 ```
 
-_Where `UNIONVISOR_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-8'}).current} />_
+_Where `UNIONVISOR_VERSION` is <FunctionResult result={chainVersion({chainId: 'union-testnet-9'}).current} />_
 
 :::note
 
@@ -158,7 +158,7 @@ A minimal Docker Compose file for Unionvisor looks like this:
 ```yaml
 services:
   node:
-    image: ghcr.io/unionlabs/bundle-testnet-8:$UNIONVISOR_VERSION
+    image: ghcr.io/unionlabs/bundle-testnet-9:$UNIONVISOR_VERSION
     volumes:
       - ~/.unionvisor:/.unionvisor
       - /tmp:/tmp

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

@@ -8,27 +8,34 @@ import { Badge } from "@astrojs/starlight/components";
 
 Here you can find records of Union network binary upgrades.
 
-## union-testnet-4
+## union-testnet-9
+
+The network `union-testnet-9` has had no binary upgrades since its genesis.
+
+| Upgrade | Height  |
+| ------- | ------- |
+| v0.25.0 | genesis |
+
+## union-testnet-8
 
 <Badge text="Deprecated" variant="caution" />
 
-The network `union-testnet-4` had two binary upgrades since its genesis.
+The network `union-testnet-8` had one binary upgrade since its genesis.
 
 | Upgrade | Height  |
 | ------- | ------- |
-| v0.14.0 | genesis |
-| v0.15.0 | 236668  |
-| v0.17.0 | 631650  |
+| v0.21.0 | genesis |
+| v0.22.0 | 186500  |
 
-## union-testnet-5
+## union-testnet-7
 
 <Badge text="Deprecated" variant="caution" />
 
-The network `union-testnet-5` had no binary upgrades since its genesis.
+The network `union-testnet-7` had no binary upgrades since its genesis.
 
 | Upgrade | Height  |
 | ------- | ------- |
-| v0.18.0 | genesis |
+| v0.20.0 | genesis |
 
 ## union-testnet-6
 
@@ -40,23 +47,24 @@ The network `union-testnet-6` had no binary upgrades since its genesis.
 | ------- | ------- |
 | v0.19.0 | genesis |
 
-## union-testnet-7
+## union-testnet-5
 
 <Badge text="Deprecated" variant="caution" />
 
-The network `union-testnet-7` had no binary upgrades since its genesis.
+The network `union-testnet-5` had no binary upgrades since its genesis.
 
 | Upgrade | Height  |
 | ------- | ------- |
-| v0.20.0 | genesis |
+| v0.18.0 | genesis |
 
-## union-testnet-8
+## union-testnet-4
 
 <Badge text="Deprecated" variant="caution" />
 
-The network `union-testnet-8` had one binary upgrade since its genesis.
+The network `union-testnet-4` had two binary upgrades since its genesis.
 
 | Upgrade | Height  |
 | ------- | ------- |
-| v0.21.0 | genesis |
-| v0.22.0 | 186500  |
+| v0.14.0 | genesis |
+| v0.15.0 | 236668  |
+| v0.17.0 | 631650  |