v0.11.0 - Darkcoin Core Release

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
How come some people can get their MNs stay on v.11 but many others can't?
 

JGCMiner

Moderator
Jun 8, 2014
364
217
113
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?
 

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
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?
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).
 

jpr

Active Member
May 11, 2014
493
393
133
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."
 

miningpoolhub

New Member
Mar 9, 2014
12
1
3
The main problem is that we don't know what the actual bug is.

Just guessing that it's related to compatibility issue, but that's not enough to fix.
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
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."
It seems you're on the right chain, and the warning is just saying there's a fork.
 
  • Like
Reactions: jpr

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
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: 0000000000008bba11033c31a1a4df29db8557b8355ef6738f7a93beb2fc4901
 
  • Like
Reactions: jpr

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
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
What does the hash mean?
 

jpr

Active Member
May 11, 2014
493
393
133
Code:
./darkcoind getblockhash 207244
error: {"code":-2,"message":"Safe mode: Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."}
Not sure if I know what I am doing :D
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
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 the enforcement is hard-coded ? While the MNs on the older version are still being enforced by the reference nodes. Could this somehow cause the problem? I wish someone would explain to me.
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
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.
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)"
 

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
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.
It's a bit early to say what caused it at the moment unfortunately.
 
  • Like
Reactions: fernando

moocowmoo

Bovine Bit-flipper
Foundation Member
Jun 15, 2014
483
603
263
masternode.me
Dash Address
XmoocowYfrPKUR6p6M5aJZdVntQe71irCX
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)"
stop and start your wallet, it'll clear now.
 

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
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 work
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Disablesafemode=1 in your conf if stopping and starting doesn't work
"Disablesafemode=1" does not work, but "disablesafemode=1" works now. Thanks. lol

EDIT: Sorry, Propulsion, I wrote this post in my sleep last night.. lol..
 
Last edited by a moderator:

stonehedge

Well-known Member
Foundation Member
Jul 31, 2014
696
333
233
Things don't look so hot today. Directbet and others have suspended DRK betting and 4/12 of my masternodes died overnight.
 

stonehedge

Well-known Member
Foundation Member
Jul 31, 2014
696
333
233
I'll report back when I know more about my masternodes. Most were still on Onyx (about to be upgraded) but three were on 11.0.x and were having problems staying up yesterday.
 

stonehedge

Well-known Member
Foundation Member
Jul 31, 2014
696
333
233
All of my masternodes will be updated to 11.0.11 today (although isn't 11.0.12 out soon?).
 

Walter

Active Member
Masternode Owner/Operator
Jul 17, 2014
231
201
103
All of my MNs were down this morning, lovely! Just updated to 11.0.11 and had to do a --reindex. Waiting to see if that's fixed things now...

looks like bct is down too!
 

stonehedge

Well-known Member
Foundation Member
Jul 31, 2014
696
333
233
IMHO this fork was caused by V11 not being stable, not by people not updating in time. I guess running V11.0.x is the only thing we can do right now but it'd be nice to have some guidance from the head honcho.
 

Walter

Active Member
Masternode Owner/Operator
Jul 17, 2014
231
201
103
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 :)
 

RenegadeMan

Member
Aug 6, 2014
61
92
58
My theory is that bitcointalk was secretly mining darkcoion on the user's computer. When Darkcoin forked, their disks broke. ;) Jks.
I had been thinking the same thing! BCT seemed to go off-air very shortly after the first wallet & MN error messages started appearing.

Thank goodness we have this alternative forum.
 
  • Like
Reactions: Walter

RenegadeMan

Member
Aug 6, 2014
61
92
58
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 :)
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.
 
  • Like
Reactions: Walter

Walter

Active Member
Masternode Owner/Operator
Jul 17, 2014
231
201
103
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.
Thanks dude. I'll leave them alone for now then :)