desmos-labs / docs Goto Github PK

https://docs.desmos.network/validators/setup
Mainnet selected :
At the end of the paragraph , "2. create validator" , link to explorer is https://morpheus.desmos.network/ instead of https://explorer.desmos.network/

Currently, since both our testnet and our mainnet had many on-chain updgrades, in order to use the state sync feature a new validator is required to know:

• which Desmos version to use when starting the sync
• the height to be used when setting up state sync

In order to make things easier, we should add inside our documentation a page (or a section) that lists all the on-chain upgrade that we had and the associated Desmos binary version that should be used to sync from that chain onward. Something like this could work (mainnet):

Also, we should explicitly tell that each time the sate sync height is changed, they need to run desmos unsafe-reset-all before trying to state sync again.

Problem:

• I was unable to find any info in the documentation pertaining to chain upgrades with cosmovisor

Tasks:

• Update the docs and include how to prepare for a chain upgrade either by relying on DAEMON_ALLOW_DOWNLOAD_BINARIES or manually building the binary beforehand and moving it in to the cosmovisor folder

While describing the command to upgrade a node to validator, both for testnet and mainnet, the following parameters appear:

--gas="auto" --gas-adjustment="1.2" --gas-prices="0.025udsm"

Probably due to a wrong setting on the automatic gas calculation, the transaction fails (in both testnet and mainnet) with the following log:

raw_log: 'out of gas in location: ReadFlat; gasWanted: 0, gasUsed: 1000: out of gas'

By removing the mentioned parameters from the call, the transaction works, both in testnet and in mainnet.

It seems as well that the correct syntax for the parameters should be --gas-adjustment=1.2 as a number instead of a string.

I noticed there are some URLs that are somewhat different from current ones, and others that I believe could be simplified. I propse to do the following changes:

Note that the types, transactions and queries one should apply to all other types as well.

Currently there is an additional part in the first two (/profiles/02-types) that I think should be deleted to make it more clear.

For queries, instead, I believe we could change the first part (/04-queries) to make it more similar to the types and transactions ones.

Algolia Search is currently not working, probably this is due to the fact that at the moment of activation the docs.desmos.network was pointing to the old docs. I've re-requested the docusearch for the new docs and currently waiting for response from them

In https://docs.desmos.network/fullnode/setup#3-get-the-genesis-file , when the user is required to verify the checksum of the downloaded file, the filepath is relative, while the file has been downloaded in ~/.desmos/config/genesis.json. Please correct the line of code into:

jq -S -c -M '' /root/.desmos/config/genesis.json | shasum -a 256

After the recent v3.0.0 Desmos testate upgrade, the current docs is now outdated.
We should update it with the relevant information for Subspaces and CosmWasm

The following is missing a closing " in https://docs.desmos.network/fullnode/cosmovisor

strings $(which cosmovisor) | egrep -e "mod\s+github.com/cosmos/cosmos-sdk/cosmovisor

The current documentation in Running a Full Node / Setup states that "To connect to an existing network, or start a new one, a genesis file is required" and provides a link to a procedure.

With the release of Desmos v2.3.1, only the state sync is supported, as the application will not be able to read the genesis file - which was created with Desmos v1.

In order to sync a node with fullsync from genesis file, the node needs to install Desmos v1.0.3 and go through all the upgrades using Cosmovisor. The latter procedure is not described, and it does not refer to v2.3.1.

It is thus necessary to make explicit in this documentation that fullsync from genesis is not possible, and, in case it is needed, to link to the specific procedure, which also will include the need for downgrade (and some possible error deriving from that) and the fundamental setup of Cosmovisor to manage the automatic chain upgrades happening while syncing the node from genesis.

On the Mainnet docs, in the Validators/Setup page, on Section 2. Create your validator, in the slice of code starting with "desmos tx staking create-validator", the following parameter appears:

--gas-prices="0.025udaric"

As it is in mainnet, should it be changed to "udsm"?

Same happens on the last TIP at the end of Section 2 (about min-self-delegation).