Issues with Masternode Payments Fork

eduffield

Core Developer
Mar 9, 2014
1,084
5,320
183
Today the masternode payments fork went into effect. The fork went off without issue and the network looks very healthy, but it appears there is some issue with pools voting for the wrong masternodes. This is causing payments to not go through as they should.

The fix is rather simple and can be done without a hard fork. After the pools update to the fixed version, the payments will begin to go through.
We’re currently working on a resolution and will provide the new version soon (probably by tomorrow, hopefully in a few hours).

Thanks,

The Darkcoin Team
 

donho

Member
Masternode Owner/Operator
Apr 16, 2014
96
20
58
Can anyone/Evan elaborate what kind of Pubkey is shown on the blockexplorer for the Masternode votes?
I would love to somehow check if I'm receiving votes.
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,320
183
Attention Pool Operators,

If you're unaware, the masternode payments have experienced some
issues. It appears there the issues is actually just problems with
masternode propagation on the network. This will fix itself over time,
however to fix this quickly we've made some modifications to the code.

Pool Operations: Please recompile the source from master and add
maxconnections=200 to your configuration
Everyone else: You need not update

If the problem doesn't resolve itself we'll look into other possible causes.
 

Coinotron

New Member
May 15, 2014
21
21
3
I think DRK network forked. I have 2 clients. 9.4.6 shows that current block is 74625. New one 9.4.7 reports 74616
 

TsuyokuNaritai

Active Member
May 24, 2014
181
102
103
I think DRK network forked. I have 2 clients. 9.4.6 shows that current block is 74625. New one 9.4.7 reports 74616
[22:12] <@evan82> k, if you're on the wrong fork please get the latest changes from the repo and compile. Run with -reindex and you'll get the right fork
[22:12] <@evan82> it should only be a few pools, no exchanges or masternodes, etc
[22:13] <eth2> evan82, which is the right fork?
[22:13] <@evan82> 0.9.4.8
[22:13] <@evan82> jimbit, masternodes should be ok as long as you're on the right fork
[22:14] <coinotron> evan82: just to clarify 0.9.4.8 has 3 your today commits
[22:14] <@evan82> yeah
 

Propulsion

The buck stops here.
Feb 26, 2014
1,008
468
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
Local wallet for MN is reporting 2 hours behind stuck on block 74603 with 23 active connections.
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,320
183
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.
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
EDIT: reindexing...
 
Last edited by a moderator:

precrime3

New Member
May 10, 2014
26
2
3
Wait so updated version is 9.4.8 not the 9.4.6 im on and is shown on main wesbite? Don't know how to compile or anything, so will have to wait for the qt-exe I guess :{
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
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.

I'm also at a lost here. Never had this issue on testnet (local / remote), but mainnet has been giving me trouble for some reason (local setup) so I took extra troubleshooting procedures. I've been away for two days and left everything shut down, yet my old IP is still listed as :1 (twice) ...

Local VM Ubuntu 14.04
- updated darkcoind 10.8.8, -reindexed, stuck issues fixed
- closed internet connection (to get brand new external IP)
- generated new genkey and put in darkcoin.conf
- masternode started successfully
- tried with and without 'externalip=xx.xx.xx.xx" (but this is only required for local /remote right?, tried anyways...)

Waited a good 45 minutes to propagate and I still can't find myself on the masternode list, any advice please?
 
Last edited by a moderator:

sukottosan_d

New Member
May 24, 2014
5
0
3
Updated and reindexed - still stuck at 74604.

Edit: problem now solved - took a long while to get the blocks.
 
Last edited by a moderator:

atavacron

Member
Apr 27, 2014
45
16
48
Hi,

My masternode receive just this error, no payment:

2014-05-25 23:09:32 !coins.IsAvailable COutPoint(cfa73aeff245e44e86b9d18a703c471cfa8a7621e8a86eb48e97928edb077837, 1)
2014-05-25 23:09:32 ERROR: CTxMemPool::acceptableInputs() : inputs already spent

up to date 10.8.8, sync OK, masternode visible from http://darkcoin.io/masternodes.txt and http://drk.poolhash.org/darksend.html and by a separate client

I don't know what to do
Anyone know the cause/fix to this? I'm having the same problem across all my masternodes.
 

fernando

Powered by Dash
Dash Core Team
Moderator
Foundation Member
May 9, 2014
1,527
2,058
283
I updated to 0.10.8.8. Everything seems to be working fine. MNs are on every list and fully synced with the right fork. However, one of them has already received a payment according to explorer.darkcoin.io but it doesn't show up in the MN's wallet. I was hours ago (block 74700) and it doesn't show up yet. Any idea?
 

atavacron

Member
Apr 27, 2014
45
16
48
I updated to 0.10.8.8. Everything seems to be working fine. MNs are on every list and fully synced with the right fork. However, one of them has already received a payment according to explorer.darkcoin.io but it doesn't show up in the MN's wallet. I was hours ago (block 74700) and it doesn't show up yet. Any idea?
Yeah, I've got the same problem. Nothing in any of my MN wallets, just the 1000DRK.
 

fernando

Powered by Dash
Dash Core Team
Moderator
Foundation Member
May 9, 2014
1,527
2,058
283
Yeah, I've got the same problem. Nothing in any of my MN wallets, just the 1000DRK.
Just wait, if it is in the blockchain you'll get it when it gets to 120 confirmations. I just received my payment.
 

donho

Member
Masternode Owner/Operator
Apr 16, 2014
96
20
58
Hi,

My masternode receive just this error, no payment:

2014-05-25 23:09:32 !coins.IsAvailable COutPoint(cfa73aeff245e44e86b9d18a703c471cfa8a7621e8a86eb48e97928edb077837, 1)
2014-05-25 23:09:32 ERROR: CTxMemPool::acceptableInputs() : inputs already spent

up to date 10.8.8, sync OK, masternode visible from http://darkcoin.io/masternodes.txt and http://drk.poolhash.org/darksend.html and by a separate client

I don't know what to do
Where do you see this error?
My MN is on both masternodelists so I assumed it's configured correctly. But apparently that's not necessarily true.
Is there any way to check for a working MN besides getting paid? Because with current unregular payments and bad luck it can take days to get a payment... So when should I get worried? 2days from now, or 3days? And then what? I try to fix it and I will have to wait another couple of days to see if it's working now...
I understand that one can see the pubkey of the Masternodes that got voted on on the blockexplorer. So I figured all Masternodes that received at least 1 vote so far must be configured correctly, but I have no idea how to find out the pubkey of my Masternode.
I think we need an easy way to check if your Masternode is (still) getting votes
 

yellowcox

New Member
Apr 23, 2014
15
3
3
It's from the debug.log file.

And I received answer on bitcointalk:

- Might be not your input.
- I've always seen stuff like that in the logs, never worried about it.

- i have same errors , but i just got my first payment , so i think it is fine