cosmos · dasanchez · Nov 12, 2025
diff --git a/README.md b/README.md
@@ -12,18 +12,15 @@ The goals of the Cosmos Hub testnet program are to:
 
 These goals are supported by a persistent testnet using similar, if not identical, parameters to the Cosmos Hub.
 
-### [Interchain Security Persistent Testnet](interchain-security/)
+### [Cosmos Hub Testnet](provider/)
 
-The Interchain Security testnet provides a public platform to explore:
-- Launching and stopping consumer chains
-- Interchain Security features
-- Relayer operations
-- Integrations (block explorers, monitors, etc.)
+The Cosmos Hub testnet (`provider`) provides a public platform to test and demonstrate Gaia features, explore relayer operations, and support the development work of integrations (block explorers, monitoring suites, etc.).
 
 We have configured this testnet so that:
 * Testnet coordinators operate 3+ validators with a combined voting power exceeding 66% total power.
 * Testnet coordinators control a faucet with >100M liquid tokens.
 
+The `provider` testnet is the primary network for [Testnet Tuesday](/testnet-tuesdays/README.md) events.
 
 ### [Local Testnet](local/)
 

diff --git a/RELEASE_TESTING_PROCESS.md b/RELEASE_TESTING_PROCESS.md
@@ -1,9 +1,6 @@
 # Release Testing
 
-This section provides:
-
-* A summary of the process used by Hypha to qualify upcoming Gaia versions as mainnet-ready.
-* A record of testing results for major Gaia upgrades.
+This page provides a summary of the process used by Hypha to qualify upcoming Gaia versions as mainnet-ready.
 
 ## Release Testing Process
 
@@ -22,33 +19,15 @@ The release testing process can be split into three phases for each major releas
 GitHub Actions workflows are used to run baseline and version-specific tests for each major upgrade.
 
 * **Pass criteria:** All test workflows for a given version run successfully.
-* **Output:** Test report and logs.
 
 ### Testnet upgrades
 
 Testnet upgrades are scheduled once a release candidate has passed all tests and is identified as having a 90% chance of reaching the Cosmos Hub as-is by the Gaia integration team. Testnet upgrades are done through governance proposals.
 
-The Release testnet (`theta-testnet-001`) is upgraded to the release candidate first; after it is confirmed as successful, the Interchain Security testnet (`provider`) is upgraded next.
+The Cosmos Hub testnet (`provider`) is upgraded to the release candidate; after it is confirmed as successful, the release candidate is qualified as mainnet-ready.
 
-Validators participating in the testnets will be given advance notice that a software upgrade is happening via Discord, at least three days in advance, so they can prepare their nodes accordingly. This repo will be updated with the relevant information so anyone willing to participate in the upgrade can join the testnet ahead of time.
+Validators participating in the Cosmos Hub testnet will be given advance notice that a software upgrade is happening via Discord, at least three days in advance, so they can prepare their nodes accordingly. This repo will be updated with the relevant information so anyone willing to participate in the upgrade can join the testnet ahead of time.
 
 * **Pass criteria:** Blocks are produced with new version after the upgrade height is reached with no indication of unexpected behaviour.
   * Depending on the features included in a specific version, additional checks may be run on the testnet after the upgrade takes place to qualify the release candidate as ready for mainnet.
