Shutdown blobber/validator using cli

Steps to shutdown blobber/validator using zboxcli.

Blobber/Validator can be only shutdown from the network using there delegate wallet.

Steps to regenerate delegate wallet for the blobber that got deployed via chimney webapp.

Create a blobber delegate wallet file in json format with the name blob_wallet.json as given below:

{
    "client_id": "Your_Wallet_Address",
    "client_key": "Your_Public_Key",
    "keys": [
        {
            "public_key": "Your_Public_Key",
            "private_key": "Your_Private_Key"
        }
    ],
    "mnemonics": "Your_Mneumonic",
    "version": "1.0",
    "date_created": "2023-05-01T18:40:02Z",
    "nonce": 0
}

To get the information that needs to replaced into above wallet template login into the chimney.software account. Navigate to Settings -> Wallet. Here you will get your Your_Wallet_Address, Your_Public_Key, Your_Private_Key & Your_Mneumonic. Kindly replace them into above wallet template and save the wallet to the home directory with the name del_wallet.json of your local system / server.

Generate zbox binary on your local system / server.

1. Install make , go if it is not present on your system.

   • Run command to install `make` and `wget`.

     sudo apt install make wget -y

   • Follow link to install go.

2. Clone the zboxcli repo.

   git clone https://github.com/0chain/zboxcli.git
   cd zboxcli
   make install
   mv zbox ~/

3. Create config.yaml file in the same directory where your del_wallet.json is present.

   cd ~/
   echo "Generating config.yaml file"
   echo "block_worker: https://mainnet.zus.network/dns" > config.yaml
   echo "signature_scheme: bls0chain" >> config.yaml
   echo "min_submit: 20" >> config.yaml
   echo "min_confirmation: 5" >> config.yaml
   echo "confirmation_chain_length: 3" >> config.yaml
   echo "max_txn_query: 5" >> config.yaml
   echo "query_sleep_time: 5" >> config.yaml

Run below commands to shutdown blobber and validator.

1. Run below command to shutdown blobber.

   ./zbox shutdown-blobber --id <blobber_id> --wallet del_wallet.json --configDir . --config ./config.yaml

2. Run below command to shutdown validator.

   ./zbox shutdown-validator --id <validator_id> --wallet del_wallet.json --configDir . --config ./config.yaml

Effects on blobber/validator shutdown/killed.

When a blobber is shutdown:

1. You won't get new rewards but can collect existing rewards.

2. Stake is slashed by 50% for both blobber & validator.

3. Data remains on the servers and could be accessible by client unless the server is turned off.

4. Blobber and validator do not receive challenges.

When a blobber is killed:

1. You won't get new rewards but can collect existing rewards.

2. Stake is slashed by 25% for both blobber & validator.

3. When blobber is dysfunctional, if there are enough blobbers to recover, everything will work, client can replace broken blobber and call repair. But if there are not enough blobbers to recover, data will be lost (when number of killed blobbers are more than parity shards).

4. Blobber and validator do not receive challenges.