Yes, my list matches your list. The duplicated MN's are disappearing. Great! But, according to my understanding, it is not a permanent fix. Evan is working on a more proper solution in the future.
v0.10.15 - Onyx Release
- Thread starter eduffield
- Start date
Evan meant that these MN entries are unique and valid. You can check it with "masternode list vin". You will notice that the vins (1000DRK) used differ and really belong to the owner of 37.46.114.158 - the private key of the 1000DRK is used to sign the entry, no way to claim others coins as his (this bug was fixed in 0.10.14.1)
flare, thanks for the explanation. It is good to know. I did not know the "vin" option after "masternode list". Where can a newbie like me find all the documentation if there is any?
Yeah, documentation lacks a bit - if you like to write something to your own you are welcome to contribute on our documentation wiki
--> http://wiki.darkcoin.qa/display/DRK/Darkcoin Documentation Home
not exactlyworksCode:masternode list help
it will actually give you an error just like
Code:
darkcoind masternode list smth
error: {"code":-1,"message":"list supports 'active', 'vin', 'pubkey', 'lastseen', 'activeseconds', 'rank'\n"}
Very happy with v.16! Hopefully we're fully behind these issues we've been having! Had to defend us on Twitter a couple of times today....don't worry, the haters have nothing...new people are starting Masternodes every day! Could use any help you guys could give with the DTPI....See my sig for details. Until the next time, Darkcoiners!
% darkcoind masternode list | sort | uniq -c | grep -v '^[^"]*1'
2 "37.46.114.158:9999" : 1,
Only two MN's with a duplicated IP address now. They are:
"37.46.114.158:9999" : "XwY1a8oh7Pbt6ApcyTXbezrBGaphF39CyY",
"37.46.114.158:9999" : "XvH3qoo6F8c9yLCunVaAFt1rY7xj8ngXji",
The strange part is that XwY1a8oh7Pbt6ApcyTXbezrBGaphF39CyY is not listening to port 9999 while XvH3qoo6F8c9yLCunVaAFt1rY7xj8ngXji is not listed on drk.mn now but shows up on masternode list command. It got 9 MN payments in the past 24 hrs all from wafflepool.
v0.10.15.16 is pretty stable now. The only question that is left is fair payment after enforcement. I think both miners and masternode owners should be considering to each other because MN's is a great feature for DRK and it takes money to buy/mine 1000 DRK and plus time/risk to run a masternode. So, both miners and masternode owners are not too different. Just my thought and I don't want to be off topic here again. So, I shall stop here.
2 "37.46.114.158:9999" : 1,
Only two MN's with a duplicated IP address now. They are:
"37.46.114.158:9999" : "XwY1a8oh7Pbt6ApcyTXbezrBGaphF39CyY",
"37.46.114.158:9999" : "XvH3qoo6F8c9yLCunVaAFt1rY7xj8ngXji",
The strange part is that XwY1a8oh7Pbt6ApcyTXbezrBGaphF39CyY is not listening to port 9999 while XvH3qoo6F8c9yLCunVaAFt1rY7xj8ngXji is not listed on drk.mn now but shows up on masternode list command. It got 9 MN payments in the past 24 hrs all from wafflepool.
v0.10.15.16 is pretty stable now. The only question that is left is fair payment after enforcement. I think both miners and masternode owners should be considering to each other because MN's is a great feature for DRK and it takes money to buy/mine 1000 DRK and plus time/risk to run a masternode. So, both miners and masternode owners are not too different. Just my thought and I don't want to be off topic here again. So, I shall stop here.
where is chaeplin ? http://drk.poolhash.org/masternode.html nodes are still on 0.10.15.13 and they are acting really strange now
Haven't got any MN payments yet after the recent updates. How long will this situation continue?
Who would play Evan in films?
Let's discuss it here (need to stay on topic here...)
https://darkcointalk.org/threads/just-for-fun-darkcoin-the-movie.2736/
Until you receive a payment.
I've had 7 'wins' today across 6 Masternodes, although 3 of them have been tx_0_vout_1's, thanks coinotron and pool_unknown 261. Enforcement at block 158000 (now at 157530 as I write this) if pool compliance is 80%, but right now we're at just under 70%, thanks to shitbag XhBLSR1HhoaWrdGgrjCHxJkCWWiFFhveHs
- Apr 8, 2014
- 1,971
- 1,339
- 1,283
How can we find out our masternode status on the network besides the drk.mn and drk.poolhash.org websites? Even if the MN payment system is not enforced, we should get a fair share from pool operators who are not blocking the payments. There is another thread "Darkcoin is more centralized than we think?" under General Discussion. It seems that the payment is controlled by the developers. How can I be sure that entity is seeing my MN and give me a fair share of the payments? I think many haven't been paid for several days while some are getting several payments per day.
What you're asking is the "round-robin" payment which doesn't happen until enforcement which probably will happen in less than 24 hours, so be patient
ssh into your server and type 'masternode list | grep <server IP>' - you should get back '<server IP>: 1'
I think this only tells you that your node sees itself as masternode. Some reported earlier that he did not see his other nodes on different machine. And, the inactivity shown in drk.mn or poolhash is about how many nodes see your node as a masternode. Right?
Use your desktop client then. But looks like the list may be cached for some time.
If your MN reports itself as a Masternode, it's a Masternode, end of story, fiddling with it is pointless.
Other MNs or your local daemon may or may not agree, they all should if they are the same protocol version, but eg. chaeplin's MNs which supply the data to his page are all still 10.15.13, so cannot be trusted to provide accurate information.
I have scripts on my masternode to check its status every 3 minutes. After the 0.10.15.16 patch, it is still on the MN list. However, I have another script checking poolhash every 3 minutes. It was disconnected by one node after 8 hours, by all other nodes after 2 additional hours. One scenario is that someone sees my node could get a MN payment and he starts banning my node by sending fake messages to others on the network. Then, the network bans me and if the attacker does this to many nodes, they have a very high chance of getting the payment. This is just my guess because I also got some not_detected payments.
EDIT: Another 5 hours later, the node did not appear as a MN on drk.poolhash.org! So, when others do not see my node as a masternode, how will it get paid as a masternode? I wish drk.mn has the API so that I can write a script to check the activity of my MN on it.
Last edited by a moderator:
Versions after 0.10.15.13 at the moment all have the same PROTOCOL_VERSION.
I did italicise the 'should.'
10.15.13 lacks a few little fixes that Evan put into later builds. I've so far had no inconsistencies across any of my 10.15.16's.
Having a MN go a day or two (or three) without a payment isn't that unusual. The fothcoming system should hopefully correct this.
Or, the attacker has figured out how to do this in a stealth manner so that we don't see it at all. After all, this is darkcoin so attack should go dark as well. :sad: BTW, the patch that prevents the node from reporting dying is increasing some time window. As someone who is not familiar with the entire source code, I think that would not really fix the problem we are seeing. Of course, the enforcement may fix it. So, I can only wait patiently as Moli suggested. Hope the enforcement will not disappoint me.I did italicise the 'should.'
10.15.13 lacks a few little fixes that Evan put into later builds. I've so far had no inconsistencies across any of my 10.15.16's.
EDIT: "attack should go dark as well" is a bad joke on myself. Don't mean to imply anything that may offend anyone.
that last update really did the trick
- no more disconnects
- payments are rolling
well done TEAM !!
- no more disconnects
- payments are rolling
well done TEAM !!
