Mandatory : All users must update to v0.11.1.x

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
We have seen an issue on the network, which comes from a disagreement between v10 and v11 clients. It appears to be an issue the network has always had, but never caused an issue until we upgraded the core client. This caused the v11 client to get stuck this morning, when a block was created and accepted by v10 and not by v11. V11 was correct to reject the block, as it has improved masternode payment detection capabilities.

Due to this, we need all users to update from v10 to v11, this includes end-users, masternodes and miners. Anyone left on the v10 will fork from the network and orphan blocks until they upgrade.

If you have an error "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues." just restart the client with --reindex

Edit by vertoe: All users must update to v0.11.1.x now!
 
Last edited by a moderator:

MangledBlue

Well-known Member
Jun 28, 2014
1,246
678
183
USA
And this will clear up the ERROR I'm getting?

{
"version" : 110006,
"protocolversion" : 70052,
"walletversion" : 60001,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 204572,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 4083.62714253,
"testnet" : false,
"keypoololdest" : 1411407802,
"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."
}
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
And this will clear up the ERROR I'm getting?

{
"version" : 110006,
"protocolversion" : 70052,
"walletversion" : 60001,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 204572,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 4083.62714253,
"testnet" : false,
"keypoololdest" : 1411407802,
"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."
}
Try --reindex
 

elbereth

Active Member
Dash Support Group
Mar 25, 2014
440
466
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
And they need to reindex...

Because I updated a couple of hours ago from v10 to v11 and v11 accepted the fork without the reindex.
 
  • Like
Reactions: oblox

elbereth

Active Member
Dash Support Group
Mar 25, 2014
440
466
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
I just finished the reindex with 0.11.0.7:

/opt/darkcoind/0.11/darkcoind-0.11.0.7 getinfo
{
"version" : 110007,
"protocolversion" : 70052,
"walletversion" : 60000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 204709,
"timeoffset" : -180,
"connections" : 11,
"proxy" : "",
"difficulty" : 2792.20437713,
"testnet" : false,
"keypoololdest" : 1394017965,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}

Still on the bad fork?
204709 00000000001776e3f483bd15db28a51e5201f869a61b290207bf1ea5fbd4af8e
 

MangledBlue

Well-known Member
Jun 28, 2014
1,246
678
183
USA
I just finished the reindex with 0.11.0.7:

/opt/darkcoind/0.11/darkcoind-0.11.0.7 getinfo
{
"version" : 110007,
"protocolversion" : 70052,
"walletversion" : 60000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 204709,
"timeoffset" : -180,
"connections" : 11,
"proxy" : "",
"difficulty" : 2792.20437713,
"testnet" : false,
"keypoololdest" : 1394017965,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}

Still on the bad fork?
204709 00000000001776e3f483bd15db28a51e5201f869a61b290207bf1ea5fbd4af8e
\


SAME

ugh - off ta work
 

aaxx1503

Active Member
Feb 28, 2014
113
106
93
All nodes updated without a problem. I started with the local client (First time upgrading to Darkcoin core from 0.10.xx) and only did a "masternode password start" on local wallets. Everything is synced up correctly.
 
  • Like
Reactions: Raico

crowning

Well-known Member
May 29, 2014
1,415
1,997
183
Alpha Centauri Bc
My blockchain explorer stopped working:
Code:
RPC service lacks full txindex
catch_up_rpc: abort
Opened /home/drk/.darkcoin/Server/blocks/blk00003.dat
incomplete block of length 1991840519 chain 15
The server is fully synced (block 204737 right now).

I know vertoe or flare have an updated version of Abe, but I cannot find a link, even with the fantastic :rolleyes: forum search...

Or do you use the original Bitcoin Abe as well?

I also wouldn't like to drop the complete table and build it again...
 
Last edited by a moderator:
  • Like
Reactions: fernando

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
My blockchain explorer stopped working:
Code:
RPC service lacks full txindex
catch_up_rpc: abort
Opened /home/drk/.darkcoin/Server/blocks/blk00003.dat
incomplete block of length 1991840519 chain 15
The server is fully synced (block 204737 right now).

