I did a diff and see that difference. You can also see the difference at:
https://github.com/darkcoin/darkcoin/compare/darkcoin:v0.10.15.13...master
v0.10.15 - Onyx Release
- Thread starter eduffield
- Start date
https://github.com/darkcoin/darkcoin/compare/darkcoin:v0.10.15.13...master
Hopefully flare's newfangled multi-Masternode wallet. There's 19000DRK been through that address today.
https://chainz.cryptoid.info/drk/address.dws?Xgyie615vTpBNmR2Nz7Z17GoAAcQLJfugm.htm
[/QUOTE][/QUOTE]
Another suspicious address is XvH3qoo6F8c9yLCunVaAFt1rY7xj8ngXji as all its payments are from innmlist or not detected. How effective will the enforcement be in terms of closing these exploits?
My masternode finally runs more stable for the past 8 hours. However, I'm not sure when I will get paid as many payments go to unknown version and non-master node such as XwzmEE1cJ6HG84CgJvAt7ADmJ8W9Wh65Tq.
Are you guys who had disconnect problem still having the disconnect problem?
Why are there so many partially inactive nodes on drk.mn these days? It used to be 100% for most active masternodes before Onyx.
eduffield
Can you please comment why some are still experiencing inactive masternodes when we are at 70-80% network on onyx. Further, can you please address the no masternode payee (no masternode is getting paid) and the RC3 nodes getting paid on occasion. I feel like there are numerous people here waiting to hear from you as it relates to these things.
Can you please comment why some are still experiencing inactive masternodes when we are at 70-80% network on onyx. Further, can you please address the no masternode payee (no masternode is getting paid) and the RC3 nodes getting paid on occasion. I feel like there are numerous people here waiting to hear from you as it relates to these things.
Removed this from BCT as things are slightly tenser there than they are here, but maybe someone can smack some sense into me. What I'm wondering is... with the Onyx update, masternodes are paid in a predictable manner. Are the masternode payee and the masternode selected for mixing determined by the same means? I.E. is the masternode that is selected for mixing predictable by examining previous payouts!? Or are the two determined in different ways?
*actually its pretty tense in here too.
*actually its pretty tense in here too.
Someone recommended messing around with the peers.dats. I'd been having a lot of trouble with one MN, but removed them on both the local and remote wallets and so far so good, its been like 4 hours which isn't much but it wasn't doing that well before.
How do I remove peers.dat from my remote wallet? I don't know Ubuntu that well.
https://drk.mn/masternodes.html
When I checked this morning, my new (and first) masternode was said partially inactive and has now turned completely inactive, though the daemon is still running on my VPS... I noticed many MN were also disconnecting, anyone knows about it?
When I checked this morning, my new (and first) masternode was said partially inactive and has now turned completely inactive, though the daemon is still running on my VPS... I noticed many MN were also disconnecting, anyone knows about it?
Remove peers.dat after stopping the daemon remotely, wait a few minutes, start it. Delete peers.dat locally, run the wallet and issue masternode start. Grep your ip and see if it is 1. No one knows why they are flipping inactive. Before it was on the basis of the network being conflicted between RC5 and onyx but now we have the majority and it is still happening...
Thanks for the trick! I'll try it tonight as I don't have access to my local wallet right now. I hope we can identify the source of the issue soon, though...
I can hold my breath for only so long...Will migrate my masternodes to the new setup scheme and will capture all i did
Yeah, worked more or less, but start-many is still alpha and has a flaw in 0.10.16.0 - will need to compile 0.10.16.1 first.
Can you please get Evan to address what's going on with the masternode inactivity with 70-80% of the network on Onyx as well as the no paid masternode blocks and occasional RC3 nodes paid?
He is already aware of the the network fragmentation (causing the disconnect MN) and unpaid/wrong paid blocks.
Is this something that will be fixed through enforcement, cleaning up the masternode lists from axing old protocols or is this going to need a new push for fixes?
As far as i know this will be fixed through enforcement.
If you want to do something against your masternode orphaning and dropping off the network (through fragmentation) and know how to compile on your own, you could try to set the protocol min version to 70043 here
https://github.com/darkcoin/darkcoin/blob/master/src/version.h#L34
This will disallow old masternodes to connect to your new one and will reduce network fragmentation.
Ya, getting that a lot as well. What's really weird to me is that from each MN IP that I log into, it will show up :1, but checking my other nodes will show :0. So for example logging into
mn a will show a:1 b:0 c:0
mn b will show a:0 b:1 c:0
mn c will show a:0 b:0 c:1
They see themselves on the network but not my other ones. --a
EDIT: Deleted peers.dat on local, will try on remote as well and see. Seems to have fixed so far. Will see in the morning
EDIT2: No problems as of deleting peers and all the new patches. Looks nice and stable now! =D
Last edited by a moderator:
Is this going to be one of those cases where we are going to draw this out another few weeks when 90% isn't possible due to coinmine.pl no longer complying? I feel like the pool police were prompt about getting the news out and all the majors to the point of what would have been around 85% updated in a few days time. Coinmine is about 15% so their decision to stop paying says a lot. What happens if other pools do the same thing knowing that 90% isn't possible and the November deadline is still a few weeks away? Makes sense to be 20% more profitable on blocks found, don't you think?
There must be some bug in the code as i did not touch anything since upgrade. I restarted daemon and hope it will pay correctly. Here is wallet log:
Getinfo gives me this:
Code:
2014-10-21 04:21:20 ThreadRPCServer method=getblockcount
2014-10-21 04:21:20 ThreadRPCServer method=getmininginfo
2014-10-21 04:21:27 received block 000000000002c624d1ed15f062f44cefaaf81da291076e3068297fdf36efe6dd peer=33
2014-10-21 04:21:27 CheckBlock() : Couldn't find masternode payment(0) or payee(1).
2014-10-21 04:21:28 CheckBlock() : Couldn't find masternode payment(0) or payee(1).
2014-10-21 04:21:28 Committing 19 changed transactions to coin database...
2014-10-21 04:21:28 SetBestChain: new best=000000000002c624d1ed15f062f44cefaaf81da291076e3068297fdf36efe6dd height=156118 log2_work=60.278239 tx=608636 date=2014-10-21 04:20:32 progress=0.999999
2014-10-21 04:21:28 CreateNewBlock: Failed to detect masternode to pay
2014-10-21 04:21:28 CreateNewBlock(): total size 1000
2014-10-21 04:21:28 CheckBlock() : Couldn't find masternode payment(0) or payee(1).
2014-10-21 04:21:28 send last getblocks for 000000000002c624d1ed15f062f44cefaaf81da291076e3068297fdf36efe6dd peer=31
2014-10-21 04:21:29 received block 000000000017ba7b98225f137ed9f0b95959d97b711ebf62f88ed28ca81a95c6 peer=30
2014-10-21 04:21:29 Committing 2 changed transactions to coin database...
2014-10-21 04:21:29 SetBestChain: new best=000000000017ba7b98225f137ed9f0b95959d97b711ebf62f88ed28ca81a95c6 height=156119 log2_work=60.278248 tx=608637 date=2014-10-21 04:21:02 progress=1.000000
2014-10-21 04:21:29 send last getblocks for 000000000017ba7b98225f137ed9f0b95959d97b711ebf62f88ed28ca81a95c6 peer=34
2014-10-21 04:21:29 send last getblocks for 000000000017ba7b98225f137ed9f0b95959d97b711ebf62f88ed28ca81a95c6 peer=950
2014-10-21 04:21:29 CreateNewBlock: Failed to detect masternode to pay
2014-10-21 04:21:29 CreateNewBlock(): total size 1000
2014-10-21 04:21:29 CheckBlock() : Couldn't find masternode payment(0) or payee(1).
2014-10-21 04:21:30 ProcessSyncCheckpoint: sync-checkpoint at 000000000003b172bd55a1ca43bfe1f124aecb970223202d24dc0a08bdeee132
2014-10-21 04:21:36 send last getblocks for 000000000017ba7b98225f137ed9f0b95959d97b711ebf62f88ed28ca81a95c6 peer=1122
2014-10-21 04:21:44 CDarkSendPool::UpdateState() == 3 | 3
2014-10-21 04:21:46 getblocks -1 to 0 limit 500 peer=1122
2014-10-21 04:21:50 ThreadRPCServer method=getinfo
2014-10-21 04:21:50 keypool reserve 15937
2014-10-21 04:21:50 keypool return 15937
2014-10-21 04:21:50 ThreadRPCServer method=getdifficulty
2014-10-21 04:21:50 ThreadRPCServer method=getblockcount
2014-10-21 04:21:50 ThreadRPCServer method=getmininginfo
2014-10-21 04:22:00 ThreadRPCServer method=help
2014-10-21 04:22:00 ThreadRPCServer method=listaccounts
2014-10-21 04:22:00 ThreadRPCServer method=getbalance
2014-10-21 04:22:00 ThreadRPCServer method=listaccounts
2014-10-21 04:22:00 ThreadRPCServer method=getbalance
2014-10-21 04:22:01 ThreadRPCServer method=listaccounts
2014-10-21 04:22:01 ThreadRPCServer method=getbalance
2014-10-21 04:22:08 CDarkSendPool::DoAutomaticDenominating - Darksend is disabled
2014-10-21 04:22:21 ThreadRPCServer method=getinfo
2014-10-21 04:22:21 keypool reserve 15937
2014-10-21 04:22:21 keypool return 15937
2014-10-21 04:22:21 ThreadRPCServer method=getdifficulty
2014-10-21 04:22:21 ThreadRPCServer method=getblockcount
2014-10-21 04:22:21 ThreadRPCServer method=getmininginfo
2014-10-21 04:22:24 CDarkSendPool::UpdateState() == 3 | 3
2014-10-21 04:22:38 ThreadRPCServer method=listsinceblock
2014-10-21 04:22:48 ThreadRPCServer method=submitblock
2014-10-21 04:22:48 CheckBlock() : Couldn't find masternode payment(0) or payee(1).
2014-10-21 04:22:48 CheckBlock() : Couldn't find masternode payment(0) or payee(1).
2014-10-21 04:22:48 AddToWallet f5186c8346d67b52b0feecf208bccaf5fc9f9c1a471e2e99a1646c00ea72c7af new
2014-10-21 04:22:48 Committing 2 changed transactions to coin database...
2014-10-21 04:22:48 SetBestChain: new best=0000000000029b04f507250d54c87e0a3f1ec4c18f7679783f3e96834ed584be height=156120 log2_work=60.278256 tx=608638 date=2014-10-21 04:22:24 progress=1.000000
2014-10-21 04:22:48 CreateNewBlock: Failed to detect masternode to pay
2014-10-21 04:22:48 CreateNewBlock(): total size 1000
2014-10-21 04:22:48 CheckBlock() : Couldn't find masternode payment(0) or payee(1).
2014-10-21 04:22:48 ThreadRPCServer method=getblock
2014-10-21 04:22:48 received getdata for: block 0000000000029b04f507250d54c87e0a3f1ec4c18f7679783f3e96834ed584be peer=30
2014-10-21 04:22:48 received getdata for: block 0000000000029b04f507250d54c87e0a3f1ec4c18f7679783f3e96834ed584be peer=34
2014-10-21 04:22:48 received getdata for: block 0000000000029b04f507250d54c87e0a3f1ec4c18f7679783f3e96834ed584be peer=109
2014-10-21 04:22:48 received getdata for: block 0000000000029b04f507250d54c87e0a3f1ec4c18f7679783f3e96834ed584be peer=950
2014-10-21 04:22:48 received getdata for: block 0000000000029b04f507250d54c87e0a3f1ec4c18f7679783f3e96834ed584be peer=31
2014-10-21 04:22:49 received getdata for: block 0000000000029b04f507250d54c87e0a3f1ec4c18f7679783f3e96834ed584be peer=976
2014-10-21 04:22:49 ProcessSyncCheckpoint: sync-checkpoint at 0000000000182904a6af0bef966eaf47d419165158f4e184982cacb9244e2611
2014-10-21 04:22:49 received getdata for: block 0000000000029b04f507250d54c87e0a3f1ec4c18f7679783f3e96834ed584be peer=1122
2014-10-21 04:22:50 Flushing wallet.dat
2014-10-21 04:22:50 Flushed wallet.dat 203ms
2014-10-21 04:22:53 ThreadRPCServer method=getinfo
2014-10-21 04:22:53 keypool reserve 15937
2014-10-21 04:22:53 keypool return 15937
Code:
{
"version" : 101513,
"protocolversion" : 70043,
"walletversion" : 60000,
"balance" : hidden,
"darksend_balance" : 0.00000000,
"blocks" : 156140,
"timeoffset" : 0,
"connections" : 8,
"proxy" : "",
"difficulty" : 3060.72107820,
"testnet" : false,
"keypoololdest" : 1413472265,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
- Apr 8, 2014
- 1,971
- 1,339
- 1,283
coinmine.pl did the restart of the server ~3 h ago and it works again...
edit: strange thing IS that all version of masternodes are paid by the pool who has updated to the onyx bianries...
edit: strange thing IS that all version of masternodes are paid by the pool who has updated to the onyx bianries...
- Apr 8, 2014
- 1,971
- 1,339
- 1,283
Camo I`m going to delete peers.dat now on both sides and see if the MNs will not drop....
anyway RC5 was the best version so far....meaby after enforcment ONYX will get the stability it should have..
anyway RC5 was the best version so far....meaby after enforcment ONYX will get the stability it should have..
I did on both sides and did not help !
Funny as they are popping in and out, so i guess giving it time (and not just switch on all the time) to connect by itself works !?
- Apr 8, 2014
- 1,971
- 1,339
- 1,283
- Apr 8, 2014
- 1,971
- 1,339
- 1,283
Guys we have a cure
To avoid the ONYX pools to pay MNs of all versions they need to add a line, look below
------
Flare said:
So yes, pools should update their MIN_PEER_PROTO_VERSION to 70043
MIN_PEER_PROTO_VERSION to 70043 here: https://github.com/darkcoin/darkcoin/blob/master/src/version.h#L34
To avoid the ONYX pools to pay MNs of all versions they need to add a line, look below
------
Flare said:
So yes, pools should update their MIN_PEER_PROTO_VERSION to 70043
MIN_PEER_PROTO_VERSION to 70043 here: https://github.com/darkcoin/darkcoin/blob/master/src/version.h#L34