Is the issue (or part of it) that MNs drop/ignore connections from previous versions but normal clients don't? If my normal wallet is v15, it shouldn't be talking to anything v14...? Yet it seems to be getting crap data from somewhere as to for example which and how many MNs are v15 and active. (edit: as are MNs!)Yeah, but dnsseeder was updated on 17th, so your fresh updated darkcoind got provided with outdated peers and the more these updated your peer got orphaned and dropped of the network.
Nevertheless i agree: the update behaviour has to be improved. As i see it problem is that protocolversion field is used as version identifier for two networks: darkcoin and masternode. This seems to not work out in case of network wide major updates.
When enforcement was last enabled, it seemed pretty efficient at orphaning blocks generated by non-compliant pools/miners, and preventing any forking. Why can't that effective enforcement be applied to everything on the network? Not current version, don't get to play.
If someone could draw a diagram/flow chart of how this stuff works it would be most helpful! And stop me asking such stupid questions. :grin:
Last edited by a moderator: