Inconsistency in Masternode - Upate to 0.12.0.58 asap !

84% - Not Bad !

not sure what to do about these other 16% - they seem to be officially MIA and do NOT care ??

LK3nneA.png
 
If master blocks were required to broadcast the hash of one of the three last blocks and only nodes on the longest chain got the reward on the longest chain then they might care.
 
tungfa said:
84% - Not Bad !

not sure what to do about these other 16% - they seem to be officially MIA and do NOT care ??

LK3nneA.png
Click to expand...
The problem is that as long as there are 350+ nodes with closed ports, dashninja is unable to determine their current version

upload_2016-9-6_15-1-24.png
 
Masternode versions (only compatible protocols)0.12.0.58 (70103): 84.2 %
;)

PLEASE check your Port settings !! (as flare pointed out above)

Call to all Masternode owners hosting at Amazon AWS, please check your firewall rules as your ports are closed !!
We are trying to get the last 16% of not updated MN’s onto 0.12.0.58 - you are a big part of this (as your ports are closed)
PLEASE check your Ports - or change providers !
https://www.dashninja.pl/?mnregexp=(Closed)#mnlistdetail
 
85% - making progress :rolleyes:

MN numbers vary a bit these days - there are some OTC trades going on and MN's are changing hands - moving to new owners/hosting/....
(wait a bit - and they will all be back on)

lik8BAI.png
 
tungfa said:
84% - Not Bad !

not sure what to do about these other 16% - they seem to be officially MIA and do NOT care ??

LK3nneA.png
Click to expand...
If they had to show up for votes or get kicked, by implementing an active abstain, so that abstain could be separated from null, this wouldn't happen. Voting needs to be part of the PoService, and this is how to add it. They would be kicked off and we wouldn't have to worry about them mucking up the network.

Between active abstain and protocol update, no more of this crap would happen.
 
camosoul said:
If they had to show up for votes or get kicked, by implementing an active abstain, so that abstain could be separated from null, this wouldn't happen. Voting needs to be part of the PoService, and this is how to add it. They would be kicked off and we wouldn't have to worry about them mucking up the network.

Between active abstain and protocol update, no more of this crap would happen.
Click to expand...

Votes or not, I don't see how they're still on the network if their ports are closed. If ports are closed then they're not able to service the network, right? How are other MNs able to connect with them? What am I missing here?
 
You must log in or register to reply here.
Back
Top