Pocket Node Setup
Last updated
Last updated
An account is needed to participate at any level of the network.
Alternatively, you can create your account using the Wallet app, then use the encrypted import command to import the account into your node environment:
Backup your private key to an encrypted and ASCII armored json file, to the specified --path , using the secure export command. After you hit enter, you will be prompted for the decrypt passphrase and an encryption passphrase for the exported account. You will also have the option to add a hint to help remember your passphrase.
Do not use your node's account as your personal account address. Since the node's private key is stored in plaintext on the server, the key is as secure as your server is. Regularly sweep your node's rewards and transfer them to a more secure account stored offline.
For more details on securely managing your POKT accounts, see here:
To stake a Validator in Pocket Network, the account must have a balance above the minimum stake:
15,000 POKT or 15,000,000,000 uPOKT
The absolute minimum node stake (15,000 POKT) is not practical for real-world usage. 15,100 is a reasonable buffer against operational slashes which can occur on seemingly properly configured nodes as well as misconfigured and misbehaving ones.
Send POKT with the following command:
You won't be able to send POKT using your CLI until you have a Validator set up. Until then, you can use the Wallet app.
If you're using the testnet, you can fund your account using the Testnet Faucet.
Check that it worked with pocket accounts get-validator
A Relay Chain is the blockchain that Validators are running full nodes for in service of Applications. Apps access Relay Chains through the serviceURI, the endpoint where Validators publicly expose the Pocket API.
RelayChainIDs can be found here.
Genesis files can be found here:
The appropriate genesis file should be placed at $HOME/.pocket/config/genesis.json
Test that your node is configured correctly by simulating a relay.
Then send a curl request to your validator URL http://<your node>:<your pocket rpc port>/v1/client/sim to test if your node responds.
200 OK – your transaction has gone through
400 Bad Request – you either have incorrect/missing parameters in the request or bad formatting in the data field
Finally, stop your node. If you don't, you'll be leaving --simulateRelay running, which means anyone will have unfiltered access to your node.
Downloading from the latest snapshot will drastically shorten the time it takes to sync the blockchain. The easiest way is by downloading with wget and extracting the archive as it downloads.
Other options for downloading the latest snapshot can be found in the pocket-snapshotter repo.
See the section on seeds for more details.
Ensure the node is all the way synced before proceeding to the next step.
Stake the account to participate in the Network as a Validator. Staking a Validator locks up POKT tokens that can be burned as a security mechanism for bad acting.
Read more about custodial versus non-custodial staking.
You should leave 1 POKT liquid (unstaked) to pay the transaction fees for your node's claim and proof transactions.
All node runners must always maintain a liquid (unstaked) balance of at least 0.02 POKT in order to submit the claim and proof transactions (which each have a transaction fee of 0.01 POKT) that generate their rewards. If a node successfully submits both the claim and proof, they will earn enough POKT to submit the next claims and proofs, and so on. However, if a node falls below a liquid balance of 0.02 POKT, their revenue will be halted.
Claim transactions have 3 sessions, the ClaimSubmissionWindow, to be successfully submitted after the conclusion of the session in which the work was done, otherwise they are lost. If a claim transaction fails, Pocket Core will auto-repeat the transaction once in each new session, until the claim is lost. This means your node will automatically take 3 attempts to submit the claim. There is a claim submission window because the global secret key that determines the required proof leaf is revealed once that window closes. Extending the claim submission window would delay the time at which the corresponding proof can be sent and rewards earned.
If you manage to successfully submit the claim transaction, you then have 120 blocks, the ClaimExpiration period, to submit the corresponding proof transaction, otherwise the pending claim expires. There is a claim expiration date because otherwise the claims would remain in the state and bloat the blockchain.
Bad Behavior Warning: Pre-staking
Pre-staking is the act of a node runner staking on a RelayChainID prior to spinning up the RelayChain node. This behavior has an extremely negative impact on the quality of service for new chains due to apps being matched in sessions with Pocket nodes that don't actually have RelayChain nodes connected to them. If you do this, your node will be challenged and slashed. You should always deploy your RelayChain node and simulate relays before staking your Pocket node for the RelayChainID.
If your stake falls below 15,000 POKT your node will be force-unstake burned. We recommend having a buffer above the 15,000 minimum (e.g. 15,100-16,000) so that minor slashing doesn't result in loss of the entire stake.
🏆 Achievement Unlocked
If you staked your node successfully, you just earned your first trophy. See here to find out how earning more trophies will ultimately earn you a vote in our DAO.
Each release may have specific modifications you need to make. This is just a general guideline for the steps you'll typically take to upgrade your node. Check the release notes for release-specific details.
Stop your Pocket Core instance running by submitting the shutdown command.
Once you shutdown Pocket Core, you will have 4 blocks (60 minutes) to complete the upgrade and start Pocket Core again before your node gets jailed for downtime.
Backing up your blockchain data will ensure a faster resync when you restart your node.
Navigate inside your $HOME/.pocket/ dir and save data/ (the entire directory):
In the event of a corrupted database you can delete the bad data rm -r ~/.pocket/data and replace it with your backup cp -r ~/backup/data ~/.pocket/data.
If you don't have a backup, a temporary backup datadir may be provided alongside a release.
Check your golang version. The release notes will specify which version it should be.
If you need to upgrade, use this guide.
Alternatively, if you use g, you can just run
Navigate into pocket-core directory
Checkout the latest release
Rebuild the binary
Pull the latest tap
Pull the latest container image
Run the update-configs command, which creates a new config file (DATADIR/config/config.json) and backs up the old config file (DATADIR/config/config.json.bk).
You'll need to manually compare your backup file with the new file to copy over your personal config details.
Start pocket running again.
You can earn a vote in the DAO and help shape the future of Pocket Network, including deciding which ecosystem tooling our treasury supports and how we configure important on-chain parameters such as node revenue.
Once you've staked your node successfully, join our Discord and report this in the 🏆trophies channel.
This is your first trophy on the path to earning a vote in the DAO. Learn more on the Node Runners page.