v0.11.0 - Darkcoin Core Release

Network is acting very funny for me. I've been waiting almost 1.5 hours for the last 6 blocks. Seems as if the network might be forking or something along those lines between old and new clients? I can't think of any reason why we'd be waiting almost 2 hours for 6 blocks? Anyone else noticing this weird long block. Anyone running any sort of block chain health type check? Hopefully it's just another anomaly but almost feels like an attack of some sort. Went to check the changelog for this release to see what else was fixed but that change log is well... a bit out of date.

https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/CHANGELOG.md
 
eduffield, I'm also getting the warning and having another Darksend tx being stuck:

20:18:34

{
"version" : 110011,
"protocolversion" : 70054,
"walletversion" : 61000,
"balance" : 66.77211480,
"darksend_balance" : 0.00000000,
"blocks" : 207100,
"timeoffset" : 7,
"connections" : 20,
"proxy" : "",
"difficulty" : 1598.86151011,
"testnet" : false,
"keypoololdest" : 1421857166,
"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...
EDIT: It's being stuck at block 207098 which is the highest block on explorer.darkcoin.fr. What's the current block right now?
Will restart with -reindex.
 
Last edited by a moderator:
This is showing up in my logs.

2015-01-22 01:39:44 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 207095 (00000000000fbacc124b1477066f633181bdbf053fbb78a8cb28588d412b206d)
lasting to height 207122 (00000000000eb367eccdca2a0800f3c955304cd7dd54dd30ebdffcbefe9dd59a).
Chain state database corruption likely.
 
Had a blast of panic.mp3 about 20 minutes ago, reindexing all my MNs and my local wallet now, all but one had the 'some folk are experiencing issues' warning.
 
Network on first chain:

"blocks" : 207106,
"timeoffset" : 0,
"connections" : 8,
"proxy" : "",
"difficulty" : 888.44160881,
This network has 59GH/s

Network on Second Chain:

"blocks" : 207133,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 3073.60266676,
This network has 67GH/s

Which is the correct chain?
 
Last edited by a moderator:
So i reindexed one of my masternodes and it jumped to the larger chain.

MN on block 207111
2015-01-22 02:17:16 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 207095 (00000000000fbacc124b1477066f633181bdbf053fbb78a8cb28588d412b206d)
lasting to height 207139 (00000000001823509dfca36c142efd50412b116d4b2935e8c6cb9e37caee7ca9).
Chain state database corruption likely.


MN on block 207139
2015-01-22 02:17:08 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 207095 (00000000000fbacc124b1477066f633181bdbf053fbb78a8cb28588d412b206d)
lasting to height 207111 (000000000011dd9884fd95562600ed81363a59897daa72c44525ceb45b0e8ea4).
Chain state database corruption likely.
 
I think my wallet is on the correct fork:


22:06:37
getinfo
22:06:37

{
"version" : 110011,
"protocolversion" : 70054,
"walletversion" : 61000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 207152,
"timeoffset" : 8,
"connections" : 10,
"proxy" : "",
"difficulty" : 2158.43949547,
"testnet" : false,
"keypoololdest" : 1421891341,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
 
OK.. Now I'm getting that warning again... eduffield ?

{
"version" : 110011,
"protocolversion" : 70054,
"walletversion" : 61000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 207166,
"timeoffset" : 8,
"connections" : 8,
"proxy" : "",
"difficulty" : 2141.90869126,
"testnet" : false,
"keypoololdest" : 1421891341,
"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."
}

EDIT: I think this is just a warning, doesn't mean it says I'm on the right or wrong fork. I read that the bitcoin code base tends to be verbose about fork warnings.
 
Last edited by a moderator:
moli said:
I think my wallet is on the correct fork:


22:06:37
getinfo
22:06:37

{
"version" : 110011,
"protocolversion" : 70054,
"walletversion" : 61000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 207152,
"timeoffset" : 8,
"connections" : 10,
"proxy" : "",
"difficulty" : 2158.43949547,
"testnet" : false,
"keypoololdest" : 1421891341,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
Click to expand...

Looking at http://explorer.darkcoin.io/chain/Darkcoin it would appear to me that you are off on the wrong fork. Currently, the latest block is 207098.
 
moli said:
No, that block has been stuck for about 4 hours. We're discussing this in IRC, I think i'm on the right fork but I can't be positive 100%. Still waiting to hear from our devs.
Click to expand...

Ooooh... Be sure and update us lurkers here when you learn what the proper fork is... I am rebuilding blocks and reindexing now!
 
feeleep said:
only Onyx keeps correct chain at this moment - all my new daemons forked
Click to expand...
You don't know that... the fact of the matter is V11 should be causing V10's to fork off as they are old clients that should have updated to Core. The problem looks, well... bad right now.
 
oblox said:
You don't know that... the fact of the matter is V11 should be causing V10's to fork off as they are old clients that should have updated to Core. The problem looks, well... bad right now.
Click to expand...
at least onyx daemon has higher diff and more blocks on it so i suppose this is a orrect chain :|

anyway - after Core reindex it is on chain now, but I am a bit afraid to switch to it until Evan will release the fix or something
 
feeleep said:
at least onyx daemon has higher diff and more blocks on it so i suppose this is a orrect chain :|

anyway - after Core reindex it is on chain now, but I am a bit afraid to switch to it until Evan will release the fix or something
Click to expand...
Not sure you can really say that. 67GH is on the chain I'm on, all core clients, last block 207236
 
You must log in or register to reply here.
Back
Top