Masternode update procedure

doopalek

New Member
Jul 21, 2014
17
1
3
Whenever there is a new version I stop my masternode, update files on remote server, restart it, update files on local host and issue "masternode start-alisas".
Do I miss something here? Is it necessary to "masternode start-alisas" after each restart on remote server? I see some masternodes with uptime of for example 1 week right after an update - how is it possible?
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
Whenever there is a new version I stop my masternode, update files on remote server, restart it, update files on local host and issue "masternode start-alisas".
Do I miss something here? Is it necessary to "masternode start-alisas" after each restart on remote server? I see some masternodes with uptime of for example 1 week right after an update - how is it possible?
You only need to "start-alias" your node if the protocol version has changed or if your node was offline for more than 60mins.

All v12 versions (e.g. v0.12.0.46, v0.12.0.47 and v0.12.0.48) had protocol version 70103

upload_2015-8-25_17-52-13.png
 
Last edited by a moderator:
  • Like
Reactions: doopalek