-* **Output:** Upgrade summary.
-
-## Test Results
-
-### Gaia v17
-
-* [Automated testing report](https://github.com/hyphacoop/cosmos-release-testing/blob/main/test-results/gaia-v17/automated-tests.md)
-* [Testnet upgrades](https://github.com/hyphacoop/cosmos-release-testing/blob/main/test-results/gaia-v17/testnet-upgrades.md)
-
-### Gaia v16
-
-* [Automated testing report](https://github.com/hyphacoop/cosmos-release-testing/blob/main/test-results/gaia-v16/automated-tests.md)
-* [Testnet upgrades](https://github.com/hyphacoop/cosmos-release-testing/blob/main/test-results/gaia-v16/testnet-upgrades.md)
-
-### Gaia v15
 
-* [Automated testing report](https://github.com/hyphacoop/cosmos-release-testing/blob/main/test-results/gaia-v15/automated-tests.md)
-* [Testnet upgrades](https://github.com/hyphacoop/cosmos-release-testing/blob/main/test-results/gaia-v15/testnet-upgrades.md)
diff --git a/interchain-security/Testnet_Incentives_Program.md b/interchain-security/Testnet_Incentives_Program.md
diff --git a/interchain-security/provider/upgrade-v9.0.3-to-v9.1.0.md b/interchain-security/provider/upgrade-v9.0.3-to-v9.1.0.md
diff --git a/interchain-security/provider/README.md → provider/README.md b/interchain-security/provider/README.md → provider/README.md
@@ -1,7 +1,7 @@
 
 # `provider` Chain Details
 
-The provider chain functions as an analogue of the Cosmos Hub. Its governance parameters will provide short voting periods to accelerate the creation of consumer chains.
+The provider chain functions as an analogue of the Cosmos Hub. Its governance parameters provide short voting periods to accelerate upgrades, parameter changes, and recovery of IBC clients.
 
 * **Chain-ID**: `provider`
 * **denom**: `uatom`
@@ -98,8 +98,8 @@ You can choose to (not) use state sync. Your node will sync much faster if you u
 ### Bash Script
 
 Run either one of the scripts provided in this repo to join the provider chain:
-* `join-ics-provider.sh` will create a `gaiad` service.
-* `join-ics-provider-cv.sh` will create a `cosmovisor` service.
+* `join-provider.sh` will create a `gaiad` service.
+* `join-provider-cv.sh` will create a `cosmovisor` service.
 * Both scripts must be run either as root or from a sudoer account.
 * Both scripts will attempt to build a binary from the [cosmos/gaia](https://github.com/cosmos/gaia/releases) repo.
 * To sync with Hypha's `provider` snapshot run with the `-s` argument

diff --git a/interchain-security/SCHEDULE.md → provider/SCHEDULE.md b/interchain-security/SCHEDULE.md → provider/SCHEDULE.md
@@ -1,4 +1,4 @@
-## Interchain Security Testnet Schedule
+## Cosmos Hub Testnet Schedule
 
 | Date                   | Testnet Incentives Program Period | Type                       | Description                                                                                                                                              |
 | ---------------------- | --------------------------------- | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |

diff --git a/interchain-security/UPGRADE_GUIDE.md → provider/UPGRADE_GUIDE.md b/interchain-security/UPGRADE_GUIDE.md → provider/UPGRADE_GUIDE.md
diff --git a/...chain-security/VALIDATOR_JOINING_GUIDE.md → provider/VALIDATOR_JOINING_GUIDE.md b/...chain-security/VALIDATOR_JOINING_GUIDE.md → provider/VALIDATOR_JOINING_GUIDE.md
@@ -1,14 +1,13 @@
 # Validator Joining Process
 
-This guide is intended for validators that are looking to join the Interchain Security testnet.
+This guide is intended for validators that are looking to join the Cosmos Hub (`provider`) testnet.
 
 ## Joining the Provider Chain
 
-To join the Interchain Security testnet as a validator, you will have to run a binary for the provider chain as well as all live consumer chains.
+To join the Cosmos Hub testnet as a validator, you will have to run a binary for the provider chain as well as all live consumer chains.
 
-1. [Join the provider chain](https://github.com/cosmos/testnets/tree/master/interchain-security/provider#how-to-join).
-1. Request funds from the provider chain [faucet](https://faucet.polypore.xyz).
-1. Join all the live consumer chains currently listed in the [status section](https://github.com/cosmos/testnets/tree/master/interchain-security#status).
+1. [Join the provider chain](README.md#how-to-join)
+2. Request funds from the provider chain [faucet](https://faucet.polypore.xyz).
 
 ## Creating a Validator on the Provider Chain
 
@@ -48,7 +47,7 @@ validator.json \
 --gas-prices 0.005uatom
 ```
 
-4. You can verify the validator was created in the [block explorer](https://explorer.rs-testnet.polypore.xyz/provider/staking), or in the command line:
+1. You can verify the validator was created in the [block explorer](https://explorer.polypore.xyz/provider/staking), or in the command line:
 
 ```
 gaiad q staking validators -o json | jq '.validators[].description.moniker'

diff --git a/...security/provider/join-ics-provider-cv.sh → provider/join-provider-cv.sh b/...security/provider/join-ics-provider-cv.sh → provider/join-provider-cv.sh
diff --git a/...in-security/provider/join-ics-provider.sh → provider/join-provider.sh b/...in-security/provider/join-ics-provider.sh → provider/join-provider.sh
diff --git a/...n-security/provider/provider-genesis.json → provider/provider-genesis.json b/...n-security/provider/provider-genesis.json → provider/provider-genesis.json
diff --git a/scripts/bigbang-setup.sh b/scripts/bigbang-setup.sh
diff --git a/scripts/check-gentx-amount.sh b/scripts/check-gentx-amount.sh