pokt-network/pocket-core RC-0.6.4.1

on GitHub

Minor release.

Solves an issue for nodes syncing from scratch on Testnet/Mainnet.
See the changelog for more details.

Thank you again for your collaboration.

Upgrade: (Same as previous releases)

1. Shutdown Pocket Core

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 anything except RC-0.6.4.1

   To grab the latest packages and tags we are going to clean the cache, swap branches to the latest tag using:
   go clean --cache
git pull
git checkout tags/RC-0.6.4.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.4.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.4.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.4.1

   or

   docker pull poktnetwork/pocket:RC-0.6.4.1

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

4. Enable the Cache:
   The cache is the centerpiece for this release (RC-0.6.4.X), and is opt-in only. It can be enabled by using the flag --useCache in the start command. It increases the use of RAM to reduce the use of CPU. Make sure to have around 512MB of RAM above the normal usage. When running in a container, ensure a strict RAM limit, otherwise consumption will rise until the orchestrator resets the container. Startup times can increase significantly depending on your hardware. Please allow time for the cache to warm.

Example usage with cache:
pocket start --mainnet --useCache