BETA-0.8.2

BETA-0.8.2

NOTE:
This is a BETA release. Please ensure you deploy it to your fleet at a slow pace. We recommend you update a small batch of nodes first and increase your deployment over time as the certainty of stability in your environment cements itself. If you run into issues, please communicate with us via discord so that we can work together to gather information and face any edge cases that escaped our quality assurance efforts.

Upgrade: (Same as previous releases)

1. Shutdown Pocket Core

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

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

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 BETA-0.8.2

   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/BETA-0.8.2
   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 BETA-0.8.2

   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 BETA-0.8.2

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

   docker pull poktnetwork/pocket-core:BETA-0.8.2

   or

   docker pull poktnetwork/pocket:BETA-0.8.2

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

RC-0.7.1.1

Closes issue #1414

BETA-0.8.1

### BETA-0.8.1

PLEASE USE:
https://github.com/pokt-network/pocket-core/releases/tag/BETA-0.8.2

NOTE:
This is a BETA release. Please ensure you deploy it to your fleet at a slow pace. We recommend you update a small batch of nodes first and increase your deployment over time as the certainty of stability in your environment cements itself. If you run into issues, please communicate with us via discord so that we can work together to gather information and face any edge cases that escaped our quality assurance efforts.

In continuation with the 0.8.x release preparations and your feedback, we have prepared this BETA-0.8.1,
changes for this version include changes to the CLI staking commands:

now we have the two options for staking clearly differentiated, each with its own command.

-pocket nodes stake custodial <fromAddr> <amount> <RelayChainIDs> <serviceURI> <networkID> <fee> <isBefore8.0>

-pocket nodes stake non-custodial <operatorPublicKey> <outputAddress> <amount> <RelayChainIDs> <serviceURI> <networkID> <fee> <isBefore8.0>

Check some of the New Features Here

As always, thanks again for your collaboration and feedback.

---

This Upgrade is in line with PIP-9 and enables the consensus rule change described (including the non-custodial operator address) with an upgrade Tx sent by the DAO, for more information about the rule change check this: PIP-9.

This means the change is backward compatible but includes a future consensus rule change, that when activated will require all nodes on the network to be running at least this version of the software to be able to continue to be part of the network.

The consensus rule change is activated after the chain reaches a specific height designated by the DAO in an upcoming upgrade transaction, so please update as soon as possible to avoid your node falling out of consensus when the upgrade hits.

This release includes changes to CLI commands and RPC routes in preparation for the new consensus rules.

Please check some of the changes below:
https://docs.pokt.network/core/specs/cli/node

---

Upgrade: (Same as previous releases)

1. Shutdown Pocket Core

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

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

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 BETA-0.8.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/BETA-0.8.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 BETA-0.8.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 BETA-0.8.1

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

   docker pull poktnetwork/pocket-core:BETA-0.8.1

   or

   docker pull poktnetwork/pocket:BETA-0.8.1

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

BETA-0.8.0

BETA-0.8.0

NOTE:
This is a BETA release. Please ensure you deploy it to your fleet at a slow pace. We recommend you update a small batch of nodes first and increase your deployment over time as the certainty of stability in your environment cements itself. If you run into issues, please communicate with us via discord so that we can work together to gather information and face any edge cases that escaped our quality assurance efforts.

This Upgrade is in line with PIP-9 and enables the consensus rule change described (including the non-custodial operator address) with an upgrade Tx sent by the DAO, for more information about the rule change check this: PIP-9.

This means the change is backward compatible but includes a future consensus rule change, that when activated will require all nodes on the network to be running at least this version of the software to be able to continue to be part of the network.

The consensus rule change is activated after the chain reaches a specific height designated by the DAO in an upcoming upgrade transaction, so please update as soon as possible to avoid your node falling out of consensus when the upgrade hits.

This release includes changes to CLI commands and RPC routes in preparation for the new consensus rules.

Please check some of the changes below:
https://docs.pokt.network/core/specs/cli/node

New Features Guide [----to be included here check back soon---]

Full list of fixes and enhancements available when the release is vetted and we bump it to RC.

Thank you for your collaboration.

Upgrade: (Same as previous releases)

1. Shutdown Pocket Core

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

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

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 BETA-0.8.0

   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/BETA-0.8.0
   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 BETA-0.8.0

   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 BETA-0.8.0

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

   docker pull poktnetwork/pocket-core:BETA-0.8.0

   or

   docker pull poktnetwork/pocket:BETA-0.8.0

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

RC-0.7.1

RC-0.7.1

Small Release to Fix an issue when syncing from scratch at height 28153. see issue #1382

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.7.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.7.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.7.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.7.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.7.1

   or

   docker pull poktnetwork/pocket:RC-0.7.1

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

RC-0.7.0.1

Rerelase of RC-0.7.0, the previous release reported Beta version on CLI/RPC.

RC-0.7.0.1

This Upgrade is in line with PIP-7 and enables the validator/servicer split with an upgrade Tx sent by the DAO,
for more information check this: PIP-7.

This change is backwards compatible but includes a future consensus rule change.

The consensus rule change is activated after the chain reaches a specific height designated by the DAO in an upcoming upgrade transaction, so please update as soon as possible to avoid your node falling out of consensus when the upgrade hits.

Upgrade height: 45353

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.7.0.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.7.0.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.7.0.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.7.0.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.7.0.1

   or

   docker pull poktnetwork/pocket:RC-0.7.0.1

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

4. Enable the Cache:
   The cache is opt-in only but highly recommended. 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

RC-0.7.0

RC-0.7.0

This Upgrade is in line with PIP-7 and enables the validator/servicer split with an upgrade Tx sent by the DAO,
for more information check this: PIP-7.

This change is backwards compatible but includes a future consensus rule change.

The consensus rule change is activated after the chain reaches a specific height designated by the DAO in an upcoming upgrade transaction, so please update as soon as possible to avoid your node falling out of consensus when the upgrade height is reached.

Upgrade height: TBD

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.7.0

   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.7.0
   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.7.0

   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.7.0

   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.7.0

   or

   docker pull poktnetwork/pocket:RC-0.7.0

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

4. Enable the Cache:
   The cache 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

BETA-0.7.0

Come Back Later
WIP

RC-0.6.4.1

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

RC-0.6.4

NOTE:
RC-0.6.4

Thanks to all the node runners that helped with Beta testing all the previous beta releases [BETA-0.6.3.8, BETA-0.6.3.9, BETA-0.6.3.10, and BETA-0.6.3.11].

This release is basically the stable bump from the latest beta.
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

   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
   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

   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

   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

   or

   docker pull poktnetwork/pocket:RC-0.6.4

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

4. Enable the Cache:
   The cache is the centerpiece for this release, 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