chore: update summary

Author: bangjelkoski

.gitbook/SUMMARY.md

@@ -60,14 +60,77 @@
 * [Modules](developers/modules/README.md)
   * [Injective](developers/modules/injective/README.md)
     * [Auction](developers/modules/injective/auction/README.md)
+      * [State](developers/modules/injective/auction/01_state.md)
+      * [Messages](developers/modules/injective/auction/02_messages.md)
+      * [EndBlock](developers/modules/injective/auction/03_end_block.md)
+      * [Events](developers/modules/injective/auction/04_events.md)
+      * [Params](developers/modules/injective/auction/05_params.md)
     * [Exchange](developers/modules/injective/exchange/README.md)
+      * [Derivative Markets Concepts](developers/modules/injective/exchange/00_derivative_market_concepts.md)
+      * [Spot Markets Concepts](developers/modules/injective/exchange/01_spot_market_concepts.md)
+      * [Binary Option Markets Concepts](developers/modules/injective/exchange/02_binary_options_markets.md)
+      * [Other Concepts](developers/modules/injective/exchange/02_other_concepts.md)
+      * [State](developers/modules/injective/exchange/03_state.md)
+      * [State Transitions](developers/modules/injective/exchange/04_state_transitions.md)
+      * [Messages](developers/modules/injective/exchange/05_messages.md)
+      * [Proposals](developers/modules/injective/exchange/06_proposals.md)
+      * [BeginBlock](developers/modules/injective/exchange/07_begin_block.md)
+      * [EndBlock](developers/modules/injective/exchange/08_end_block.md)
+      * [Events](developers/modules/injective/exchange/09_events.md)
+      * [Params](developers/modules/injective/exchange/10_params.md)
+      * [MsgPrivilegedExecuteContract](developers/modules/injective/exchange/11_msg_privileged_execute_contract.md)
+      * [Improvements](developers/modules/injective/exchange/07_future_improvements.md)
     * [Insurance](developers/modules/injective/insurance/README.md)
+      * [State](developers/modules/injective/insurance/01_state.md)
+      * [State Transitions](developers/modules/injective/insurance/02_state_transition.md)
+      * [Messages](developers/modules/injective/insurance/03_messages.md)
+      * [EndBlock](developers/modules/injective/insurance/04_end_block.md)
+      * [Events](developers/modules/injective/insurance/05_events.md)
+      * [Params](developers/modules/injective/insurance/06_params.md)
+      * [Improvements](developers/modules/injective/insurance/07_future_improvements.md)
     * [OCR](developers/modules/injective/ocr/README.md)
+      * [Concepts](developers/modules/injective/ocr/01_concepts.md)
+      * [State](developers/modules/injective/ocr/02_state.md)
+      * [Messages](developers/modules/injective/ocr/03_messages.md)
+      * [Proposals](developers/modules/injective/ocr/04_proposals.md)
+      * [BeginBlock](developers/modules/injective/ocr/05_begin_block.md)
+      * [Hooks](developers/modules/injective/ocr/06_hooks.md)
+      * [Events](developers/modules/injective/ocr/07_hooks.md)
+      * [Params](developers/modules/injective/ocr/08_params.md)
     * [Oracle](developers/modules/injective/oracle/README.md)
+      * [State](developers/modules/injective/oracle/01_state.md)
+      * [Keeper](developers/modules/injective/oracle/02_keeper.md)
+      * [Messages](developers/modules/injective/oracle/03_messages.md)
+      * [Proposals](developers/modules/injective/oracle/04_proposals.md)
+      * [Events](developers/modules/injective/oracle/05_events.md)
+      * [Improvements](developers/modules/injective/oracle/06_future_improvements.md)
     * [Peggy](developers/modules/injective/peggy/README.md)
+      * [Definitions](developers/modules/injective/peggy/01_definitions.md)
+      * [Workflow](developers/modules/injective/peggy/02_workflow.md)
+      * [State](developers/modules/injective/peggy/03_state.md)
+      * [Messages](developers/modules/injective/peggy/04_messages.md)
+      * [Slashing](developers/modules/injective/peggy/05_slashing.md)
+      * [EndBlock](developers/modules/injective/peggy/06_end_block.md)
+      * [Events](developers/modules/injective/peggy/07_events.md)
+      * [Params](developers/modules/injective/peggy/08_params.md)
+      * [Relay Semantics](developers/modules/injective/peggy/09_relay_semantics.md)
+      * [Improvements](developers/modules/injective/peggy/10_future_improvements.md)
     * [Permissions](developers/modules/injective/permissions/README.md)
