• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

v0.11.0 - Darkcoin Core Release

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?
 
JGCMiner said:
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?
Click to expand...
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).
 
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."
 
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.
 
jpr said:
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."
Click to expand...
It seems you're on the right chain, and the warning is just saying there's a fork.
 
  • Like
Reactions: jpr
jpr said:
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."
Click to expand...

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
oblox said:
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
Click to expand...
What does the hash mean?
 
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
 
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.
 
babygiraffe said:
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.
Click to expand...
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)"
 
moli said:
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.
Click to expand...
It's a bit early to say what caused it at the moment unfortunately.
 
moli said:
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)"
Click to expand...
Disablesafemode=1 in your conf if stopping and starting doesn't work
 
oblox said:
Disablesafemode=1 in your conf if stopping and starting doesn't work
Click to expand...
"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:
Things don't look so hot today. Directbet and others have suspended DRK betting and 4/12 of my masternodes died overnight.
 
You must log in or register to reply here.
Back
Top