Closed azilber closed 6 years ago
DO NOT UPGRADE your masternode to v2.0.0.6.
You will see entries like this in your debug.log:
2018-02-22 16:34:15 CMasternodeMan::AskForMN - Asking node for missing entry, vin: CTxIn(COutPoint(8ebfcfa6130858736208bb8661932b75d84f72b58fb4feb4c5a62c28049e4495, 0), scriptSig=) 2018-02-22 16:34:16 mnb - Got bad Masternode address signature 2018-02-22 16:34:16 Misbehaving: 47.254.129.26:43463 (9200 -> 9300)
All Masternode signatures become invalid,e except for 3 masternodes. Removing mncache.dat resolves nothing.
Please test version 2.0.0.7
limxdev
commented
6 years ago limxdev
commented
6 years ago
DO NOT UPGRADE your masternode to v2.0.0.6.
You will see entries like this in your debug.log:
2018-02-22 16:34:15 CMasternodeMan::AskForMN - Asking node for missing entry, vin: CTxIn(COutPoint(8ebfcfa6130858736208bb8661932b75d84f72b58fb4feb4c5a62c28049e4495, 0), scriptSig=) 2018-02-22 16:34:16 mnb - Got bad Masternode address signature 2018-02-22 16:34:16 Misbehaving: 47.254.129.26:43463 (9200 -> 9300)All Masternode signatures become invalid,e except for 3 masternodes. Removing mncache.dat resolves nothing.