+      * [Concepts](developers/modules/injective/permissions/01_concepts.md)
+      * [State](developers/modules/injective/permissions/02_state.md)
+      * [State Transition](developers/modules/injective/permissions/03_state_transitions.md)
     * [TokenFactory](developers/modules/injective/tokenfactory/README.md)
+      * [Concepts](developers/modules/injective/tokenfactory/01_concepts.md)
+      * [State](developers/modules/injective/tokenfactory/02_state.md)
+      * [Messages](developers/modules/injective/tokenfactory/03_messages.md)
+      * [Events](developers/modules/injective/tokenfactory/04_events.md)
+      * [Params](developers/modules/injective/tokenfactory/05_params.md)
     * [WasmX](developers/modules/injective/wasmx/README.md)
+      * [Concepts](developers/modules/injective/wasmx/01_concepts.md)
+      * [Data](developers/modules/injective/wasmx/02_data.md)
+      * [Proposals](developers/modules/injective/wasmx/03_proposals.md)
+      * [Messages](developers/modules/injective/wasmx/04_messages.md)
+      * [Params](developers/modules/injective/wasmx/05_params.md)
   * [Core](developers/modules/core/README.md)
     * [Auth](developers/modules/core/auth/README.md)
     * [AuthZ](developers/modules/core/authz/README.md)
@@ -100,7 +163,23 @@
 * [Validators](nodes/validators/README.md)
   * [Mainnet](nodes/validators/mainnet/README.md)
     * [Peggo](nodes/validators/mainnet/peggo.md)
-    * [Canonical Chain Upgrades](nodes/validators/mainnet/canonical-chain-upgrades.md)
+    * [Canonical Chain Upgrades](nodes/validators/mainnet/canonical-chain-upgrades/README.md)
+      * [Upgrade to 10002-rc1](nodes/validators/mainnet/canonical-chain-upgrades/canonical-10002-rc1.md)
+      * [Upgrade to 10002-rc2](nodes/validators/mainnet/canonical-chain-upgrades/canonical-10002-rc2.md)
+      * [Upgrade to 10003-rc1](nodes/validators/mainnet/canonical-chain-upgrades/canonical-10003-rc1.md)
+      * [Upgrade to 10004-rc1](nodes/validators/mainnet/canonical-chain-upgrades/canonical-10004-rc1.md)
+      * [Upgrade to 10004-rc1-patch](nodes/validators/mainnet/canonical-chain-upgrades/canonical-10004-rc1-patch.md)
+      * [Upgrade to 10005-rc1](nodes/validators/mainnet/canonical-chain-upgrades/canonical-10005-rc1.md)
+      * [Upgrade to 10006-rc1](nodes/validators/mainnet/canonical-chain-upgrades/canonical-10006-rc1.md)
+      * [Upgrade to 10007-rc1](nodes/validators/mainnet/canonical-chain-upgrades/canonical-10007-rc1.md)
+      * [Upgrade to 10008 - Camelot](nodes/validators/mainnet/canonical-chain-upgrades/canonical-10008.md)
+      * [Upgrade to 10009](nodes/validators/mainnet/canonical-chain-upgrades/canonical-10009.md)
+      * [Upgrade to v1.10](nodes/validators/mainnet/canonical-chain-upgrades/canonical-100010.md)
+      * [Upgrade to v1.11](nodes/validators/mainnet/canonical-chain-upgrades/canonical-10011.md)
+      * [Upgrade to v1.12.0](nodes/validators/mainnet/canonical-chain-upgrades/canonical-1-12.md)
+      * [Upgrade to v1.12.1](nodes/validators/mainnet/canonical-chain-upgrades/canonical-1-12-1.md)
+      * [Upgrade to v1.13.0](nodes/validators/mainnet/canonical-chain-upgrades/canonical-1.13.0.md)
+      * [Upgrade to v1.13.2](nodes/validators/mainnet/canonical-chain-upgrades/canonical-1.13.2.md)
   * [Testnet](nodes/validators/testnet/README.md)
     * [Testnet Peggo](nodes/validators/testnet/testnet-peggo.md)
   * [Cosmosvisor](nodes/validators/cosmosvisor.md)

.gitbook/nodes/validators/mainnet/canonical-chain-upgrades.md

