{"action":"created","issue":{"url":"https://api.github.com/repos/dashpay/dash/issues/539","labels_url":"https://api.github.com/repos/dashpay/dash/issues/539/labels{/name}","comments_url":"https://api.github.com/repos/dashpay/dash/issues/539/comments","events_url":"https://api.github.com/repos/dashpay/dash/issues/539/events","html_url":"https://github.com/dashpay/dash/issues/539","id":101276017,"number":539,"title":"Masternode-Update","user":{"login":"scratchy","id":906544,"avatar_url":"https://avatars.githubusercontent.com/u/906544?v=3","gravatar_id":"","url":"https://api.github.com/users/scratchy","html_url":"https://github.com/scratchy","followers_url":"https://api.github.com/users/scratchy/followers","following_url":"https://api.github.com/users/scratchy/following{/other_user}","gists_url":"https://api.github.com/users/scratchy/gists{/gist_id}","starred_url":"https://api.github.com/users/scratchy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/scratchy/subscriptions","organizations_url":"https://api.github.com/users/scratchy/orgs","repos_url":"https://api.github.com/users/scratchy/repos","events_url":"https://api.github.com/users/scratchy/events{/privacy}","received_events_url":"https://api.github.com/users/scratchy/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/dashpay/dash/labels/wontfix","name":"wontfix","color":"ffffff"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-08-16T15:46:56Z","updated_at":"2015-09-04T01:28:04Z","closed_at":"2015-08-22T17:32:04Z","body":"Hey,\r\n\r\nAs I noticed currently theres a need of resending the Masternode 'start' command on version bump.\r\nI guess the reason for this, that new pings after version bumps are rejected.\r\nIt would be awesome if its possible to upgrade masternodes without resending the start command, is there any possibility / anything planed?\r\n"},"comment":{"url":"https://api.github.com/repos/dashpay/dash/issues/comments/137616862","html_url":"https://github.com/dashpay/dash/issues/539#issuecomment-137616862","issue_url":"https://api.github.com/repos/dashpay/dash/issues/539","id":137616862,"user":{"login":"scratchy","id":906544,"avatar_url":"https://avatars.githubusercontent.com/u/906544?v=3","gravatar_id":"","url":"https://api.github.com/users/scratchy","html_url":"https://github.com/scratchy","followers_url":"https://api.github.com/users/scratchy/followers","following_url":"https://api.github.com/users/scratchy/following{/other_user}","gists_url":"https://api.github.com/users/scratchy/gists{/gist_id}","starred_url":"https://api.github.com/users/scratchy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/scratchy/subscriptions","organizations_url":"https://api.github.com/users/scratchy/orgs","repos_url":"https://api.github.com/users/scratchy/repos","events_url":"https://api.github.com/users/scratchy/events{/privacy}","received_events_url":"https://api.github.com/users/scratchy/received_events","type":"User","site_admin":false},"created_at":"2015-09-04T01:28:04Z","updated_at":"2015-09-04T01:28:04Z","body":"Sad to hear that.\r\n\r\nI dont get why the protocol number is that critical, that it has to be signed?\r\nIts pretty hard to keep the nodes updated like this. The reason for this is there a lot of \"hosting-services\" out there (including one im running) which dont own the private key for the nodes. Now there are two possiblitys if theres a version bump:\r\n\r\n1. Update the nodes (thats what should be the best solution), but then ALL nodes will drop from the Masternode-List, because the hosters cant resend the start command.\r\n\r\n2. Dont update the nodes as long as its enforced, thats sadly currently the best solution for the Masternode owners but not for the Dash-Network (Running on old versions should not be the best solution, should it?). The reason why its currently preffered is because the nodes are online as much time as possible but after the enforcement, all nodes will drop again waiting for the owners to resend the start command, so were here on the same issue.\r\n\r\nBoth solutions are not optimal, because they lead to a downtime of Masternodes (as long as all users resend their mnb), which in fact is bad for the network and for the hosting services. Im up to solutions for updating masternodes or other idears how to update the nodes without downtime, but as far as i can see it, its not possible without help on the dashd side"}}