Releases: pokt-network/pocket-core
BETA-0.9.2
BETA-0.9.2
This version brings one new feature and two new endpoints to Pocket Core:
New feature: LeanPocket
LeanPocket is a configuration that enables multiple Pocket instances to run on a single process, allowing node runners to consolidate resources, resulting in better scalability and reduced hardware costs.
-
Create a new
lean_nodes_keys.json
file inside your Pocket configuration directory (typically.pocket
). -
Format the file with a JSON array of your node's private keys:
[
{ "priv_key": "<PRIVATE_KEY_1>" },
{ "priv_key": "<PRIVATE_KEY_2>" }
]
- Set/update your validators:
pocket accounts set-validators <path/to/lean_nodes_keys.json>
-
Edit your node's
config.json
file to addlean_pocket: "true";
in thepocket_config
block. -
If you run a script that starts the Pocket service, add
--keybase=false
to thepocket start
command. -
Edit your proxy settings such that the
/v1
endpoint is publicly accessible for every one of your nodes. -
Restart your Pocket service, making sure to add the
--keybase=false
option.
Learn more: https://docs.pokt.network/node/leanpocket/
New API endpoints
-
/v1/query/unconfirmedtxs: Returns all unconfirmed transactions in the mempool for a given node. Transactions are decoded following the same format as blocktxs (hash + stdTx). Try it out: https://docs.pokt.network/api-docs/pokt/
-
/v1/query/unconfirmedtx: Returns an unconfirmed transaction in the mempool, specified by the transaction hash. Try it out: https://docs.pokt.network/api-docs/pokt/
Update your node
To update your node to the latest version, follow instructions here: https://docs.pokt.network/node/update
RC-0.9.1.3
RC-0.9.1.3
-Fix for NCUST activation with caching
sleep until 10/27/2022 noon (EST)
RC-0.9.1.2
RC-0.9.1.2
-Fix for NCUST activation with caching
RC-0.9.1.1
RC-0.9.1.1
This release includes future consensus rules 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 (TBD) in an upcoming upgrade transaction, so please update as soon and safely as possible to avoid your node falling out of consensus when the upgrade hits.
Changes Included in this release:
- This release fixes an issue with the Relay Reward logic found here.
This bug prevents Non-Custodial staking nodes to receive rewards when PIP-22 is enabled, failing with the following error: no validator found for address
.
Upgrade:
(Same as previous releases)
Shutdown Pocket Core
!!! Ensure golang version 1.17 !!! or > golang upgrade
Startup script linux users might find this useful (BenVan's Validator Script Only)
sudo apt-get update
g install 1.17
Build from source 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.9.1.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.9.1.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.9.1.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.9.1.1
or
docker pull poktnetwork/pocket:RC-0.9.1.1
Depending on which of the 2 Docker images you want to use.
BETA-0.9.1.1
This release fixes an issue with the Relay Reward logic found here.
This bug prevents Non-Custodial staking nodes to receive rewards when PIP-22 is enabled, failing with the following error: no validator found for address
.
Previous beta was not able to sync from scratch and its use is not recommended.
BETA-0.9.1
This release fixes an issue with the Relay Reward logic found here.
This bug prevents Non-Custodial staking nodes to receive rewards when PIP-22 is enabled, failing with the following error: no validator found for address
.
RC-0.9.0
RC-0.9.0
This release includes future consensus rules 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 (TBD) in an upcoming upgrade transaction, so please update as soon and safely as possible to avoid your node falling out of consensus when the upgrade hits.
Nodes Running BETA-0.9.0 are recommended to switch to RC-0.9.0 version.
Changes Included in this release:
- Mempool Refinements.
- Implementation of PIP22 (Stake Weighted Servicer Rewards)[RSCAL][VEDIT]. (@Andrew-Pohl)
- Customizable Max Block Size bytes and new tendermint evidence age.[BLOCK].
- New RPC endpoint for querying accounts (.../v1/query/accounts).
- Backport tendermint #6068 (terminate broadcastEvidenceRoutine when peer is stopped).
We would like to thank all external contributors who have contributed to this release in any shape or form, from ideation to reporting bugs and helping with QA efforts. Special shout out to @jorgecuesta , @rBurgett, @Andrew-Pohl, @PoktBlade, @DragonDmoney !
Upgrade: (Same as previous releases)
Shutdown Pocket Core
!!! Ensure golang version 1.17 !!! or > golang upgrade
Startup script linux users might find this useful (BenVan's Validator Script Only)
sudo apt-get update
g install 1.17
Build from source 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.9.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.9.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.9.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.9.0
or
docker pull poktnetwork/pocket:RC-0.9.0
Depending on which of the 2 Docker images you want to use.
BETA-0.9.0
BETA-0.9.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.
Upgrade: (Same as previous releases)
-
Shutdown Pocket Core
-
!!! 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
-
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 exceptBETA-0.9.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.9.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.9.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.9.0
or
docker pull poktnetwork/pocket:BETA-0.9.0
Depending on which of the 2 Docker images you want to use.
RC-0.8.3
RC-0.8.3
Changes:
- Patch an indirect dependency for YAML CVE-2022-28948.
- Enforces config.json checks for mempool and tx indexer.
- Minor Bug Fixes
- Allow read only config.json/chains.json (@lander2k2)
- Documentation fixes.
We would like to thank all external contributors who have contributed to this release, this time a special shout out to @msmania @lander2k2 @immunity20
Upgrade: (Same as previous releases)
-
Shutdown Pocket Core
-
!!! 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
-
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 exceptRC-0.8.3
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.8.3
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.8.3
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 versionOutput will be
RC-0.8.3
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.8.3
or
docker pull poktnetwork/pocket:RC-0.8.3
Depending on which of the 2 Docker images you want to use.
RC-0.8.2
RC-0.8.2
This version include changes to the CLI commands (staking/unstaking/unjail):
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>
NOTE : The legacy stake command pocket nodes stake <fromAddr> <amount> <relayChainIDs> <serviceURI> <networkID> <fee>
is not available on this release.
Please use pocket nodes stake custodial <fromAddr> <amount> <relayChainIDs> <serviceURI> <networkID> <fee> true
as a replacement.
For more info on the CLI changes check This
Also check some of the New Features Here
Upgrade: (Same as previous releases)
-
Shutdown Pocket Core
-
!!! 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
-
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 exceptRC-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/RC-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
RC-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 versionOutput will be
RC-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:RC-0.8.2
or
docker pull poktnetwork/pocket:RC-0.8.2
Depending on which of the 2 Docker images you want to use.