Issues with Masternode Payments Fork

mahowi

Member
Mar 13, 2014
49
7
48
Germany
Please update ASAP!

Some bad masternodes set off a chain reaction which forked the network
into many smaller forks. To ensure you're on the correct fork please
update your daemon and run with the command "-reindex". It may take a
bit to reindex, but you'll be on the correct fork.

Source code:
https://github.com/darkcoinproject/darkcoin

Stable version (v0.9.4.8):
http://www.darkcoin.io/downloads/darkcoind
http://www.darkcoin.io/downloads/darkcoin-qt

RC2 (v0.10.8.8):
http://www.darkcoin.io/downloads/rc/darkcoind
http://www.darkcoin.io/downloads/rc/darkcoin-qt

Windows binaries to come soon.
Can't download darkcoind (RC2):
Code:
Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.
https doesn't work either:
Code:
 wget -c https://www.darkcoin.io/downloads/rc/darkcoind
--2014-05-26 14:56:03--  https://www.darkcoin.io/downloads/rc/darkcoind
Resolving www.darkcoin.io (www.darkcoin.io)... 162.252.83.46
Connecting to www.darkcoin.io (www.darkcoin.io)|162.252.83.46|:443... connected.
OpenSSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
Unable to establish SSL connection.
 

Scriptiee

Member
Apr 24, 2014
44
20
48
Out of this world
Code:
2014-05-26 08:11:08 ERROR: CheckBlock() : Bad vote detected
2014-05-26 08:21:52 ERROR: CheckBlock() : Bad vote detected
2014-05-26 08:26:48 ERROR: CheckBlock() : Bad vote detected
2014-05-26 08:45:48 ERROR: CheckBlock() : Bad vote detected
2014-05-26 11:06:15 ERROR: CheckBlock() : Bad vote detected
2014-05-26 11:30:31 ERROR: CheckBlock() : Bad vote detected
any idea what these are?
 

Coinotron

New Member
May 15, 2014
21
21
3
FYI
Today, 26 May 2014 Darkcoin pool was mining for 6 hours on forked chain. As a result over 100 blocks were orphaned. We updated pool's wallet to the newest version 0.9.4.8 yesterday. Everything worked fine. Pool was on proper chain until about 7:20 UTC. Then DRK block chain forked. I asked DarkCoin developer to investigate this issue.
 

sukottosan_d

New Member
May 24, 2014
5
0
3
Just FYI - earlier I had issues with my masternode. I messed around a bit - updated and reindexed - finally got my local wallet on the right fork as it was on the wrong one.
Seemed to be great after that - just got my first payment.

I know others were having issues so I wanted to post to update you all.
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
Votes don't seem to be happening, at least that appears to be why only a fraction of blocks are paying masternodes.
As far as my math goes, the "6 votes till payment" rule will lead to 1/6th (16%) of currently expected per MN payment. The rule is equal to having payment each 6 blocks in median, which meets the facts of the last 24 hours.

We will see how this levels out
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
Good morning :)
sukottosan_d, how did you know you had issues? I updated to the latest wallet only an hour after it was announced, I never forked, I'm on the correct chain, I show up on all the masternode lists, and I have two Masternodes. I have yet to receive a payment. I'm wondering if I am just having really bad luck or what? I'm at almost 25% luck? Almost feels like something is wrong but I can't find the problem. Of course it could just be bad luck....
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
As far as my math goes, the "6 votes till payment" rule will lead to 1/6th (16%) of currently expected per MN payment. The rule is equal to having payment each 6 blocks in median, which meets the facts of the last 24 hours.

We will see how this levels out
Well, if that is the case, then I can see why I haven't gotten paid. I'm sure that's not how it was intended to work, so I hope Evan comes back and fixes it, but it is a holiday today, and he's probably out with his family. If I were his wife, I would probably have forbidden him to look at the forums, LOL. He might have been at the grindstone all week for all we know and needs a break.
 

sukottosan_d

New Member
May 24, 2014
5
0
3
Good morning :)
sukottosan_d, how did you know you had issues? I updated to the latest wallet only an hour after it was announced, I never forked, I'm on the correct chain, I show up on all the masternode lists, and I have two Masternodes. I have yet to receive a payment. I'm wondering if I am just having really bad luck or what? I'm at almost 25% luck? Almost feels like something is wrong but I can't find the problem. Of course it could just be bad luck....
Honestly, I had doubts based on what I was seeing in my logs - many lost connections and no messages relating to DarkSend.
When I investigated - I noticed my local wallet was not up to the current block.

That may be okay for all I know (the log info) - but I was concerned and now I'm not. Based on the stats I'd say you need to wait a day or two to be concerned if you think you have everything covered.
I think at first - the working nodes will get a few more payments - just because all the nodes are not on the right fork right now.

You do have to factor in that those posting on forums are active - which means they are more likely to have fixed their MNs and there may still be many who have not fixed theirs yet. So you may be wondering why you aren't getting paid - however, it is likely that the people posting are more active - so they have a higher chance of getting payouts because they have troubleshot their stuff.... and, you are just on an unlucky streak to start.
If you follow that....that is a likely possibility.
 

mahowi

Member
Mar 13, 2014
49
7
48
Germany
From miningpoolhub @ bitcointalk:
Dev, please revert to before the masternode payout.


75092 block is found both in drkpool, suchpool.
75094 block is found in drkpool, suchpool, miningpoolhub.


Three pools are running in three different block chain.

This is really big problem. Please revert it as soon as possible.
My wallet shows:
Code:
version" : 100808,
"protocolversion" : 70015,
"walletversion" : 60000,
[...],
"blocks" : 75091,
So there is definitely a problem!

Edit: http://chainz.cryptoid.info/drk/ shows block 75106, http://explorer.darkcoin.io/chain/DarkCoin shows block 75096!
 

rnd0m

New Member
May 26, 2014
4
0
1
i see this situation also.
i have two different clients - darkcoind 0.9.4.8 (downloaded from site precompiled) and darkcoin-qt 0.9.4.8 (compiled from github source) which are both stuck at 75090, rejecting any blocks from both of mentioned forks.

debug file shows lots of:
ERROR: CheckBlock() : Bad vote detected
ERROR: ProcessBlock() : CheckBlock FAILED
and
ERROR: CTxMemPool::acceptableInputs() : inputs already spent

clients are both on linux, but on different machines and networks. both clients went through full -reindex, still no change.
never had problems before, using this setup for months.

we do need some help it seems, can someone at least clarify which of those fork (if any) is proper?
 

mahowi

Member
Mar 13, 2014
49
7
48
Germany
Both block explorers still show different blockheight. And my client (Windows RC2 v0.10.8.8) is still stuck at block 75091 for more than an hour.
 

rnd0m

New Member
May 26, 2014
4
0
1
i managed to unstuck one of my clients by replacing darkcoind 0.9.4.8 with darkcoind-rc2-0.10.8.9 which i downloaded few minutes ago from http://darkcoin.io/downloads/rc/darkcoind
now it shows same block height and information as official explorer at http://explorer.darkcoin.io/chain/DarkCoin and receiving news blocks, i am waiting to see how will that work with p2pool.
meanwhile, is this any fix at all? does this mean that we must migrate all our clients to 0.10.x
cheers