From ed8a68d58b791c39c911d4eefd5868daeba7bb44 Mon Sep 17 00:00:00 2001 From: Pavel Zaborskii Date: Wed, 5 Feb 2025 01:03:07 +0300 Subject: [PATCH 1/7] software-upgrades.mdx --- pages/devs/validators/software-upgrades.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/devs/validators/software-upgrades.mdx b/pages/devs/validators/software-upgrades.mdx index a3981ff..5c62887 100644 --- a/pages/devs/validators/software-upgrades.mdx +++ b/pages/devs/validators/software-upgrades.mdx @@ -48,9 +48,9 @@ version that is being upgraded from, and the function to run to do the migration #### For Allora Chain Validator Operators -For those running the chain software, you will have to have to perform an upgrade as follows: +For those running the chain software, you will have to perform an upgrade as follows: -1. Make sure you're running the `allorad` software with [Cosmovisor](https://docs.cosmos.network/main/build/tooling/cosmovisor)) managing the process, `DAEMON_NAME=allorad` and `DAEMON_HOME=/path/to/allorad/data/folder`. Hopefully you've already run `cosmovisor init /path/to/allorad-binary` and have the `/allorad/data/folder/cosmovisor` set. +1. Make sure you're running the `allorad` software with [Cosmovisor](https://docs.cosmos.network/main/build/tooling/cosmovisor) managing the process, `DAEMON_NAME=allorad` and `DAEMON_HOME=/path/to/allorad/data/folder`. Hopefully you've already run `cosmovisor init /path/to/allorad-binary` and have the `/allorad/data/folder/cosmovisor` set. 2. At some point the blockchain developers will provide you with a binary to put in that `/allorad/data/folder/cosmovisor` folder to upgrade to. This may be optional if the `UpgradeInfo` is set correctly by the developers, but if you're the paranoid type you can always download the binary yourself ahead of the upgrade and put it in the right folder by hand. 3. When the developers put up the upgrade proposal to governance, be helpful and vote to make it pass. You can do this via the CLI with `allorad tx gov vote $proposal_id yes --from $validator` or an example of doing this programmatically can be found in the integration test [voteOnProposal](https://github.com/allora-network/allora-chain/blob/main/test/integration/upgrade_test.go) function. 4. At the block height of the upgrade, the old software will panic - cosmovisor will catch the panic and restart the process using the new binary for the upgrade instead. Monitor your logs appropriately to see the restart. From 1d198a60e63fa9723c9eb1e97a0233242d715d91 Mon Sep 17 00:00:00 2001 From: Pavel Zaborskii Date: Wed, 5 Feb 2025 01:04:54 +0300 Subject: [PATCH 2/7] build-and-deploy-worker-with-node-runners.mdx --- .../deploy-worker/build-and-deploy-worker-with-node-runners.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/devs/workers/deploy-worker/build-and-deploy-worker-with-node-runners.mdx b/pages/devs/workers/deploy-worker/build-and-deploy-worker-with-node-runners.mdx index 1108330..d4ee1b2 100644 --- a/pages/devs/workers/deploy-worker/build-and-deploy-worker-with-node-runners.mdx +++ b/pages/devs/workers/deploy-worker/build-and-deploy-worker-with-node-runners.mdx @@ -45,7 +45,7 @@ This diagram illustrates the architecture of the integration between the Allora ## AWS Activate -Before proceeding, please note that eligibility for AWS Activate credits and terams are governed by AWS. This documentation may become outdated, so ensure you refer to the [AWS Activate program page](https://aws.amazon.com/startups/credits#hero) for the latest eligibility requirements and instructions. +Before proceeding, please note that eligibility for AWS Activate credits and terms are governed by AWS. This documentation may become outdated, so ensure you refer to the [AWS Activate program page](https://aws.amazon.com/startups/credits#hero) for the latest eligibility requirements and instructions. ## AWS Activate Stepwise Process From cdfe6ec68945a75e42010694edb530951c4760da Mon Sep 17 00:00:00 2001 From: Pavel Zaborskii Date: Wed, 5 Feb 2025 01:16:42 +0300 Subject: [PATCH 3/7] allorad.mdx --- pages/devs/reference/allorad.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/devs/reference/allorad.mdx b/pages/devs/reference/allorad.mdx index 44ba463..7646271 100644 --- a/pages/devs/reference/allorad.mdx +++ b/pages/devs/reference/allorad.mdx @@ -628,7 +628,7 @@ Detailed instructions on [how to create a topic](/devs/topic-creators/how-to-cre - **Description:** Remove an admin address from the whitelist used for admin functions on-chain. - **Positional Arguments:** - `sender` Address of the sender - - `address` Address that will be removed to the whitelist + - `address` Address that will be removed from the whitelist ### Register Network Actor - **RPC Method:** `Register` From c3aee95d48ecc14c0fd6a9c1f4df9f9dee7e48e5 Mon Sep 17 00:00:00 2001 From: Pavel Zaborskii Date: Wed, 5 Feb 2025 01:19:21 +0300 Subject: [PATCH 4/7] chain.mdx --- pages/devs/reference/params/chain.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/devs/reference/params/chain.mdx b/pages/devs/reference/params/chain.mdx index 5ac4ea9..175ea41 100644 --- a/pages/devs/reference/params/chain.mdx +++ b/pages/devs/reference/params/chain.mdx @@ -96,7 +96,7 @@ Penalizing workers for missing inferences encourages reliability and accountabil #### required_minimum_stake -Sets the minimum stake to be considered as a reputer in good standing. If a reputer has less than this stake, than their contribution to reputation scoring will be ignored, and they will not receive any rewards from the system. +Sets the minimum stake to be considered as a reputer in good standing. If a reputer has less than this stake, then their contribution to reputation scoring will be ignored, and they will not receive any rewards from the system. Default Value: 100 allo From 89b661bfab89d7e8e4c31b31e983d0bc529292f1 Mon Sep 17 00:00:00 2001 From: Pavel Zaborskii Date: Wed, 5 Feb 2025 01:24:28 +0300 Subject: [PATCH 5/7] chain.mdx --- pages/devs/reference/params/chain.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/devs/reference/params/chain.mdx b/pages/devs/reference/params/chain.mdx index 175ea41..5ac4ea9 100644 --- a/pages/devs/reference/params/chain.mdx +++ b/pages/devs/reference/params/chain.mdx @@ -96,7 +96,7 @@ Penalizing workers for missing inferences encourages reliability and accountabil #### required_minimum_stake -Sets the minimum stake to be considered as a reputer in good standing. If a reputer has less than this stake, then their contribution to reputation scoring will be ignored, and they will not receive any rewards from the system. +Sets the minimum stake to be considered as a reputer in good standing. If a reputer has less than this stake, than their contribution to reputation scoring will be ignored, and they will not receive any rewards from the system. Default Value: 100 allo From 4d61ae36e72648333f1a7c57e1c8534e5b4ffa6c Mon Sep 17 00:00:00 2001 From: Pavel Zaborskii Date: Wed, 5 Feb 2025 01:27:16 +0300 Subject: [PATCH 6/7] software-upgrades.mdx --- pages/devs/validators/software-upgrades.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/devs/validators/software-upgrades.mdx b/pages/devs/validators/software-upgrades.mdx index 5c62887..7b2c790 100644 --- a/pages/devs/validators/software-upgrades.mdx +++ b/pages/devs/validators/software-upgrades.mdx @@ -50,7 +50,7 @@ version that is being upgraded from, and the function to run to do the migration For those running the chain software, you will have to perform an upgrade as follows: -1. Make sure you're running the `allorad` software with [Cosmovisor](https://docs.cosmos.network/main/build/tooling/cosmovisor) managing the process, `DAEMON_NAME=allorad` and `DAEMON_HOME=/path/to/allorad/data/folder`. Hopefully you've already run `cosmovisor init /path/to/allorad-binary` and have the `/allorad/data/folder/cosmovisor` set. +1. Make sure you're running the `allorad` software with [Cosmovisor](https://docs.cosmos.network/main/build/tooling/cosmovisor)) managing the process, `DAEMON_NAME=allorad` and `DAEMON_HOME=/path/to/allorad/data/folder`. Hopefully you've already run `cosmovisor init /path/to/allorad-binary` and have the `/allorad/data/folder/cosmovisor` set. 2. At some point the blockchain developers will provide you with a binary to put in that `/allorad/data/folder/cosmovisor` folder to upgrade to. This may be optional if the `UpgradeInfo` is set correctly by the developers, but if you're the paranoid type you can always download the binary yourself ahead of the upgrade and put it in the right folder by hand. 3. When the developers put up the upgrade proposal to governance, be helpful and vote to make it pass. You can do this via the CLI with `allorad tx gov vote $proposal_id yes --from $validator` or an example of doing this programmatically can be found in the integration test [voteOnProposal](https://github.com/allora-network/allora-chain/blob/main/test/integration/upgrade_test.go) function. 4. At the block height of the upgrade, the old software will panic - cosmovisor will catch the panic and restart the process using the new binary for the upgrade instead. Monitor your logs appropriately to see the restart. From d855d99cfe11ef6f3770b11be8bf61c9b33e5559 Mon Sep 17 00:00:00 2001 From: Pavel Zaborskii Date: Wed, 5 Feb 2025 01:29:21 +0300 Subject: [PATCH 7/7] build-and-deploy-worker-with-node-runners.mdx --- .../deploy-worker/build-and-deploy-worker-with-node-runners.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/devs/workers/deploy-worker/build-and-deploy-worker-with-node-runners.mdx b/pages/devs/workers/deploy-worker/build-and-deploy-worker-with-node-runners.mdx index d4ee1b2..1108330 100644 --- a/pages/devs/workers/deploy-worker/build-and-deploy-worker-with-node-runners.mdx +++ b/pages/devs/workers/deploy-worker/build-and-deploy-worker-with-node-runners.mdx @@ -45,7 +45,7 @@ This diagram illustrates the architecture of the integration between the Allora ## AWS Activate -Before proceeding, please note that eligibility for AWS Activate credits and terms are governed by AWS. This documentation may become outdated, so ensure you refer to the [AWS Activate program page](https://aws.amazon.com/startups/credits#hero) for the latest eligibility requirements and instructions. +Before proceeding, please note that eligibility for AWS Activate credits and terams are governed by AWS. This documentation may become outdated, so ensure you refer to the [AWS Activate program page](https://aws.amazon.com/startups/credits#hero) for the latest eligibility requirements and instructions. ## AWS Activate Stepwise Process