RC-0.6.1

• Fixed RelaysToTokensMultiplier bug
• Added utility CLI command to convert evidence from amino to protobuf
• Updated RPC spec to include stdTx
• Return Dispatch for certain failed relay codes to save a hop on client side
• Fix simulate relay to use basic auth
• Updated User Guide to use RC-0.6.0
• Added unsafe delete command to the keybase
• Added optional flag to bypass interactive prompt for commands that require passphrase input

Upgrade

1. Shutdown Pocket Core (NOTE: Validators will not be jailed until they have been offline for 6 blocks. You have more than one hour to complete this upgrade. 15 to 30 minutes should be sufficient.)

2. !!! Ensure golang version 1.16 !!! or > golang upgrade NOTE: This version is new so please ensure you are on 1.16 or later

   # Startup script linux users might find this useful (BenVan's Validator Script Only)
   sudo apt-get update
   g install 1.16
   

3. Build from source, Homebrew or Docker:

   To build the latest binary from source, follow these steps:

   Navigate into your pocket-core directory:
   Example: cd ~/go/src/github.com/pokt-network/pocket-core

   Enter: pocket version
   You should see: RC-0.5.2.10 (or older)

   To grab the latest packages and tags we are going to swap branches to the latest tag using:

   git pull
   git checkout tags/RC-0.6.1
   Once you checked out the latest tag and branch, we are going to rebuild the binary by entering in:
   go build -o $GOPATH/bin/pocket ./app/cmd/pocket_core/main.go

   After it builds, make sure you are on the latest release version by entering in:
   pocket version

   Output will be RC-0.6.1

   If you built your binary using Homebrew, follow these steps to upgrade your binary:

   In a terminal window, we are going to pull the latest tap by entering:
   $ brew upgrade pokt-network/pocket-core/pocket

   After it builds, make sure you are on the latest version by entering in:
   pocket version

   Output will be RC-0.6.1

   For individuals using Docker, all you will need to do to get the new container image is run:

   docker pull poktnetwork/pocket-core:RC-0.6.1

   or

   docker pull poktnetwork/pocket:RC-0.6.1

   Depending on which of the 2 Docker images you want to use.

4. Upgrade your config.json
   NOTE: There are no config changes from RC-0.6.0
   Use the default config for all options (except unique configurations like moniker, external addr, etc).

   You have two options:
   OPTION 1 (RECOMENDED)

   Run pocket util update-configs command (creates a new config file and backs up old config file)

   In order to use the most performant values, you will need to upgrade your config.json file in within your /config directory.
   The following example assumes your config.json to be ~/.pocket/config, but feel free to swap out your actual with the location in your system.
   Run the pocket util update-configs command to backup your old config and generate a new default one.
   Manually go over your /config/config.json.bk file and update your new /config/config.json with any custom changes that you use.

   OPTION 2

   Backup and remove your existing config.json file (mv ~/.pocket/config/config.json ~/.pocket/config/config.json.bk)

   Execute a CLI command, (this will cause a default config.json to be created), then update the custom configurations.
   Manually go over your datadir/config/config.json.bk file and update your new datadir/config/config.json with any pertinent values such as moniker, external addr, etc.

5. Delete Session.DB before upgrading

   • rm -rf <datadir>/session.db

6. NOTE: Step 6 IS ONLY NEEDED IF RUNNING VERSION EARLIER THAN RC-0.6.0
   Convert pocket_evidence.DB before upgrading

   • pocket util convert-pocket-evidence-db

   Successfully Converted Pocket Evidence DB

   If the command Failed and success message not shown, delete pocket_evidence.DB

7. NOTE: Step 7 IS ONLY NEEDED IF RUNNING VERSION EARLIER RC-0.5.2.9 OR DB CORRUPTED
   GoLevelDB is the only supported database from RC-0.5.2 onward

   • If previously using CLevelDB, users might experience incompatibility issues due to known incompatibilities between the two
   • PNI temporarily will provide a backup datadir to download to avoid syncing from scratch:
     22K .zip
   • After uncompressing theses files, place the contents in the <datadir>/data folder