They have different collateral requirements and get rewarded differently. Masternodes require a 1000 SPK collateral. Guardian nodes require a 25,000 SPK collateral and are paid 26.75 times more often than masternodes, which amounts to 7% more payments than the equivalent amount of masternodes.
Masternodes are in a “payment queue”, where each masternode gets paid when it is at the beginning of the queue, then get sent back at the end. When a masternode is started, it is put at the end of that queue. The queue is composed of all masternodes and guardians. Guardians are equivalent to 26.75 masternodes. So, for example, if the queue contains 500 masternodes and 100 guardian nodes, it translates to 500 + 2675 = 3175 masternodes.
Each block is mined on average every 2 minutes, which means there are theoretically about 720 blocks mined per day. When first started, a masternode must wait to get paid for a time (in minutes) at least equal to: number of masternodes in queue * 2.6. In our example, this means 3175 * 2.6 = 8,255 minutes, or roughly 5.75 days.
After this first payment, the masternode will be in the normal queue cycle. So for our example, 3175 * 2 minutes, roughly 4.4 days. Guardian nodes get paid 26.75 times faster, so about 5 times a day.
As the mining rate varies greatly, more often than not, far less blocks are mined per day than the expected 720, yielding longer delays before earning rewards. You can see the actual number of blocks mined per day in the explorer.
You can check the number of active masternodes and guardians by typing the following commands in the console of your control wallet: masternode count or guardian count
No, and it won’t for the foreseeable future.
Sparks is a Proof of Work coin. The algorithm used is Neoscrypt.
We are still debating whether it would be good to do so.
At first nothing, just wait. This happens because sometimes a block must be mined for your wallet to start synchronizing, but the blockchain is stuck for lack of mining power. As soon as a block is found, your wallet will start synchronizing.
If you see the blockchain moving (on the explorer for instance), and your wallet still does not synchronize, then check if it has any peers (go to Tools > Peers list). If you have no peers, you might have an old version of the wallet. Download the latest version from github.
Yes, but you need a different IP address per masternode. You will need to create a different user for each masternode and add the following lines in each sparks.conf file :
Alternately, you could use the same user, but would then be required to launch each masternode with a “- datadir=<sparkscore-XX>” parameter.
This happens because the available mining power (also called the hashrate) is not high enough to find new blocks quickly. The mining difficulty varies with each block, depending on the time the previous block was found, and unfortunately, lots of pools of miners are set up to mine the most profitable coin at any given time, so that they will mine a coin until difficulty becomes high, then go mine another coin. Difficulty stays high, but mining power drops, so it becomes much more difficult to find a new block, which results in big delays. This will eventually diminish as Sparks rises in value and more stable miners join.
You can help mine Sparks by joining our pool: mining.sparkspay.io
The easiest way is to unlock the collateral. This is done by going on the Send tab and clicking on the Inputs… button in the top left corner. If you do not see that button, then you must activate it by going in Settings > Options… then Wallet tab and check the Enable coin control features box.
Once in the coin selection window, find the collateral address with the locked amount (has a little closed lock next to the amount), right-click the amount and click on “Unlock unspent”. You will now be able to spend that collateral.
Another way is to edit the masternode.conf file and delete the masternode line. You will have to restart your wallet afterwards.
First, check your firewall. Is it enabled? If so, is port 8890 opened? If you have a VPS with Ubuntu, check this with the following command:
sudo ufw status
This should show you a list of lines, one of which should be: 8890/tcp ALLOW. If it isn’t there, you can add it by typing:
sudo ufw allow 8890/tcp
If firewall is ok, check CPU load, memory and storage space. For Ubuntu, we recommend using htop (type sudo apt-get install htop if not installed).
If any of those parameters are overloaded, you need to fix the problem:
- CPU: kill unnecessary processes
- Memory: if possible, add swap space
- Storage: delete unnecessary files (notably logs, and especially /var/log/journal logs)