Well, you have cases where Core 11 daemons and clients were on other blocks than existing Core clients not to mention forks from Onyx clients (expected).Isn't forking usually caused by enforcement? I thought Evan could just turn it off and issue a checkpoint to get everybody back on the right chain.
Or is this a more serious problem?
It seems you're on the right chain, and the warning is just saying there's a fork.I just reindexed my nodes. But still see the warning.
"version" : 110011,
"protocolversion" : 70054,
"walletversion" : 60001,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 207241,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 3439.95854335,
"testnet" : false,
"keypoololdest" : 1418931689,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."
That doesn't mean you are on a bad fork. It just means the client detected another fork out there on the network. Judging by block number, you are on the right fork but check the hash: 0000000000008bba11033c31a1a4df29db8557b8355ef6738f7a93beb2fc4901I just reindexed my nodes. But still see the warning.
"version" : 110011,
"protocolversion" : 70054,
"walletversion" : 60001,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 207241,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 3439.95854335,
"testnet" : false,
"keypoololdest" : 1418931689,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."
What does the hash mean?That doesn't mean you are on a bad fork. It just means the client detected another fork out there on the network. Judging by block number, you are on the right fork but check the hash: 0000000000008bba11033c31a1a4df29db8557b8355ef6738f7a93beb2fc4901
That is the hash of a block on the correct chain. In the debug console, just enter "getblock 0000000000008bba11033c31a1a4df29db8557b8355ef6738f7a93beb2fc4901" and if you have that block, then you are on the right chain.What does the hash mean?
I've got this message:That is the hash of a block on the correct chain. In the debug console, just enter "getblock 0000000000008bba11033c31a1a4df29db8557b8355ef6738f7a93beb2fc4901" and if you have that block, then you are on the right chain.
It's a bit early to say what caused it at the moment unfortunately.What I understand is the Core version "Removed centralized checkpointing node / sporking code (to be implemented better in the future)" as Evan stated on the OP page of the v.11 Test Thread (https://darkcointalk.org/threads/v0-11-0-x-testing.3401/). Does it mean the Masternodes on the Core version are not enforced by the reference nodes but it's hard-coded ? While the MNs on the older version are still having the enforcement by the reference nodes. Could this somehow cause the problem? I wish someone would explain to me.
stop and start your wallet, it'll clear now.I've got this message:
"Safe mode: Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues. (code -2)"
Disablesafemode=1 in your conf if stopping and starting doesn't workI've got this message:
"Safe mode: Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues. (code -2)"
s/D/d/Disablesafemode=1 in your conf if stopping and starting doesn't work
"Disablesafemode=1" does not work, but "disablesafemode=1" works now. Thanks. lolDisablesafemode=1 in your conf if stopping and starting doesn't work
Dislike !Things don't look so hot today. Directbet and others have suspended DRK betting and 4/12 of my masternodes died overnight.
I had been thinking the same thing! BCT seemed to go off-air very shortly after the first wallet & MN error messages started appearing.My theory is that bitcointalk was secretly mining darkcoion on the user's computer. When Darkcoin forked, their disks broke.Jks.
My MN is doing the same thing Walter. I believe it's on the correct fork and all but it still produces that same error message which I think is because the network is having problems. I'm just leaving it alone until we're given further instructions to either go back into the dining room for the second course or wait near the life boats.All my MNs still snapped. One just stopped the daemon and the other two:
"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."
Does that error message mean that the MN is not functioning properly? Or is it just an observation by the MN that the network is a bit fucked...?!
Happy to leave the other two running with that message as long as my MN is functioning. A bit of guidance needed please?
Thanks![]()
Thanks dude. I'll leave them alone for now thenMy MN is doing the same thing Walter. I believe it's on the correct fork and all but it still produces that same error message which I think is because the network is having problems. I'm just leaving it alone until we're given further instructions to either go back into the dining room for the second course or wait near the life boats.