Frequently Asked Questions

How will the revised rewards be credited into the Node Operator's account?

There is no change in the methods of claiming rewards.

I am getting the following error while trying to check for the logs as provided in the image below :

This is the issue related to the Docker version as the docker installed already is not updated so in order to update the docker. Kindly follow the steps below carefully in the Terminal.

1. Command to Uninstall the docker Completely :--
   • sudo apt-get purge docker-engine
   • sudo apt-get purge docker
   • sudo apt-get autoremove
   • sudo apt-get purge -y docker-engine docker docker.io docker-ce docker-ce-cli
2. Removing the docker directories
   • sudo rm -rf /var/lib/docker /etc/docker
   • sudo rm /etc/apparmor.d/docker
   • sudo groupdel docker
   • sudo rm -rf /var/run/docker.sock
   • sudo rm -rf /var/lib/containerd
   • sudo rm -r ~/.docker
3. Checking the docker is uninstalled properly :--
   • docker
   • Once the docker is uninstalled you will get the “No such directories / No such file exist.”
4. Reinstalling the docker using the command :--
   • sudo bash bootstrap.sh
5. Checking the Docker Version
   • docker --version
   • You can check the version of the docker using the above command. If this gives you the output with version means the docker is installed successfully.
6. Check for the Docker status
   • sudo systemctl status docker
   • Make sure the status is active here.
7. Starting the Docker
   • sudo systemctl start docker
   • If the status is inactive you need to start the docker using the above command.
8. Validating the any container is running in the docker
   • docker ps
   • The above command will give you the container running status
9. Now you can run the command
   • sudo bash start-node.sh
   • This will start the node.
10. Checking for the logs
    • sudo bash check-logs.sh
    • This will give you the output of the docker running container status.

Once you are getting the right status as per the documentation in the storX you can continue with the check for the node setup in your browser URL.

What happens if a VPS gets wiped/lost, the node turns inactive but the operator can still claim (with a 1 month cool off period) ? How exactly do we risk losing the staked amount?

If the VPS is wiped/lost, This is considered as breach of service terms. So the user would have to inform us at [email protected] , Since the Storage Node was not available the users would be unable to reclaim his staking deposit

If the vps data is intact, Then he can proceed with resigning the node and that would be considered as graceful exist and he would have to wait for one month and proceed with cancellation of node, and reclaim staking deposit.

So if an incident occurs on the hardware or VPS provider side, if the operator informs support he can still claim his staked amount, even if the data has been lost ?

The nodes are paid to keep the data intact, The node operator is responsible to ensure that the data is intact and available to users. In the mainnet there is an option for users to do a graceful exit by giving a notice of 1 month so that the user data can be backed up.

Contabo had a service downtime and not data being lost. To be very specific to your case, you can still send the email to support, We can evaluate the details of the node and revert back . The incident needs to be reported and reviewed for exact resolutions.

Is it possible to change VPS providers without losing my stake position?

I am assuming that your nodes are currently in active state, Since you have not mentioned it specifically, All active nodes can migrate their existing storage nodes or can change ISP or Storage Nodes without changing their staking limit. Users would have to follow the step by step guidelines as suggested to upgrade their node. They would be promoted to provide node id details and email address during the upgrade process. Once completed your node would be live with the same id and specific staking limit.

Is it possible to create a new node (with 40k min stake) using the migration script used for migrating the existing nodes ?

Yes it is possible to create a new node with the script provided make sure you are following the criteria as mentioned in the document.

What is the cooling off / Notice period for storage nodes to resign in the mainnet?

The cooling-off period for storage nodes to resign and claim staking tokens is one month from the resignation date.

What if the storage node exits without notice on the mainnet?

If the storage node exits without providing the one-month notice specified above, the user will not be able to claim the deposit of the staking amount.

How can I check if the node is set up successfully?

Once the node is set up, you can check the status of the node setup on this link: https://farmer.storx.io/. You must provide the wallet ID in the search bar to check its status. If it is active, then it is appropriately configured.