From f3e20e89b91c9555dc8918e1bfa3afc43551312b Mon Sep 17 00:00:00 2001 From: futreall <86553580+futreall@users.noreply.github.com> Date: Mon, 27 Jan 2025 17:58:47 +0200 Subject: [PATCH 1/3] Update deploy-consumer.mdx Signed-off-by: futreall <86553580+futreall@users.noreply.github.com> --- pages/devs/consumers/consumer-contracts/deploy-consumer.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/devs/consumers/consumer-contracts/deploy-consumer.mdx b/pages/devs/consumers/consumer-contracts/deploy-consumer.mdx index d952b2e..d250107 100644 --- a/pages/devs/consumers/consumer-contracts/deploy-consumer.mdx +++ b/pages/devs/consumers/consumer-contracts/deploy-consumer.mdx @@ -27,7 +27,7 @@ Create a `.env` file in the root of the project with the following structure: ```Text .env deploymentName= -chainId= +chainId= rpcUrl= privateKey= etherscanApiKey= @@ -42,4 +42,4 @@ yarn deploy You should see output indicating that the `AlloraConsumer` is being deployed, and then verified on etherscan. Deployed addresses will be saved in `/deploy/deployments/.json`. If a given contract is already deployed with that deployment name, it will be skipped. Delete the deployment record `/deploy/deployments/.json` to deploy new contracts. - \ No newline at end of file + From 3c7e28bd71945f15336985678c842099400c5205 Mon Sep 17 00:00:00 2001 From: futreall <86553580+futreall@users.noreply.github.com> Date: Mon, 27 Jan 2025 18:01:37 +0200 Subject: [PATCH 2/3] Update software-upgrades.mdx Signed-off-by: futreall <86553580+futreall@users.noreply.github.com> --- 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..e2057cd 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 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. @@ -64,4 +64,4 @@ Cosmos SDK Upgrade Module: [Documentation](https://docs.cosmos.network/main/buil Cosmovisor Process Manager Software [Documentation](https://docs.cosmos.network/main/build/tooling/cosmovisor) -Cosmos SDK Gov Module: [Documentation](https://docs.cosmos.network/main/build/modules/gov) \ No newline at end of file +Cosmos SDK Gov Module: [Documentation](https://docs.cosmos.network/main/build/modules/gov) From 102bac4d87a530c9bdd54f75cba04148fdcaf1a3 Mon Sep 17 00:00:00 2001 From: futreall <86553580+futreall@users.noreply.github.com> Date: Mon, 27 Jan 2025 18:02:21 +0200 Subject: [PATCH 3/3] Update chain.mdx Signed-off-by: futreall <86553580+futreall@users.noreply.github.com> --- pages/devs/reference/params/chain.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/devs/reference/params/chain.mdx b/pages/devs/reference/params/chain.mdx index 5ac4ea9..776f755 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 then 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 @@ -160,4 +160,4 @@ Default Value: 0.0000001 The maximum length of a string to allow to store on the chain. For example, used in limiting metadata for the creation of new topics. -Default Value: 255 \ No newline at end of file +Default Value: 255