Note: You need to change the token both on your masternode as well as on your local installation of Syscoin-Qt. If you have multiple masternodes, you need to use different voting tokens for each one.
1. Create a new control token
Start Syscoin-Qt
Open the console: Window -> Console
Type: masternode genkey and press Enter for each masternode
Copy the output of the command
2. Replace the control token in your local Syscoin-Qt
Note: If you used the script to install your masternode, you can run this command to update your control key: bash <(curl -sL https://raw.githubusercontent.com/syscoin/syscoin-governance-update/master/script.sh) Note: We encourage you to never run scripts you find on the internet (including ours) without checking them beforehand.
Otherwise, if you have installed your masternode manually:
Log into your masternode
Navigate to your masternode’s data directory
Open syscoin.conf in an editor
nano syscoin.conf
Replace the value for masternodeprivkey with your newly generated control token
Close and save the file
press CTRL+X
Restart syscoind (or your vps if you’re unsure on how to restart syscoind)
4. Reinitialize your masternode from Syscoin-Qt
Click on Window -> Console
Unlock your wallet by entering walletpassphrase [PASSPHRASE] [SECONDS]
replace [PASSPHRASE] with your passphrase
replace [SECONDS] by the number of seconds after which you want the client to lock the wallet again.
Initialize your masternode by entering masternode initialize [LABEL]
replace [LABEL] with the name of the masternode you want to restart.
Make sure it is synced fully syscli mnsync status. You want it to be 999 and then re-initialize from Qt before you pay attention to the masternode status.
no problem with the sys rewards, but need to know if I am to be watching this or it should be ok ? My VPS shows me this:
syscli masternode status
{
“outpoint”: “0000000000000000000000000000000000000000000000000000000000000000-4294967295”,
“service”: “5.181.49.15:8369”,
“status”: “Not capable masternode: Masternode not in masternode list”
That sounds like your QT (controller) masternode.conf might have a misalignment or otherwise not be configured properly… or you have not updated the control token in the syscoin.conf on your masternode host (line masternodeprivkey=<controlTokenHere> )
Hi @MooBaa
there is no cutoff date. You will continue receiving rewards until you start with the process to change the control token, after which you’ll have to wait for the duration of the grace period.
Allnodes will be sending out instructions this week. Please wait for them to contact you.
I am now finally getting ready to change the governance control token which I plan to do concurrently with the 4.2. uprade.
Questions:
a) does the qt wallet need to be online to generate the new masternode control token or is this simply generated by the wallet itself
b) when there are are more than one mn in a wallet and i generate more than one control token, these tokens can be associated with any of the masternodes, correct? Sequence of how they are generated doesn’t matter, correct?