Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix spelling issue #101

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

fix spelling issue #101

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f3e20e8
Update deploy-consumer.mdx
futreall Jan 27, 2025
3c7e28b
Update software-upgrades.mdx
futreall Jan 27, 2025
102bac4
Update chain.mdx
futreall Jan 27, 2025
03fedef
Merge branch 'main' into main
kush-alloralabs Jan 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions pages/devs/consumers/consumer-contracts/deploy-consumer.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Create a `.env` file in the root of the project with the following structure:

```Text .env
deploymentName=<chain name string>
chainId=<chain id unt>
chainId=<chain id uint>
rpcUrl=<rpc url>
privateKey=<private key hex without '0x'>
etherscanApiKey=<etherscan api key string>
Expand All @@ -42,4 +42,4 @@ yarn deploy

<Callout>
You should see output indicating that the `AlloraConsumer` is being deployed, and then verified on etherscan. Deployed addresses will be saved in `/deploy/deployments/<deploymentName>.json`. If a given contract is already deployed with that deployment name, it will be skipped. Delete the deployment record `/deploy/deployments/<deploymentName>.json` to deploy new contracts.
</Callout>
</Callout>
4 changes: 2 additions & 2 deletions pages/devs/reference/params/chain.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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
Default Value: 255
4 changes: 2 additions & 2 deletions pages/devs/validators/software-upgrades.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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)
Cosmos SDK Gov Module: [Documentation](https://docs.cosmos.network/main/build/modules/gov)