pocketd CLI Installation
curl -LO "https://github.com/pokt-network/poktroll/releases/latest/download/pocket_$(uname | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz"Extract to /usr/local/bin:
sudo tar -zxf "pocket_$(uname | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" -C /usr/local/binMake it executable:
sudo chmod +x /usr/local/bin/pocketdCheck version:
pocketd versionAdditional references and links:
Pre-built binaries can be found on the releases page: https://github.com/pokt-network/poktroll/releases
Latest release: https://github.com/pokt-network/poktroll/releases/latest
From Source (danger zone)
Do not continue unless you're a 🚀👨💻💎
For ADVANCED users only. Requires developer tools.
Installation dependencies
https://go.dev/doc/install (Go v1.23+)
https://www.gnu.org/software/make/ (Make)
https://docs.ignite.com/welcome/install (Ignite CLI)
Build from source
Clone the repository:
git clone https://github.com/pokt-network/poktroll.git pocket
cd pocketBuild the dependencies:
make go_developThen, you have a few options:
When you're done, verify the installation:
pocketd version
pocketd --helpBuilding Release Binaries From Source
The official binaries in our GitHub releases are built using this GitHub workflow: https://github.com/pokt-network/poktroll/actions/workflows/release-artifacts.yml
You can build the release binaries locally for all CPU architectures like so:
make ignite_releaseWindows (why!?)
Native Windows installation is not supported.
Use Windows Subsystem for Linux (WSL): https://docs.microsoft.com/en-us/windows/wsl/install
Follow the Linux install instructions above.
Publishing a new pocketd release
pocketd releaseThis section is intended for core protocol developers only. It is intended only for dev releases of the pocketd CLI. If you are publishing an official protocol upgrade accompanied by a CLI update, visit the release procedure docs: https://dev.poktroll.com/develop/upgrades/upgrade_preparation
Create a new dev or rc git tag
dev or rc git tag# Clone the repository if you haven't already
git clone [email protected]:pokt-network/poktroll.git poktroll
cd poktroll
# Create a new rc tag from `main` or `master` and follow the on-screen instructions
make release_tag_rc
# OR
# Create a new dev tag from any branch and follow the on-screen instructions
make release_tag_dev
# Push the tag to GitHub
git push origin $(git tag)Wait for the release artifacts to be built (5 - 20 minutes)
The release artifacts workflow https://github.com/pokt-network/poktroll/actions/workflows/release-artifacts.yml will automatically build and publish the release artifacts to GitHub. The artifacts will be attached as an Asset to your release once the workflow completes.
Was this helpful?
