You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe when nothing in the masternode list information changes, masternodes can be upgraded without downtime when you swap the executable and only briefly bring it down to restart. However, when the protocol number changes, this may be causing each masternode's place in the list to be reset as the change is detected.
This request would be to investigate if this is indeed the case, and if so, if it would be safe and secure to allow masternodes to be upgraded to a new protocol version and allow a change to just that one attribute without resetting the masternode's place in the list.
The text was updated successfully, but these errors were encountered:
with dash i believe the masternode is only effect if down longer then a hour correct me if am wrong but that is what i heard. So yes i also believe that.
I believe when nothing in the masternode list information changes, masternodes can be upgraded without downtime when you swap the executable and only briefly bring it down to restart. However, when the protocol number changes, this may be causing each masternode's place in the list to be reset as the change is detected.
This request would be to investigate if this is indeed the case, and if so, if it would be safe and secure to allow masternodes to be upgraded to a new protocol version and allow a change to just that one attribute without resetting the masternode's place in the list.
The text was updated successfully, but these errors were encountered: