diff --git a/README.md b/README.md index 8698716a..9340088a 100644 --- 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 index f47ff1f9..1b6324cd 100644 --- 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 deleted file mode 100644 index 59efe7a2..00000000 --- a/interchain-security/Testnet_Incentives_Program.md +++ /dev/null @@ -1,56 +0,0 @@ -# Testnet Incentive Program (TIP) - -Since November 2023, Hypha has worked with AADAO to give testnet validators the opportunity to earn ATOM for participating on the ICS testnet. This Testnets Incentives Program is meant to incentivize high quality validator performance on the ICS testnet on a per-month basis. - -The ICS testnet is **public**, meaning that anyone can join, run a validator, and learn about gaia node operations and new features on the Cosmos Hub. - -**However** – only active mainnet validators who run all Top N consumer chains are eligible for payments from TIP. - - -## Quick links -* Join the ICS testnet by following the instructions [here](VALIDATOR_JOINING_GUIDE.md) -* Register using the Google form [here](https://docs.google.com/forms/d/e/1FAIpQLSeXlXu89uyAgsfck0wpjtUVqaXWRzyJQwLMM-9dlJk9WIH3Zg/viewform) - * Resubmit this form if either your `provider` or `cosmoshub-4` keys change -* Stay tuned for Testnet Tuesday events by following our schedule [here](SCHEDULE.md) (and in Discord) -* Track validator participation using the Google sheet [here](https://docs.google.com/spreadsheets/d/1CR-gtLgHUXvP2Ww8KFqnOej7ma_GwDjNt8IhdTXbGGw/edit?gid=1605434271#gid=1605434271) - - -## How do I register? - -You can register by filling out our [Google form](https://forms.gle/G6VB3uc1KUa54ht39). You only need to register once (unless either your mainnet or testnet validator address change). - -In order for us to track your participation, we need to have an on-chain way to confirm that your mainnet validator and testnet validator are associated with one another (otherwise, some random person could claim to be a mainnet validator and claim the incentives)! - -We accept two ways of proving this: - -1. Memo: Using your **mainnet** validator wallet, send a trivial amount of ATOM to our multisig address (`cosmos1078gmgntta9qguve7c52dhxrs45xumjvcwrutd`). In the memo field, put the cosmovaloper address of your **testnet** validator. Do NOT put the address of your mainnet validator. -2. Email: Using the email in your mainnet validator’s security contact, email [project.cosmos@hypha.coop](mailto:project.cosmos@hypha.coop) and tell us the cosmovaloper address of your **testnet** validator . Reminder -- you can edit your security contact using the following command: `gaiad tx staking edit-validator --security-contact --from ` - -⚠️ If either your mainnet or testnet address changes (due to tombstoning, for example), you **must** notify us to remain eligible. Your key is your identity – we can’t process changes in identity without hearing from you! - - -## What are the criteria for getting paid? -Each period, we evaluate the following three criteria: -* **Criteria 1:** Be an active mainnet validator. Submit proof via our Google form -* **Criteria 2.1:** Validate all available Top N consumer chains secured by the Cosmos Hub (Neutron and Stride) with > 50% uptime. -* **Criteria 2.2:** Use *assigned consumer keys* for all available Top N consumer chains (i.e., do not reuse your Hub key). -* **Criteria 3:** Run a testnet infrastructure setup that closely mimics mainnet. - -If you meet these three criteria (most testnet validators do), you can participate in testnet events and earn points. At the end of each period, we'll translate those points into USDC and pay you for your testnet work! There are even bonus points for completing all events perfectly and remaining unjailed. - -Validators can typically track all criteria except for **participation** using their own monitoring and awareness of their options. We publish results for **participation** in this public [Google Sheet](https://docs.google.com/spreadsheets/d/1CR-gtLgHUXvP2Ww8KFqnOej7ma_GwDjNt8IhdTXbGGw/edit?gid=1605434271#gid=1605434271) throughout the period and erase it at the end of a period after payments have been made. - - -## Do you ever make exceptions? - -We occasionally make exceptions for an entire event for **jailing** and ** perfect participation** depending on how the testnet is behaving. -* Exceptions for **participation** mean we will remove an event and not count it at all. This sometimes happens if we give incorrect instructions or fail to announce an event with enough lead time. -* Exceptions for **jailing** occur when there’s a widespread event that impacts many validators. For example, if a bug is discovered during an upgrade and it leads to many validators being jailed, we might make an exception and not count that jailing incident for the period. - -We also sometimes make exceptions for: -* **Intentional experimentation communicated in advance.** For example: trying to double sign and getting tombstoned for it, trying a new cosmovisor setting and missing a 5 block signing window because it doesn’t work. -* **Quick diagnosis and resolution of issues**, possibly involving submitting logs for debugging. For example, being jailed due to a faulty snapshot, informing the snapshot provider, unjailing, and emailing [project.cosmos@hypha.coop](mailto:project.cosmos@hypha.coop) within 24 hours (~15,000 blocks) of being jailed to explain the situation. - -‼️ In order to process an exception, you **must** contact us in advance or within 24 hours. ‼️ - -Once a period is completed and payments have been made, there will be no changes made retroactively. 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 deleted file mode 100644 index 0e7ebf59..00000000 --- a/interchain-security/provider/upgrade-v9.0.3-to-v9.1.0.md +++ /dev/null @@ -1,48 +0,0 @@ -# Upgrading provider chain from Gaia v9.0.3 to v9.1.0 - -We will be upgrading the provider chain on **Wednesday, May 17 2023**. This upgrade has already been applied on mainnet as an emergency upgrade. - -* Block height: 1534600 -* Golang version: 1.18.x - -## ❗Halt height settings - -As the upgrade is a non-governance upgrade, the halt height needs to be manually set. You can do this one of the following ways, see here for more information. You must: - -Set the halt-height configuration parameter in your config/app.toml -**Or** pass the --halt-height flag to gaiad with the block height specified - -#### Option 1: Modify app.toml - -App.toml example: - -If you use this method, you MUST restart the node for the halt-height to be activated. - -halt and shutdown that can be used to assist upgrades and testing. -``` -halt-height = 1534600 -``` - -#### Option 2: gaiad start - -Gaiad start example: - -``` -gaiad start --halt-height 1534600 -``` -## ❗Avoiding double signing errors - -To avoid the potential for double signing, make sure that you backup your `priv_validator_state.json` file and make sure that you are using the same file if moving machines etc. We recommend that you do not switch machines during this process. Instead, go down at the halt height, and come back up afterward on the same machine with the same data-dir using the new binary. - -Do NOT start multiple machines with the same `priv_validator_state.json`, your validator will be tombstoned and you will be slashed. -Do NOT use unsafe-reset-all, as that will destroy your `priv_validator_state.json` file. - -## ❗Dealing with stuck nodes - -Do NOT restart your node, it might take some time to reach consensus. Monitor the `#replicated-security` channel for more information/instructions as the upgrade progresses. - -Support - -Please don’t hesitate to ask for help. Key to doing this well, is for as many validators as possible to halt at the same time. We’re on standby to help with the halt height setup. - -Before the time of the upgrade, please monitor the Interchain Security `#announcements` channel on Cosmos Discord, and be sure to be in`#replicated-security` channel where you can get support for the upgrade. diff --git a/interchain-security/provider/README.md b/provider/README.md similarity index 98% rename from interchain-security/provider/README.md rename to provider/README.md index 1945b929..730b46ce 100644 --- a/interchain-security/provider/README.md +++ b/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 b/provider/SCHEDULE.md similarity index 99% rename from interchain-security/SCHEDULE.md rename to provider/SCHEDULE.md index 95ddb48d..24c3dabe 100644 --- a/interchain-security/SCHEDULE.md +++ b/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 b/provider/UPGRADE_GUIDE.md similarity index 100% rename from interchain-security/UPGRADE_GUIDE.md rename to provider/UPGRADE_GUIDE.md diff --git a/interchain-security/VALIDATOR_JOINING_GUIDE.md b/provider/VALIDATOR_JOINING_GUIDE.md similarity index 91% rename from interchain-security/VALIDATOR_JOINING_GUIDE.md rename to provider/VALIDATOR_JOINING_GUIDE.md index 02ea30cd..de24000d 100644 --- a/interchain-security/VALIDATOR_JOINING_GUIDE.md +++ b/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/interchain-security/provider/join-ics-provider-cv.sh b/provider/join-provider-cv.sh similarity index 100% rename from interchain-security/provider/join-ics-provider-cv.sh rename to provider/join-provider-cv.sh diff --git a/interchain-security/provider/join-ics-provider.sh b/provider/join-provider.sh similarity index 100% rename from interchain-security/provider/join-ics-provider.sh rename to provider/join-provider.sh diff --git a/interchain-security/provider/provider-genesis.json b/provider/provider-genesis.json similarity index 100% rename from interchain-security/provider/provider-genesis.json rename to provider/provider-genesis.json diff --git a/scripts/bigbang-setup.sh b/scripts/bigbang-setup.sh deleted file mode 100755 index 4b6870a3..00000000 --- a/scripts/bigbang-setup.sh +++ /dev/null @@ -1,96 +0,0 @@ -#!/bin/bash - -command_exists () { - type "$1" &> /dev/null ; -} - -if command_exists go ; then - echo "Golang is already installed" -else - echo "Install dependencies" - sudo apt update - sudo apt install build-essential jq -y - - wget https://dl.google.com/go/go1.15.5.linux-amd64.tar.gz - tar -xvf go1.15.5.linux-amd64.tar.gz - sudo mv go /usr/local - - echo "" >> ~/.bashrc - echo 'export GOPATH=$HOME/go' >> ~/.bashrc - echo 'export GOROOT=/usr/local/go' >> ~/.bashrc - echo 'export GOBIN=$GOPATH/bin' >> ~/.bashrc - echo 'export PATH=$PATH:/usr/local/go/bin:$GOBIN' >> ~/.bashrc - - #source ~/.bashrc - . ~/.bashrc - - -fi - -echo "-- Stopping any previous system service of akashd" - -sudo systemctl stop akashd - -akashd unsafe-reset-all - -echo "-- Clear old akash data and install akashd and setup the node --" - -rm -rf $GOBIN/akashctl -rm -rf $GOBIN/akashd -rm -rf ~/.akashd -rm -rf ~/.akashctl -rm -rf ~/akash - -YOUR_KEY_NAME=$1 -YOUR_NAME=$2 -DAEMON=akashd -DENOM=uakt -CHAIN_ID=bigbang-3 -PERSISTENT_PEERS="6205fb3c05d0dccb5451507112601af454f4d059@104.131.69.13:26656" - -echo "installing akashd" -git clone https://github.com/ovrclk/akash.git -cd akash -git fetch -git checkout bigbang -make install - -echo "Creating keys" -$DAEMON keys add $YOUR_KEY_NAME - -echo "Setting up your validator" -$DAEMON init $YOUR_NAME --chain-id $CHAIN_ID -curl http://104.131.69.13:26657/genesis | jq .result.genesis > ~/.$DAEMON/config/genesis.json - -echo "----------Setting config for seed node---------" -sed -i 's#tcp://127.0.0.1:26657#tcp://0.0.0.0:26657#g' ~/.$DAEMON/config/config.toml -sed -i '/persistent_peers =/c\persistent_peers = "'"$PERSISTENT_PEERS"'"' ~/.$DAEMON/config/config.toml - - -echo "---------Creating system file---------" - -echo "[Unit] -Description=Akashd daemon -After=network-online.target -[Service] -User=${USER} -ExecStart=${GOBIN}/$DAEMON start -Restart=always -RestartSec=3 -LimitNOFILE=4096 -[Install] -WantedBy=multi-user.target -" > akashd.service - -sudo mv akashd.service /etc/systemd/system/akashd.service -sudo systemctl daemon-reload -sudo systemctl start akashd - -echo -echo "Your account address is :" -$DAEMON keys show $YOUR_KEY_NAME -a -echo "Your node setup is done. You would need some tokens to start your validator. You can get some tokens from the faucet: https://faucet.bigbang.vitwit.com" -echo -echo -echo "After receiving tokens, you can create your validator by running" -echo "$DAEMON tx staking create-validator --amount 90000000$DENOM --commission-max-change-rate \"0.1\" --commission-max-rate \"0.20\" --commission-rate \"0.1\" --details \"Some details about yourvalidator\" --from $YOUR_KEY_NAME --pubkey=\"$($DAEMON tendermint show-validator)\" --moniker $YOUR_NAME --min-self-delegation \"1\" --chain-id $CHAIN_ID" diff --git a/scripts/check-gentx-amount.sh b/scripts/check-gentx-amount.sh deleted file mode 100755 index e72bd6da..00000000 --- a/scripts/check-gentx-amount.sh +++ /dev/null @@ -1,38 +0,0 @@ -#!/bin/bash - -set -eo pipefail - -path="$1" - -declare -i maxbond=1000000000 - -extraquery='[.value.msg[]| select(.type != "cosmos-sdk/MsgCreateValidator")]|length' - -gentxquery='.value.msg[]| select(.type == "cosmos-sdk/MsgCreateValidator")|.value.value' - -denomquery="[$gentxquery | select(.denom != \"star\")] | length" - -amountquery="$gentxquery | .amount" - -# only allow MsgCreateValidator transactions. -if [ "$(jq "$extraquery" "$path")" != "0" ]; then - echo "spurious transactions" - exit 1 -fi - -# only allow "star" tokens to be bonded -if [ "$(jq "$denomquery" "$path")" != "0" ]; then - echo "invalid denomination" - exit 1 -fi - -# limit the amount that can be bonded -for amount in "$(jq -rM "$amountquery" "$path")"; do - declare -i amt="$amount" - if [ $amt -gt $maxbond ]; then - echo "bonded too much: $amt > $maxbond" - exit 1 - fi -done - -exit 0 \ No newline at end of file diff --git a/scripts/generate-genesis.sh b/scripts/generate-genesis.sh deleted file mode 100755 index 0ea96b2d..00000000 --- a/scripts/generate-genesis.sh +++ /dev/null @@ -1,33 +0,0 @@ -#!/bin/bash - -NETWORK=bigbang-1 -DAEMON=akashd -HOME_DIR=~/.akashd -CONFIG=~/.akashd/config -TOKEN_DENOM=star -FAUCET_ACCOUNTS=("akash1czxh6ewhuy00tsv5zu50gz7lz2cxcpufdrarty" "akash1qjcvelu4rud75jztawcls48luxmapcajvfdhuy") - -rm -rf $HOME_DIR - -$DAEMON init $NETWORK --chain-id $NETWORK - -rm -rf $CONFIG/gentx && mkdir $CONFIG/gentx - -sed -i "s/\"stake\"/\"$TOKEN_DENOM\"/g" $HOME_DIR/config/genesis.json - -for i in $NETWORK/gentx/*.json; do - echo $i - $DAEMON add-genesis-account $(jq -r '.value.msg[0].value.delegator_address' $i) 1000000000$TOKEN_DENOM - cp $i $CONFIG/gentx/ -done - -for addr in "${FAUCET_ACCOUNTS[@]}"; do - echo "Adding faucet addr: $addr" - $DAEMON add-genesis-account $addr 100000000000$TOKEN_DENOM -done - -$DAEMON collect-gentxs - -$DAEMON validate-genesis - -cp $CONFIG/genesis.json $NETWORK \ No newline at end of file diff --git a/scripts/verify-gentx.sh b/scripts/verify-gentx.sh deleted file mode 100755 index 12cbf062..00000000 --- a/scripts/verify-gentx.sh +++ /dev/null @@ -1,73 +0,0 @@ -#!/bin/sh -DAEMON_HOME="/tmp/app$(date +%s)" -CLI_HOME="/tmp/appcli$(date +%s)" -DAEMON=akashd -CLI=akashctl -DENOM=star -RANDOM_KEY="randomvalidatorkeyxx" -CHAIN_ID=bigbang-1 - -GENTX_FILE=$(ls $CHAIN_ID/gentx | head -1) -LEN_GENTX=$(echo ${#GENTX_FILE}) - -GENTX_DEADLINE=$(date -d '2020-10-19 15:00:00' '+%d/%m/%Y %H:%M:%S'); -now=$(date +"%d/%m/%Y %H:%M:%S") - -# if [ $GENTX_DEADLINE < $now ]; then -# echo 'Gentx submission is closed' -# el -if [ $LEN_GENTX -eq 0 ]; then - echo "No new gentx file found." -else - set -e - - ./scripts/check-gentx-amount.sh "./$CHAIN_ID/gentx/$GENTX_FILE" || exit 1 - - echo "...........Install & Init Chain.............." - curl -L https://github.com/ovrclk/akash/releases/download/v0.8.1/akash_0.8.1_linux_amd64.zip -o akash_linux.zip && unzip akash_linux.zip - rm akash_linux.zip - cd akash_0.8.1_linux_amd64 - - echo "12345678" | ./$CLI keys add $RANDOM_KEY --keyring-backend test --home $CLI_HOME - - ./$DAEMON init --chain-id $CHAIN_ID dummyvalidator --home $DAEMON_HOME -o - - echo "..........Fetching genesis......." - rm -rf $DAEMON_HOME/config/genesis.json - curl -s https://raw.githubusercontent.com/cosmos/testnets/master/$CHAIN_ID/genesis.json > $DAEMON_HOME/config/genesis.json - - sed -i '/genesis_time/c\ \"genesis_time\" : \"2020-09-20T00:00:00Z\",' $DAEMON_HOME/config/genesis.json - - GENACC=$(cat ../$CHAIN_ID/gentx/$GENTX_FILE | sed -n 's|.*"delegator_address":"\([^"]*\)".*|\1|p') - - echo $GENACC - - echo "12345678" | ./$DAEMON add-genesis-account $RANDOM_KEY 1000000000000$DENOM --home $DAEMON_HOME \ - --keyring-backend test --home-client $CLI_HOME - ./$DAEMON add-genesis-account $GENACC 1000000000$DENOM --home $DAEMON_HOME - - echo "12345678" | ./$DAEMON gentx --name $RANDOM_KEY --amount 900000000000$DENOM --home $DAEMON_HOME \ - --keyring-backend test --home-client $CLI_HOME - cp ../$CHAIN_ID/gentx/$GENTX_FILE $DAEMON_HOME/config/gentx/ - - echo "..........Collecting gentxs......." - ./$DAEMON collect-gentxs --home $DAEMON_HOME - sed -i '/persistent_peers =/c\persistent_peers = ""' $DAEMON_HOME/config/config.toml - - ./$DAEMON validate-genesis --home $DAEMON_HOME - - echo "..........Starting node......." - ./$DAEMON start --home $DAEMON_HOME & - - sleep 5s - - echo "...checking network status.." - - ./$CLI status --chain-id $CHAIN_ID --node http://localhost:26657 - - sleep 5s - - echo "...Cleaning the stuff..." - killall $DAEMON >/dev/null 2>&1 - rm -rf $DAEMON_HOME >/dev/null 2>&1 -fi diff --git a/interchain-security/Testnet_Tuesdays.md b/testnet-tuesdays/README.md similarity index 100% rename from interchain-security/Testnet_Tuesdays.md rename to testnet-tuesdays/README.md