Masternodes are required to be up and running 24/7. The network keeps track of “Proof of Service” with a “PoSe score”. The optimal score is 0, and the worst score corresponds to the number of registered masternodes. The network bans a node with a poor score after it reaches the network’s banning threshold.
If banned there are several things you can do to unban it and prevent it from happening again. Make sure the VPS is on a reliable host that is always online. Also make sure that the VPS has the required dedicated resources and specifications. Make sure that the node is synced to the right chain and the right block by logging into VPS and using syscli commands (or syscoin-cli if syscli not enabled):
If not synced, stop, restart, and reindex the node with:
Finally, and sometimes this is all that is needed: from QT console do a protx_update_service command with 5 arguments.
protx_update_service "proTxHash" "ipAndPort" "MasternodePrivateKey " ( "" "feeSourceAddress" )
Protx hash (your original masternode “provider registration transaction” or ProRegTx hash) is obtained from QT by right-clicking on the masternode and selecting Protx hash.
IP:Port is of the VPS.
You can retrieve the masternode private key from the VPS using this command in VPS:
cat /home/syscoin/.syscoin/syscoin.conf | grep masternodeblsprivkey
The next argument is the masternode payout address. To keep it the same, use “”, to change it, insert the new payout address.
Lastly, the fifth argument is the syscoin address in QT that will fund the transaction. The fee is very small (typically less than 0.00001 sys) but this address needs to have funds in it (it cannot be zero), and also, this address cannot have too many past transactions (more than a few hundred) or the protx_update_service transaction will be rejected as too large (too many inputs). If left out, this argument defaults to the payout address, instead of to the orginal feesourceaddress, so it is best to go into coin control in QT and select a small, funded change address with minimal transactions on it.
DO NOT SHARE MASTERNODE PRIVATE KEYS WITH ANYONE. DO NOT GRANT ACCESS TO VPS LOGIN OR MASTERNODEBLSPRIVKEY COMMAND TO ANYONE. DO NOT USE REGULAR DISCORD DM FOR SUPPORT, AS THESE ARE ALL SCAMMERS IMPERSONATING ADMIN ACCOUNTS. ONLY USE THE CREATE TICKET SYSTEM FOR SUPPORT.
NOTE: IF YOU COPY-PASTE COMMANDS, BE SURE TO CONVERT THE DOUBLE QUOTES FROM THE STYLIZED FORMAT IN THIS POST TO PLAIN UNICODE (U+0022) DOUBLE QUOTES IN YOUR TEXT EDITOR FIRST, OR THE COMMANDS MAY NOT WORK.