diff --git a/docs/protocol_devs/development/developing_runtime.md b/docs/protocol_devs/development/developing_runtime.md
index 7899292..43241a9 100644
--- a/docs/protocol_devs/development/developing_runtime.md
+++ b/docs/protocol_devs/development/developing_runtime.md
@@ -153,7 +153,7 @@ If you're curious how a real [Pool](https://app.korellia.kyve.network/#/pools/30
"operating_cost": "2500000000",
"min_delegation": "100000000000",
"max_bundle_size": "100",
- "version": "1.0.0-beta.2",
+ "version": "1.0.7",
"binaries": "{\"kyve-linux-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.0-beta.2/kyve-linux-x64.zip\",\"kyve-linux-arm64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.0-beta.2/kyve-linux-arm64.zip\"}",
"storage_provider_id": 3,
"compression_id": 1
diff --git a/docs/tools/supervysor/examples.md b/docs/tools/supervysor/examples.md
index 35b7b48..c8960ed 100644
--- a/docs/tools/supervysor/examples.md
+++ b/docs/tools/supervysor/examples.md
@@ -19,9 +19,9 @@ With your node being able to run using Cosmovisor, you can stop the process and
```bash
supervysor init \
---binary-path '/root/go/bin/cosmovisor' \
+--binary '/root/go/bin/cosmovisor' \
--chain-id 'kyve-1' \
---home-path '/root/.osmosisd' \
+--home '/root/.osmosisd' \
--pool-id 1 \
--seeds '6bcdbcfd5d2c6ba58460f10dbcfde58278212833@osmosis.artifact-staking.io:26656,ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@seeds.polkachu.com:12556'
```
diff --git a/docs/tools/supervysor/installation.md b/docs/tools/supervysor/installation.md
index c4c95ac..12ef769 100644
--- a/docs/tools/supervysor/installation.md
+++ b/docs/tools/supervysor/installation.md
@@ -20,7 +20,7 @@ go install github.com/KYVENetwork/supervysor/cmd/supervysor@latest
To install a previous version, you can specify the version:
```bash
-go install github.com/KYVENetwork/supervysor/cmd/supervysor@v0.1.0
+go install github.com/KYVENetwork/supervysor/cmd/supervysor@v0.2.0
```
:::info
diff --git a/docs/tools/supervysor/overview.md b/docs/tools/supervysor/overview.md
index ecd896a..cad1ff6 100644
--- a/docs/tools/supervysor/overview.md
+++ b/docs/tools/supervysor/overview.md
@@ -30,8 +30,3 @@ These values ensure that
### Pruning
Aside from the optimized syncing process, pruning already validated data is the second role of the supervysor to fulfill its goal of reducing disk storage requirements. Therefore, a custom pruning method is used, which relies on the provided Tendermint functionality of pruning all blocks until a specified height. In the context of the supervysor, this until-height should always be lower than the latest validated height of the KYVE data pool to ensure no data is pruned that needs validation. Unfortunately, the node has to be stopped to execute the pruning process, while a pruning-interval needs specification in hours. During this interval, the supervysor halts the current node process, prunes all validated blocks, and restarts the node. Due to the required time to connect with peers and to prevent the pool from catching up with the node, the pruning process is only initiated if the node is in GhostMode. If the node is in NormalMode, even if the interval reaches the pruning threshold, pruning will be enabled immediately after the node enters GhostMode. Additionally, it is recommended to set the pruning-interval to a value of at least six hours to ensure there is enough time to find peers before the pool catches up.
-
-This ensures that
-
-- only the required blocks for the next 2 days are kept locally, everything else will be pruned,
-- because `min_retain_blocks > height_difference_max`, nothing will be pruned before it was validated in the data pool.
\ No newline at end of file
diff --git a/docs/tools/supervysor/usage.md b/docs/tools/supervysor/usage.md
index 3f9679c..b842922 100644
--- a/docs/tools/supervysor/usage.md
+++ b/docs/tools/supervysor/usage.md
@@ -8,10 +8,12 @@ To use the supervysor, you first need to initialize it:
```bash
supervysor init
---binary-path string 'path to chain binaries (e.g. ~/go/bin/osmosisd)'
+--abci-endpoint string 'ABCI Endpoint to request node information (default "http://127.0.0.1:26657")'
+--binary string 'path to chain binaries (e.g. ~/go/bin/osmosisd)'
--chain-id string 'KYVE chain-id'
---home-path string 'path to home directory (e.g. ~/.osmosisd)'
+--home string 'path to home directory (e.g. ~/.osmosisd)'
--metrics string 'exposing Prometheus metrics ("true" or "false")'
+--metrics-port int 'port for metrics server (default 26660)'
--pool-id int 'KYVE pool-id'
--seeds string 'seeds for the node to connect'
--pruning-interval int 'block-pruning interval (hours) (default 24)'
diff --git a/docs/validators/protocol_nodes/pools/archway/run_archway_node.md b/docs/validators/protocol_nodes/pools/archway/run_archway_node.md
index ffe0e38..c0c6c35 100644
--- a/docs/validators/protocol_nodes/pools/archway/run_archway_node.md
+++ b/docs/validators/protocol_nodes/pools/archway/run_archway_node.md
@@ -80,7 +80,7 @@ Finally, the node can be started:
```
:::caution
-**ATTENTION**: To be able to perform upgrades automatically, it is recommended to use the cosmovisor. How to set it up can be found [here](https://docs.archway.io/validators/running-a-node/cosmovisor).
+To be able to perform upgrades automatically, it is recommended to use the cosmovisor. How to set it up can be found [here](https://docs.archway.io/validators/running-a-node/cosmovisor).
:::
To start the Archway node with the cosmovisor, run:
@@ -89,6 +89,10 @@ To start the Archway node with the cosmovisor, run:
cosmovisor run start --x-crisis-skip-assert-invariants
```
+:::info
+Regarding __SoftwareUpgrades__ of the node, we recommend the official [upgrade path]("https://docs.axelar.dev/node/join-genesis#follow-the-upgrade-path") by Axelar
+:::
+
### 2. Archway Docker Container
To get the latest Archway node image, run:
diff --git a/docs/validators/protocol_nodes/pools/archway/run_protocol_node.md b/docs/validators/protocol_nodes/pools/archway/run_protocol_node.md
index 3a73f92..bcc6755 100644
--- a/docs/validators/protocol_nodes/pools/archway/run_protocol_node.md
+++ b/docs/validators/protocol_nodes/pools/archway/run_protocol_node.md
@@ -51,8 +51,8 @@ After the node successfully started you should see the following logs:
2023-02-13 08:46:00.873 INFO Runtime = @kyvejs/tendermint
2023-02-13 08:46:00.873 INFO Valaddress = kyve1887l27uwn5r6u9gxw7dg9wt0kqh7uk23suumzc
-2023-02-13 08:46:00.873 INFO @kyvejs/tendermint = v1.0.0-beta.1
-2023-02-13 08:46:00.873 INFO @kyvejs/protocol = v1.0.0-beta.14
+2023-02-13 08:46:00.873 INFO @kyvejs/tendermint = v1.0.7
+2023-02-13 08:46:00.873 INFO @kyvejs/protocol = v1.0.11
2023-02-13 08:46:00.876 INFO Valaccount has not joined the pool with id 1 yet
2023-02-13 08:46:00.876 INFO Visit https://app.kyve.network and join the pool from your validator account:
diff --git a/docs/validators/protocol_nodes/pools/archway/upgrade.md b/docs/validators/protocol_nodes/pools/archway/upgrade.md
index 8f04174..2576391 100644
--- a/docs/validators/protocol_nodes/pools/archway/upgrade.md
+++ b/docs/validators/protocol_nodes/pools/archway/upgrade.md
@@ -39,14 +39,14 @@ The first step is to check if the upgrade proposal has passed and when it will g
"@type": "/kyve.pool.v1beta1.MsgScheduleRuntimeUpgrade",
"authority": "kyve10d07y265gmmuvt4z0w9aw880jnsr700jdv7nah",
"runtime": "@kyvejs/tendermint",
- "version": "1.0.0-beta.1",
+ "version": "1.0.7",
"scheduled_at": "1684749600",
"duration": "600",
- "binaries": "{\"kyve-linux-arm64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.0-beta.1/kyve-linux-arm64.zip\",\"kyve-linux-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.0-beta.1/kyve-linux-x64.zip\",\"kyve-macos-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.0-beta.1/kyve-macos-x64.zip\"}"
+ "binaries": "{\"kyve-linux-arm64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.7/kyve-linux-arm64.zip\",\"kyve-linux-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.7/kyve-linux-x64.zip\",\"kyve-macos-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.7/kyve-macos-x64.zip\"}"
}
```
-Here **every** pool which is running on the _@kyvejs/tendermint_ runtime gets upgraded with the new version of _1.0.0-beta.1_. The upgrade will go into effect
+Here **every** pool which is running on the _@kyvejs/tendermint_ runtime gets upgraded with the new version of _1.0.7_. The upgrade will go into effect
at the _scheduled_at_ time (UNIX time format). Once the upgrade goes into effect the pool will halt during the upgrade is getting applied. The length of the upgrade
is determined by the _duration_ (here 600 seconds -> 10 mins). The reason behind an upgrade duration where the pool halts is to give node operators some time to perform
the upgrade (restart the node or manually switch out the binaries during that time). After the duration has completed the pool will continue automatically. Finally, the
@@ -70,8 +70,8 @@ mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/x.x.x/bin/
**IMPORTANT**: The version _x.x.x_ has to match with the version in the upgrade proposal, so for the example proposal above it would be:
```bash
-mkdir -r ~/.kysor/upgrades/pool-0/1.0.0-beta.1/bin/
-mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/1.0.0-beta.1/bin/
+mkdir -r ~/.kysor/upgrades/pool-0/1.0.7/bin/
+mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/1.0.7/bin/
```
:::
@@ -79,12 +79,12 @@ mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/1.0.0-beta.1/bin/
To make sure the installation was successful you can print the version which should match with the version in the path:
```bash
-.kysor/upgrades/pool-0/1.0.0-beta.1/bin/kyve-macos-x64 version
+.kysor/upgrades/pool-0/1.0.7/bin/kyve-macos-x64 version
```
```bash
-@kyvejs/tendermint version: 1.0.0-beta.0
-@kyvejs/protocol version: 1.0.0-beta.24
+@kyvejs/tendermint version: 1.0.7
+@kyvejs/protocol version: 1.0.11
Node version: v18.5.0
Platform: linux
@@ -106,8 +106,8 @@ if you have installed the correct version by executing the version command.
```
```bash
-@kyvejs/tendermint version: 1.0.0-beta.1
-@kyvejs/protocol version: 1.0.0-beta.24
+@kyvejs/tendermint version: 1.0.7
+@kyvejs/protocol version: 1.0.11
Node version: v18.5.0
Platform: linux
diff --git a/docs/validators/protocol_nodes/pools/axelar/run_protocol_node.md b/docs/validators/protocol_nodes/pools/axelar/run_protocol_node.md
index caa302d..a0da3a6 100644
--- a/docs/validators/protocol_nodes/pools/axelar/run_protocol_node.md
+++ b/docs/validators/protocol_nodes/pools/axelar/run_protocol_node.md
@@ -51,8 +51,8 @@ After the node successfully started you should see the following logs:
2023-02-13 08:46:00.873 INFO Runtime = @kyvejs/tendermint
2023-02-13 08:46:00.873 INFO Valaddress = kyve1887l27uwn5r6u9gxw7dg9wt0kqh7uk23suumzc
-2023-02-13 08:46:00.873 INFO @kyvejs/tendermint = v1.0.0-beta.1
-2023-02-13 08:46:00.873 INFO @kyvejs/protocol = v1.0.0-beta.14
+2023-02-13 08:46:00.873 INFO @kyvejs/tendermint = v1.0.7
+2023-02-13 08:46:00.873 INFO @kyvejs/protocol = v1.0.11
2023-02-13 08:46:00.876 INFO Valaccount has not joined the pool with id 1 yet
2023-02-13 08:46:00.876 INFO Visit https://app.kyve.network and join the pool from your validator account:
diff --git a/docs/validators/protocol_nodes/pools/axelar/upgrade.md b/docs/validators/protocol_nodes/pools/axelar/upgrade.md
index 41e10ab..7e426d6 100644
--- a/docs/validators/protocol_nodes/pools/axelar/upgrade.md
+++ b/docs/validators/protocol_nodes/pools/axelar/upgrade.md
@@ -39,14 +39,14 @@ The first step is to check if the upgrade proposal has passed and when it will g
"@type": "/kyve.pool.v1beta1.MsgScheduleRuntimeUpgrade",
"authority": "kyve10d07y265gmmuvt4z0w9aw880jnsr700jdv7nah",
"runtime": "@kyvejs/tendermint",
- "version": "1.0.0-beta.1",
+ "version": "1.0.7",
"scheduled_at": "1684749600",
"duration": "600",
- "binaries": "{\"kyve-linux-arm64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.0-beta.1/kyve-linux-arm64.zip\",\"kyve-linux-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.0-beta.1/kyve-linux-x64.zip\",\"kyve-macos-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.0-beta.1/kyve-macos-x64.zip\"}"
+ "binaries": "{\"kyve-linux-arm64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.7/kyve-linux-arm64.zip\",\"kyve-linux-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.7/kyve-linux-x64.zip\",\"kyve-macos-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.7/kyve-macos-x64.zip\"}"
}
```
-Here **every** pool which is running on the _@kyvejs/tendermint_ runtime gets upgraded with the new version of _1.0.0-beta.1_. The upgrade will go into effect
+Here **every** pool which is running on the _@kyvejs/tendermint_ runtime gets upgraded with the new version of _1.0.7_. The upgrade will go into effect
at the _scheduled_at_ time (UNIX time format). Once the upgrade goes into effect the pool will halt during the upgrade is getting applied. The length of the upgrade
is determined by the _duration_ (here 600 seconds -> 10 mins). The reason behind an upgrade duration where the pool halts is to give node operators some time to perform
the upgrade (restart the node or manually switch out the binaries during that time). After the duration has completed the pool will continue automatically. Finally, the
@@ -70,8 +70,8 @@ mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/x.x.x/bin/
**IMPORTANT**: The version _x.x.x_ has to match with the version in the upgrade proposal, so for the example proposal above it would be:
```bash
-mkdir -r ~/.kysor/upgrades/pool-0/1.0.0-beta.1/bin/
-mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/1.0.0-beta.1/bin/
+mkdir -r ~/.kysor/upgrades/pool-0/1.0.7/bin/
+mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/1.0.7/bin/
```
:::
@@ -79,14 +79,12 @@ mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/1.0.0-beta.1/bin/
To make sure the installation was successful you can print the version which should match with the version in the path:
```bash
-.kysor/upgrades/pool-0/1.0.0-beta.1/bin/kyve-macos-x64 version
+.kysor/upgrades/pool-0/1.0.7/bin/kyve-macos-x64 version
```
-TODO
-
```bash
-@kyvejs/tendermint version: 1.0.0-beta.0
-@kyvejs/protocol version: 1.0.0-beta.24
+@kyvejs/tendermint version: 1.0.7
+@kyvejs/protocol version: 1.0.11
Node version: v18.5.0
Platform: linux
@@ -107,11 +105,9 @@ if you have installed the correct version by executing the version command.
./kyve-macos-x64 version
```
-TODO
-
```bash
-@kyvejs/tendermint version: 1.0.0-beta.1
-@kyvejs/protocol version: 1.0.0-beta.24
+@kyvejs/tendermint version: 1.0.7
+@kyvejs/protocol version: 1.0.11
Node version: v18.5.0
Platform: linux
diff --git a/docs/validators/protocol_nodes/pools/cosmos_hub/run_node.md b/docs/validators/protocol_nodes/pools/cosmos_hub/run_node.md
index 369d0c2..27f940b 100644
--- a/docs/validators/protocol_nodes/pools/cosmos_hub/run_node.md
+++ b/docs/validators/protocol_nodes/pools/cosmos_hub/run_node.md
@@ -51,8 +51,8 @@ After the node successfully started you should see the following logs:
2023-02-13 08:46:00.873 INFO Runtime = @kyvejs/tendermint-bsync
2023-02-13 08:46:00.873 INFO Valaddress = kyve1887l27uwn5r6u9gxw7dg9wt0kqh7uk23suumzc
-2023-02-13 08:46:00.873 INFO @kyvejs/tendermint-bsync = v1.0.0-beta.9
-2023-02-13 08:46:00.873 INFO @kyvejs/protocol = v1.0.0-beta.14
+2023-02-13 08:46:00.873 INFO @kyvejs/tendermint-bsync = v1.0.11
+2023-02-13 08:46:00.873 INFO @kyvejs/protocol = v1.0.11
2023-02-13 08:46:00.876 INFO Valaccount has not joined the pool with id 0 yet
2023-02-13 08:46:00.876 INFO Visit https://app.kyve.network and join the pool from your validator account:
diff --git a/docs/validators/protocol_nodes/pools/cosmos_hub/upgrade.md b/docs/validators/protocol_nodes/pools/cosmos_hub/upgrade.md
index bff5b53..2622cc1 100644
--- a/docs/validators/protocol_nodes/pools/cosmos_hub/upgrade.md
+++ b/docs/validators/protocol_nodes/pools/cosmos_hub/upgrade.md
@@ -39,14 +39,14 @@ The first step is to check if the upgrade proposal has passed and when it will g
"@type": "/kyve.pool.v1beta1.MsgScheduleRuntimeUpgrade",
"authority": "kyve10d07y265gmmuvt4z0w9aw880jnsr700jdv7nah",
"runtime": "@kyvejs/tendermint-bsync",
- "version": "1.0.0-beta.10",
+ "version": "1.0.11",
"scheduled_at": "1684749600",
"duration": "600",
- "binaries": "{\"kyve-linux-arm64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint-bsync%401.0.0-beta.10/kyve-linux-arm64.zip\",\"kyve-linux-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint-bsync%401.0.0-beta.10/kyve-linux-x64.zip\",\"kyve-macos-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint-bsync%401.0.0-beta.10/kyve-macos-x64.zip\"}"
+ "binaries": "{\"kyve-linux-arm64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint-bsync%401.0.11/kyve-linux-arm64.zip\",\"kyve-linux-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint-bsync%401.0.11/kyve-linux-x64.zip\",\"kyve-macos-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint-bsync%401.0.11/kyve-macos-x64.zip\"}"
}
```
-Here **every** pool which is running on the _@kyvejs/tendermint-bsync_ runtime gets upgraded with the new version of _1.0.0-beta.10_. The upgrade will go into effect
+Here **every** pool which is running on the _@kyvejs/tendermint-bsync_ runtime gets upgraded with the new version of _1.0.11_. The upgrade will go into effect
at the _scheduled_at_ time (UNIX time format). Once the upgrade goes into effect the pool will halt during the upgrade is getting applied. The length of the upgrade
is determined by the _duration_ (here 600 seconds -> 10 mins). The reason behind an upgrade duration where the pool halts is to give node operators some time to perform
the upgrade (restart the node or manually switch out the binaries during that time). After the duration has completed the pool will continue automatically. Finally, the
@@ -70,8 +70,8 @@ mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/x.x.x/bin/
**IMPORTANT**: The version _x.x.x_ has to match with the version in the upgrade proposal, so for the example proposal above it would be:
```bash
-mkdir -r ~/.kysor/upgrades/pool-0/1.0.0-beta.10/bin/
-mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/1.0.0-beta.10/bin/
+mkdir -r ~/.kysor/upgrades/pool-0/1.0.11/bin/
+mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/1.0.11/bin/
```
:::
@@ -79,12 +79,12 @@ mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/1.0.0-beta.10/bin/
To make sure the installation was successful you can print the version which should match with the version in the path:
```bash
-.kysor/upgrades/pool-0/1.0.0-beta.10/bin/kyve-macos-x64 version
+.kysor/upgrades/pool-0/1.0.11/bin/kyve-macos-x64 version
```
```bash
-@kyvejs/tendermint-bsync version: 1.0.0-beta.10
-@kyvejs/protocol version: 1.0.0-beta.24
+@kyvejs/tendermint-bsync version: 1.0.11
+@kyvejs/protocol version: 1.0.11
Node version: v18.5.0
Platform: linux
@@ -106,8 +106,8 @@ if you have installed the correct version by executing the version command.
```
```bash
-@kyvejs/tendermint-bsync version: 1.0.0-beta.10
-@kyvejs/protocol version: 1.0.0-beta.24
+@kyvejs/tendermint-bsync version: 1.0.11
+@kyvejs/protocol version: 1.0.11
Node version: v18.5.0
Platform: linux
diff --git a/docs/validators/protocol_nodes/pools/osmosis/run_protocol_node.md b/docs/validators/protocol_nodes/pools/osmosis/run_protocol_node.md
index 8932a9a..a2bfa1a 100644
--- a/docs/validators/protocol_nodes/pools/osmosis/run_protocol_node.md
+++ b/docs/validators/protocol_nodes/pools/osmosis/run_protocol_node.md
@@ -51,8 +51,8 @@ After the node successfully started you should see the following logs:
2023-02-13 08:46:00.873 INFO Runtime = @kyvejs/tendermint
2023-02-13 08:46:00.873 INFO Valaddress = kyve1887l27uwn5r6u9gxw7dg9wt0kqh7uk23suumzc
-2023-02-13 08:46:00.873 INFO @kyvejs/tendermint = v1.0.0-beta.1
-2023-02-13 08:46:00.873 INFO @kyvejs/protocol = v1.0.0-beta.14
+2023-02-13 08:46:00.873 INFO @kyvejs/tendermint = v1.0.7
+2023-02-13 08:46:00.873 INFO @kyvejs/protocol = v1.0.11
2023-02-13 08:46:00.876 INFO Valaccount has not joined the pool with id 1 yet
2023-02-13 08:46:00.876 INFO Visit https://app.kyve.network and join the pool from your validator account:
diff --git a/docs/validators/protocol_nodes/pools/osmosis/upgrade.md b/docs/validators/protocol_nodes/pools/osmosis/upgrade.md
index 9f10821..84470ed 100644
--- a/docs/validators/protocol_nodes/pools/osmosis/upgrade.md
+++ b/docs/validators/protocol_nodes/pools/osmosis/upgrade.md
@@ -39,14 +39,14 @@ The first step is to check if the upgrade proposal has passed and when it will g
"@type": "/kyve.pool.v1beta1.MsgScheduleRuntimeUpgrade",
"authority": "kyve10d07y265gmmuvt4z0w9aw880jnsr700jdv7nah",
"runtime": "@kyvejs/tendermint",
- "version": "1.0.0-beta.1",
+ "version": "1.0.7",
"scheduled_at": "1684749600",
"duration": "600",
- "binaries": "{\"kyve-linux-arm64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.0-beta.1/kyve-linux-arm64.zip\",\"kyve-linux-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.0-beta.1/kyve-linux-x64.zip\",\"kyve-macos-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.0-beta.1/kyve-macos-x64.zip\"}"
+ "binaries": "{\"kyve-linux-arm64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.11/kyve-linux-arm64.zip\",\"kyve-linux-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.7/kyve-linux-x64.zip\",\"kyve-macos-x64\":\"https://github.com/KYVENetwork/kyvejs/releases/download/%40kyvejs%2Ftendermint%401.0.7/kyve-macos-x64.zip\"}"
}
```
-Here **every** pool which is running on the _@kyvejs/tendermint_ runtime gets upgraded with the new version of _1.0.0-beta.1_. The upgrade will go into effect
+Here **every** pool which is running on the _@kyvejs/tendermint_ runtime gets upgraded with the new version of _1.0.7_. The upgrade will go into effect
at the _scheduled_at_ time (UNIX time format). Once the upgrade goes into effect the pool will halt during the upgrade is getting applied. The length of the upgrade
is determined by the _duration_ (here 600 seconds -> 10 mins). The reason behind an upgrade duration where the pool halts is to give node operators some time to perform
the upgrade (restart the node or manually switch out the binaries during that time). After the duration has completed the pool will continue automatically. Finally, the
@@ -70,8 +70,8 @@ mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/x.x.x/bin/
**IMPORTANT**: The version _x.x.x_ has to match with the version in the upgrade proposal, so for the example proposal above it would be:
```bash
-mkdir -r ~/.kysor/upgrades/pool-0/1.0.0-beta.1/bin/
-mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/1.0.0-beta.1/bin/
+mkdir -r ~/.kysor/upgrades/pool-0/1.0.7/bin/
+mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/1.0.7/bin/
```
:::
@@ -79,13 +79,12 @@ mv kyve-linux-x64 ~/.kysor/upgrades/pool-0/1.0.0-beta.1/bin/
To make sure the installation was successful you can print the version which should match with the version in the path:
```bash
-.kysor/upgrades/pool-0/1.0.0-beta.1/bin/kyve-macos-x64 version
+.kysor/upgrades/pool-0/1.0.7/bin/kyve-macos-x64 version
```
-TODO
```bash
-@kyvejs/tendermint version: 1.0.0-beta.0
-@kyvejs/protocol version: 1.0.0-beta.24
+@kyvejs/tendermint version: 1.0.7
+@kyvejs/protocol version: 1.0.11
Node version: v18.5.0
Platform: linux
@@ -106,11 +105,9 @@ if you have installed the correct version by executing the version command.
./kyve-macos-x64 version
```
-TODO
-
```bash
-@kyvejs/tendermint version: 1.0.0-beta.1
-@kyvejs/protocol version: 1.0.0-beta.24
+@kyvejs/tendermint version: 1.0.7
+@kyvejs/protocol version: 1.0.11
Node version: v18.5.0
Platform: linux