# Update your validator node

Rewards

Upon completing this challenge, you will be rewarded 50 Desmos Tokens.

Additionally, you will also earn more tokens the longer you keep the node running. To know more about this please reference the Validators program.

When a new version of Desmos is released, all validators need to update their node so that it can keep running properly. Following you will find the guide on how you can do this making sure everything is ready for when the new chain is started.

# Quick update

The following guide is based on the genesis file we have already published on our GitHub repository. If you feel comfortable with what we have done, you can follow the below steps. On the other hand, if you want to check that what we have done is correct and not malicious, you can perform a manual update instead.

In order to perform the quick update, execute the following commands.

  1. Stop the running service:

    sudo systemctl stop desmosd
    
    1
  2. Update the Desmos binaries:

    cd ~/desmos
    git fetch -a 
    git checkout tags/v0.3.0
    make install
    
    1
    2
    3
    4
  3. Delete the current genesis.json file and download the new one:

    rm ~/.desmosd/config/genesis.json
    curl https://raw.githubusercontent.com/desmos-labs/morpheus/master/genesis.json > ~/.desmosd/config/genesis.json
    
    1
    2
  4. Reset your node to make sure everything is ready:

    desmosd unsafe-reset-all
    
    1
  5. Start your new node:

    sudo systemctl desmosd start
    
    1

Now you should be able to see your node properly syncing with the other ones by executing:

tail -100f /var/log/syslog
1

# Manual update

If you feel more comfortable into performing a manual update of your node, you can follow the updating guide on the Desmos Docs website.

Required state change

After you have exported the chain state, you are required to perform a small state change.

The state JSON file should have the following top fields:

{
  "app_hash": "",
  "app_state": { },
  "chain_id": "morpheus-1001",
  "consensus_params": { },
  "genesis_time": "2020-01-14T00:00:00Z",
  "validators": []
}
1
2
3
4
5
6
7
8

In order to make sure the migration to v0.3.0 works properly, you need to delete the consensus_params field. You should end up with a state like the following:

{
  "app_hash": "",
  "app_state": { },
  "chain_id": "morpheus-1001",
  "genesis_time": "2020-01-14T00:00:00Z",
  "validators": []
}
1
2
3
4
5
6
7

After doing so, you can proceed with the migration command.

If you do not want to export and migrate the chain state by yourself, you can download and use the genesis file of morpheus-3000 directly. Details of the genesis file can be found at the Morpheus Testnet repository.

# Keys migration required

When migrating from v0.2.0 to v0.3.0, you need to also migrate your keys to the new keystore system. In order to do so, please follow the detailed guide.

After you've updated your keys, restart your validator node by running

sudo systemctl restart desmosd
1

# Getting the reward

After you have updated your nmode, please follow the steps below to claim your reward:

  1. Create a fork of this repo inside your private GitHub profile.
    If you do not know how to do it, follow the GitHub fork guide.

  2. Pull the fork locally:

    git clone https://github.com/<your-name>/primer.git ~/desmos-primer
    cd ~/desmos-primer
    
    1
    2
  3. Make sure your fork is up to date with the Primer repository:

    git remote add upstream https://github.com/desmos-labs/primer.git
    git fetch upstream
    git rebase upstream/master
    
    1
    2
    3
  4. Create a file named after your GitHub username containing the public key of your validator:

    echo $(desmoscli keys show <your_key> --bech=val --address) >> ./phase-3/challenges/updates/<your-github-name>
    
    # Example
    # echo $(desmoscli keys show validator_key --bech=val --address) >> ./phase-3/challenges/updates/RiccardoM
    
    1
    2
    3
    4
  5. Commit the changes, push them to your forked repo and create a pull request. If you do not know how to create one, refer to the GitHub Pull Requests guide.

Last Updated: 8/10/2020, 6:36:22 AM