I know vertoe or flare have an updated version of Abe, but I cannot find a link, even with the fantastic :rolleyes: forum search...

Or do you use the original Bitcoin Abe as well?

I also wouldn't like to drop the complete table and build it again...
You can use upstream https://github.com/bitcoin-abe/bitcoin-abe

As for the update: I don't know of any update procedure, redid the whole DB.
 

IYFTech

New Member
Jan 17, 2015
3
1
3
I can't get v11 to work with p2pool - so I can't upgrade......Ever since I upgraded to the latest version I've been unable to get p2pool to connect on port 9999:

2015-01-16 16:38:13.821624 p2pool (version 81fc6c5-dirty)
2015-01-16 16:38:13.821724
2015-01-16 16:38:13.821780 Testing bitcoind RPC connection to 'REMOVED' with username 'IYFTechDRK'...
2015-01-16 16:38:13.850612 ...success!
2015-01-16 16:38:13.850710 Current block hash: 5f2afca31990cbc9c8be1722088daafeac266253c55a1e7f06a47
2015-01-16 16:38:13.850753 Current block height: 204176
2015-01-16 16:38:13.850777
2015-01-16 16:38:13.850815 Testing bitcoind P2P connection to '127.0.0.1:9999'...
2015-01-16 16:38:18.851266 ...taking a while. Common reasons for this include all of bitcoind's connection slots being used...

If I revert to v10 I have no problem..........it just won't connect on 9999
 

elbereth

Active Member
Dash Support Group
Mar 25, 2014
440
466
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
Not sure if it is normal, but blocktemplate in v11 has changed the values for coinbasevalue.

v10: coinbasevalue was total generated coins for the block
v11: is now only the miner's part

This caused the wrong percentage paid blocks on 204703 204704 204706 and 204707.
 

Propulsion

The buck stops here.
Feb 26, 2014
1,008
467
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
Strange, that's what I use. And I fear when I build the datase again Abe gets stuck at the same block.

So for me it's now a complete blockchain rebuild followed by a complete Abe rebuild. Aaargl...

Anyway, thanks.
I'm so sorry... :sad:
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Just got version 11006 to sync with -reindex, but then it crashed a minute or so after it synced, (windows 32-bit).

Will try v.11007.
 

acidburn

Active Member
May 26, 2014
467
175
113
I just picked this up today after opening my version 10 wallet. Some drk was sent last night and I revived it. Do I need to reindex when I install v11?
 

orangecycle

Well-known Member
Foundation Member
Oct 2, 2014
169
239
203
node40.com
All of my nodes dropped offline about 15 minutes after updating to 11.0.7.

getinfo reveals they are on the correct block and I don't see any errors. But none of my nodes show up in masternode list.
 

crowning

Well-known Member
May 29, 2014
1,415
1,997
183
Alpha Centauri Bc
All of my nodes dropped offline about 15 minutes after updating to 11.0.7.

getinfo reveals they are on the correct block and I don't see any errors. But none of my nodes show up in masternode list.
I had this when I went from v0.10.17.26 to v0.11.0.6.

Stopping the Masternode(s), removing peers.dat and starting the Mastenodes with -reindex fixed it, not a single drop since then.
 

splawik21

Grizzled Member
Dash Core Team
Moderator
Foundation Member
Dash Support Group
Apr 8, 2014
1,917
1,274
1,283
I had this when I went from v0.10.17.26 to v0.11.0.6.

Stopping the Masternode(s), removing peers.dat and starting the Mastenodes with -reindex fixed it, not a single drop since then.
Same here.
Always on protocol change delete peers.dat just in case ;) in the past I have never had any issues or deamons down. 99,9% of the time ;)
 

orangecycle

Well-known Member
Foundation Member
Oct 2, 2014
169
239
203
node40.com
I had this when I went from v0.10.17.26 to v0.11.0.6.

Stopping the Masternode(s), removing peers.dat and starting the Mastenodes with -reindex fixed it, not a single drop since then.
After reindex, did you have to start from QT again?

I'm reindexing now, but it's going to take a little bit. On 155878 right now. Thankfully I have a bunch of nodes to update so I'm not twiddling my thumbs :)