@@ -0,0 +1,87 @@
+# Canonical Chain Upgrades
+
+Nov 8th, 2021
+
+The following document describes the necessary steps involved that validators and full node operators must take in order to upgrade from the Injective Canary Chain to the Canonical Chain. The upgrade will take place via an on-chain software upgrade proposal passed by Injective governance. If passed, this proposal would commit the Injective Mainnet to halting the Canary Chain injectived application binary at approximately 14:00 UTC on Nov 8th and starting the application binary for the Injective Canonical Chain.
+
+Injective Canary Chain to the Canonical Chain upgrade follows [proposal #65](https://hub.injective.network/proposals/65)
+
+Following a chain upgrade timeline, as a first step proccedd to Canonical chain release [10002-rc1](canonical-10002-rc1.md) upgrade.
+
+
+## The History of Canonical Chain Upgrades
+
+---
+### Version 10002-rc1
+Nov 8th 2021 14:00 UTC 
+
+Block number: [4,352,000](https://explorer.injective.network/block/4352000)
+
+Released Artifacts: [Injective Chain 10002-rc1 release](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.1.0-1636178708)
+
+Following [proposal #65](https://hub.injective.network/proposals/65)
+
+---
+### Version 10002-rc2
+November 15th 2021 
+
+Block number: [4,594,100](https://explorer.injective.network/block/4594100)
+
+Released Artifacts: [Injective Chain 10002-rc2 release](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.1.1-1636733798)
+
+Following [proposal #70](https://hub.injective.network/proposals/70)
+
+---
+### Version 10003-rc1
+Thursday Dec 30th 2021
+
+Block number: [6,159,200](https://explorer.injective.network/block/6159200)
+
+Released Artifacts: [Mainnet-10003-rc1-1640627705](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.1.1-1640627705)
+
+Following [proposal #93](https://hub.injective.network/proposals/93)
+
+---
+### Version 10004-rc1
+Tuesday Jan 25th 2022
+
+Block number: [7067700](https://explorer.injective.network/block/7067700)
+
+Released Artifacts: [Mainnet-10004-rc1-v1.4.0-1642928125](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.4.0-1642928125)
+
+Following [proposal #106](https://hub.injective.network/proposals/106)
+
+### Version 10004-rc1-patch
+Sunday Feb 20th 2022
+
+Block number: [7941974](https://explorer.injective.network/block/7941974)
+
+Released Artifacts: [Mainnet-10004-rc1-v1.4.0-1645352045](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.4.0-1645352045)
+
+### Version 10005-rc1
+Monday April 11th 2022
+
+Block number: [9614200](https://explorer.injective.network/block/9614200)
+
+Released Artifacts: [Mainnet-v1.5.0-1649280277](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.5.0-1649280277)
+
+### Version 10006-rc1
+Tuesday July 5th 2022
+
+Block number: [12569420](https://explorer.injective.network/block/12569420)
+
+Released Artifacts: [Mainnet-v1.6.0-1656650662](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.6.0-1656650662)
+
+### Version 10007-rc1
+Thursday September 1th 2022
+
+Block number: [14731000](https://explorer.injective.network/block/14731000)
+
+Released Artifacts: [Mainnet-v1.7.0-1661881062](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.7.0-1661881062)
+
+### Version 10008
+Monday November 21th 2022
+
+Block number: [19761600](https://explorer.injective.network/block/19761600)
+
+Released Artifacts:  [Mainnet-10008-1668679102](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.8.0-1668679102)

.gitbook/nodes/validators/mainnet/canonical-chain-upgrades/README.md

@@ -0,0 +1,109 @@
+---
+sidebar_position: 14
+---
+   
+# Upgrade to v1.12.0
+Thursday January 11 2024
+
+Following [proposal 314](https://hub.injective.network/proposals/314/)
+This indicates that the upgrade procedure should be performed on block number **57076000**
+
+  - [Summary](#summary)
+  - [Risks](#risks)
+  - [Recovery](#recovery)
+  - [Upgrade Procedure](#upgrade-procedure)
+  - [Notes for Validator Operators](##notes-for-validator-operators)
+  - [Notes for Service Providers](##notes-for-DEX-relayer-providers)
+
+## Summary
+
+The Injective Canonical Chain will undergo a scheduled enhancement upgrade on **Jan 11th 14:00 UTC**.
+
+The following is a short summary of the upgrade steps:
+
+1. Vote and wait till the node panics at block height **57076000**.
+2. Backing up configs, data, and keys used for running the Injective Canonical Chain.
+3. Install the [v1.12.0-1704530206](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1)
+4. Start your node with the new injectived binary to fulfill the upgrade.
+
+Upgrade coordination and support for validators will be available on the `#validators` private channel of the [Injective Discord](https://discord.gg/injective).
+
+The network upgrade can take the following potential pathways:
+1. **Happy path**  
+Validators successfully upgrade chain without purging the blockchain history and all validators are up within 1-2 hours of the scheduled upgrade.
+
+2. **Not-so-happy path**  
+Validators have trouble upgrading to latest Canonical chain. This could be some consensus breaking changes not covered in upgrade handler, or compatibility issue of the migrated state with new injectived binary, but validators can at least export the genesis.
+
+3. **Abort path**  
+In the rare event that the team becomes aware of unnoticed critical issues, the Injective team will attempt to patch all the breaking states and provide another official binary within 36 hours.  
+If the chain is not successfully resumed within 36 hours, the upgrade will be announced as aborted on the #mainnet-validators channel of [Discord](https://discord.gg/injective), and validators will need to resume running the chain without any updates or changes. A new governance proposal for the upgrade will need to be issued and voted on by the community for the next upgrade.
+
+## Risks
+
+As a validator performing the upgrade procedure on your consensus nodes carries a heightened risk of double-signing and being slashed. The most important piece of this procedure is verifying your software version and genesis file hash before starting your validator and signing.
+
+The riskiest thing a validator can do is discover that they made a mistake and repeat the upgrade procedure again during the network startup. If you discover a mistake in the process, the best thing to do is wait for the network to start before correcting it. If the network is halted and you have started with a different genesis file than the expected one, seek advice from an Injective developer before resetting your validator.
+
+## Recovery
+
+Prior to exporting chain state, validators are encouraged to take a full data snapshot at the export height before proceeding. Snapshotting depends heavily on infrastructure, but generally this can be done by backing up the `.injectived` directory.
+
+It is critically important to backup the `.injectived/data/priv_validator_state.json` file after stopping your injectived process. This file is updated every block as your validator participates in a consensus rounds. It is a critical file needed to prevent double-signing, in case the upgrade fails and the previous chain needs to be restarted.
+
+In the event that the upgrade does not succeed, validators and operators must restore the snapshot and downgrade back to [Injective Chain 10011 release](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.11.6-1688984159) and continue the chain until next upgrade announcement.
+
+### Upgrade Procedure
+
+## Notes for Validators
+Validator operators should configure the **timeout_commit** in **config.toml** to `300ms`.
+
+You must remove the wasm cache before upgrading to the new version (rm -rf .injectived/wasm/wasm/cache/).
+
+1. Verify you are currently running the correct version (`69fb0c5`) of `injectived`:
+   ```bash
+      injectived version
+      Version dev (69fb0c5)
+      Compiled at 20230710-1016 using Go go1.19.3 (amd64)
+   ```
+
+2. After the chain has halted, make a backup of your `.injectived` directory
+    ```bash
+    cp ~/.injectived ./injectived-backup
+    ```
+    **NOTE**: It is recommended for validators and operators to take a full data snapshot at the export height before proceeding in case the upgrade does not go as planned or if not enough voting power comes online in a sufficient and agreed upon amount of time. In such a case, the chain will fallback to continue operating the Chain. See [Recovery](#recovery) for details on how to proceed.
+
+3. Download and install the injective-chain `v1.12.0 release`
+   ```bash
+   wget https://github.com/InjectiveLabs/injective-chain-releases/releases/download/v1.12.0-1704530206/linux-amd64.zip
+   unzip linux-amd64.zip
+   sudo mv injectived peggo /usr/bin
+   sudo mv libwasmvm.x86_64.so /usr/lib
+   ```
+
+4. Verify you are currently running the correct version (`b92723b13`) of `injectived` after downloading the v1.12.0 release:
+    ```bash
+   injectived version
+   Version dev (b92723b13)
+   Compiled at 20240106-0837 using Go go1.19.3 (amd64)
+   ```
+
+5. Coordinate to restart your injectived with other validators
+   ```bash
+   injectived start
+   ```
+   The binary will perform the upgrade automatically and continue the next consensus round if everything goes well.
+
+6. Verify you are currently running the correct version (`9e702f1`) of `peggo` after downloading the v1.12.0 release:
+  ```bash
+    peggo version
+    Version dev (9e702f1)
+    Compiled at 20240106-0837 using Go go1.19.3 (amd64)
+   ```
+8. Start peggo
+   ```bash
+   peggo orchestrator
+   ```   
+
+## Notes for DEX relayer providers
+Relayer upgrade will be available after the chain is successfully upgraded as it relies on several other components that work with injectived.