Paxi Binary Upgrade
Tip
Looking to install a new node from scratch? Visit the Validator Installation Guide.
Upgrade to v1.0.6
| Target Block | Proposal ID | Release Version | Binary Daemon |
|---|---|---|---|
816000 | #1 | v1.0.6 | paxid |
Download & Extract Binary
cd $HOME
mkdir -p paxi
cd paxi
wget https://github.com/paxi-web3/paxi/archive/refs/tags/v1.0.6.tar.gz
tar -xzvf v1.0.6.tar.gz
cd paxi-1.0.6
make installCheck new binary version
$HOME/paxid/paxid versionStart a new tmux session
tmux new -s paxi-upgradeRun the auto-upgrade script.
⚠️ NOTE: Make sure you adjust the following according to your setup:
- RPC port: use your own RPC endpoint after -r (default is http://localhost:26657)
- API port: use your own REST API endpoint after -a (default is http://localhost:1317)
UPGRADE_SCRIPT="https://raw.githubusercontent.com/astrostake/scripts/refs/heads/main/upgrade_binary.sh"
curl -sL $UPGRADE_SCRIPT | bash -s -- \
-b "paxid" \
-t "816000" \
-n "$HOME/paxid/paxid" \
-p "$HOME/.paxi" \
-r "http://localhost:11657" \
-i "1" \
-a "http://localhost:11317" \
-d "https://discord.com/api/webhooks/xxx/yyy" \ # optional
--progress-interval 0Flag explanation:
| Flag | Name | Description |
|---|---|---|
-b | binary-name | Name of the running daemon (e.g. paxid) |
-t | target-block | Block height at which the upgrade should happen |
-n | new-binary-path | Full path to the new binary |
-p | install-path | Path where the current binary is installed (default: $HOME/go/bin) |
-r | rpc-url | RPC endpoint used to monitor current block height |
-i | proposal-id | (Optional) Proposal ID to validate governance status |
-a | api-url | (Optional) API endpoint used to fetch proposal status |
