Finished reviewing docusaurus/docs/protocol/upgrades/contigency_plans.md

docusaurus/docs/protocol/upgrades/contigency_plans.md

@@ -21,7 +21,7 @@ This document is intended to help you recover without significant downtime.
 - [Option 1: The migration didn't start (i.e. migration halt)](#option-1-the-migration-didnt-start-ie-migration-halt)
 - [Option 2: The migration is stuck (i.e. incomplete/partial migration)](#option-2-the-migration-is-stuck-ie-incompletepartial-migration)
 - [Option 3: The migration succeed but the network is stuck (i.e. migration had a bug)](#option-3-the-migration-succeed-but-the-network-is-stuck-ie-migration-had-a-bug)
-- [Documentation and scripts to update](#documentation-and-scripts-to-update)
+- [MANDATORY Checklist of Documentation \& Scripts to Update](#mandatory-checklist-of-documentation--scripts-to-update)
 
 ### Option 0: The bug is discovered before the upgrade height is reached
 
@@ -65,27 +65,36 @@ If the migration is stuck, there's always a chance the upgrade handler was execu
 In such a case, we need:
 
 - **All full nodes and validators**: Roll back validators to the backup
+
   - A snapshot is taken by `cosmovisor` automatically prior to upgrade when `UNSAFE_SKIP_BACKUP` is set to `false` (the default recommended value;
     [more information](https://docs.cosmos.network/main/build/tooling/cosmovisor#command-line-arguments-and-environment-variables))
+
 - **All full nodes and validators**: skip the upgrade
+
   - Add the `--unsafe-skip-upgrade=$upgradeHeightNumber` argument to `poktroll start` command like so:
+
     ```bash
     poktrolld start --unsafe-skip-upgrade=$upgradeHeightNumber # ... the rest of the arguments
     ```
+
+- **Protocol team**: Resolve the issue with an upgrade and schedule a new plan.
+
+  - The upgrade needs to be fixed, and then a new plan needs to be submitted to the network.
+
 - **Protocol team**: document the failed upgrade
-  - document and add `--unsafe-skip-upgrade=$upgradeHeightNumber` to the scripts (such as docker-compose and cosmovisor installer)
+
+  - Document and add `--unsafe-skip-upgrade=$upgradeHeightNumber` to the scripts (such as docker-compose and cosmovisor installer)
   - The next time somebody tries to sync the network from genesis they will automatically skip the failed upgrade; see [documentation and scripts to update](#documentation-and-scripts-to-update)
-- **Protocol team**: Resolve the issue with an upgrade and schedule a new plan.
 
 <!-- TODO_MAINNET(@okdas): new cosmovisor UX can simplify this -->
 
 ### Option 3: The migration succeed but the network is stuck (i.e. migration had a bug)
 
 This should be treated as a consensus or non-determinism bug that is unrelated to the upgrade. See [Recovery From Chain Halt](../../develop/developer_guide/recovery_from_chain_halt.md) for more information on how to handle such issues.
 
-### Documentation and scripts to update
+### MANDATORY Checklist of Documentation & Scripts to Update
 
-- The [upgrade list](./upgrade_list.md) should reflect a failed upgrade and provide a range of heights that served by each version.
-- Systemd service should include`--unsafe-skip-upgrade=$upgradeHeightNumber` argument in its start command [here](https://github.com/pokt-network/poktroll/blob/main/tools/installer/full-node.sh).
-- [Helm chart](https://github.com/pokt-network/helm-charts/blob/main/charts/poktrolld/templates/StatefulSet.yaml) (consider exposing via a `values.yaml` file)
-- [docker-compose](https://github.com/pokt-network/poktroll-docker-compose-example/tree/main/scripts) example
+- [ ] The [upgrade list](./upgrade_list.md) should reflect a failed upgrade and provide a range of heights that served by each version.
+- [ ] Systemd service should include`--unsafe-skip-upgrade=$upgradeHeightNumber` argument in its start command [here](https://github.com/pokt-network/poktroll/blob/main/tools/installer/full-node.sh).
+- [ ] The [Helm chart](https://github.com/pokt-network/helm-charts/blob/main/charts/poktrolld/templates/StatefulSet.yaml) should point to the latest version;consider exposing via a `values.yaml` file
+- [ ] The [docker-compose](https://github.com/pokt-network/poktroll-docker-compose-example/tree/main/scripts) examples should point to the latest version