Frequently asked questions (FAQ)
JPool Delegation Program
How to join JPool Delegation Program
To join JPool Delegation Program, you must make sure your validator meets the delegation criteria below. The joining process itself is automatic and requires no manual intervention.
Note: For details on how to bootstrap your validator using SVT, see Connect an existing validator in the SVT documentation.
Criteria for your validator
Your validator will be considered eligible for the JPool Delegation Program, if it meets the following criteria:
In Top 300 by average APY for the last 10 epochs (if not, consider reducing commission).
Active for at least 10 epochs.
Not a member of the Superminority group.
Not run by an operator of a Superminority validator.
Information, including a name, a logo, and a website, is published at validators.app (for details, see Published Information in the Getting Started section at validators.app).
Not flagged as Suspicious activity with vote accounts by validators.app.
Not operated by a person who is running more than one validator node (so-called "Sybil").
Note: You can quickly check if your validator meets the delegation criteria using the Analytics feature of our Smart Validator Toolkit (SVT).
Validator node
After I start my validator, it seems to be out of sync with the network. How do I make sure it's catching up?
If you find that your validator is out of sync with the network after starting it, you can use the solana catchup command to ensure that it catches up with the cluster. Run the following command to monitor your validator's progress during this process:
sudo -u solana /home/solana/app/active_release/bin/solana catchup {pathto}/validator-keypair.json --our-localhost --follow --logKeep in mind that catching up might take some time for your validator. During this time, it won't be able to successfully vote or accept delegated stake. If you observe that the cluster's slot count is increasing faster than your validator's, it could mean that your validator may never catch up, which is usually a sign of a networking problem between your validator and the cluster.
I lost access to my wallet. What will happen to my validator node? How do I manage it with SVT again?
If you lost the password and seed phrase for your crypto wallet, unfortunately, it's gone forever. On the bright side, this will not affect your validator node. It will continue running on your server as usual.
To regain access to it, you need to create another wallet and connect your validator node in SVT (see Connect an existing validator).
I can no longer access the device (or browser) that I used to manage my validator node through SVT. What do I do?
If you try to use another device, or even browser, to manage your validator node through SVT, you won't succeed, because you won't have a proper device key.
Device key is used to authorize user devices with the Agent so it can execute commands coming from them. It's generated for a specific device, or even a specific browser, and stored locally.
To authorize a new device or browser, you need to remove the existing channel of communication with the Agent (see Remove the communication channel), then create a new channel and install the Agent with the new channel (see Set up a communication channel and Install the Agent, respectively).
I want to use another device or browser to manage my validator node in SVT. Can I do it?
If you try to use another device, or even browser, to manage your validator node through SVT, you won't succeed, because you won't have a proper device key.
Device key is used to authorize user devices with the Agent so it can execute commands coming from them. It's generated for a specific device, or even a specific browser, and stored locally.
As of now, there's no quick way to authorize a new device with the Agent. We are currently working on a user-friendly solution that will allow you do that based on your wallet address.
The only workaround available today is described in the answer to this question:
Agent
General guidance
If you encounter an error, look it up in your log via CLI or Dozzle (see View real-time logs for details)—it may be something simple and quickly resolvable, for example a private key stored in a wrong folder. In this specific case, you will see this error message if you use CLI:
Or this one if you use Dozzle:
Questions & answers
I can't send a command to the Agent through the Messenger channel. Is there other way to execute it?
You can generate a command and execute it manually. For details, please refer to Execute commands manually.
I can't deploy the Agent. The server says it needs curl installed first. How do I install it?
Just run these two commands in your CLI:
sudo apt update
sudo apt install curlI reinstalled my server's operating system and now all commands that I send to the Agent fail. How can I fix it?
The Agent was removed from your server when you reinstalled its operating system. To be able to manage your node through the Agent again, complete the steps in Connect an existing validator.
I've pushed the Run Command button to send a command to the Agent but nothing happened. Now the loader keeps spinning and the command history doesn't show that the Agent has started to execute my command. What do I do?
First of all, try to refresh the page. If it doesn't help, open your CLI and run docker restart svt-agent on your server to restart the Agent. After that, make another attempt at sending the command.
Last updated
