Please Update To v10.14.1 - Masternode Security Update

HinnomTX said:
The rogue client is not actually a masternode owner. He/she is not staking any coins for the exploit. He/she can keep the exploit running indefinitely. However, the rogue's future earnings will evaporate as more peers upgrade to 0.10.14.x. There is a stricter version of masternode payment enforcement which is in the works, and rumor has it will require a hard fork. This will cut off the exploit for good.
Click to expand...
Thanks, was browsing trough the BCT thread and was trying to figure out how the fix came to pass :)
 
What is your personal record? The maximum number of days that a masternode didn't get paid since setting up for the first time? This is a total turn off and not sure if I should set up more MNs. I would have made more money by trading on an exchnage :mad::mad::mad:

4 days not a single payment.

Edit: If I withdraw 1000 drk to trade on an exchnage and then send it back to the masternode account after Evan fixes fair payment issue, would it automatically start working again?
 
Last edited by a moderator:
Light said:
What is your personal record? The maximum number of days that a masternode didn't get paid since setting up for the first time? This is a total turn off and not sure if I should set up more MNs. I would have made more money by trading on an exchnage :mad::mad::mad:

4 days not a single payment: http://drk.poolhash.org/masternode.html?srch&nmstr=XyHjiBk59amY7HhHqoy6nue2y4Cnqawtzq

Edit: If I withdraw 1000 drk to trade on an exchnage and then send it back to the masternode account after Evan fixes fair payment issue, would it automatically start working again?
Click to expand...
Light, If you send the 1000 drk to an exchange, your MN is down and later you have to set it up all over again.
 
Last edited by a moderator:
moli said:
Light, If you send the 1000 drk to and exchange, your MN is down and later you have to set it up all over again.
Click to expand...

All over again? I don't think so. I just send back 1000DRK in one piece and start it :tongue:
 
DrkMiner said:
For some reason the pool nicehash keeps paying another MN than mine.


innmlist: XtzrcCsxS3eA3LejArCt7F7BdWC33MR9ry

My MN is on the list and should to be paid, but other MN id being paid. weird that it happens only with nicehash and to the same address.
Click to expand...
Yeah, he is tricking the v14 system, will come to an end with v15 aka Onyx

pBHp2.jpg
 
What about it shows a "-" in the Masternode payee column? I am seeing this at drk dot poolhash dot org when search for p2pool. Please see message #149 on the "v10.15 - Onyx Release" thread under darkcointalk for details. Is this another exploit or just the same old 0.10.14.1 exploit?

EDIT: My masternode was ":1" when this happened. Then, shortly after the other address getting paid, my node was shown as ":0".
 
Last edited by a moderator:
GermanRed+ said:
What about it shows a "-" in the Masternode payee column? I am seeing this at drk dot poolhash dot org when search for p2pool. Please see message #149 on the "v10.15 - Onyx Release" thread under darkcointalk for details. Is this another exploit or just the same old 0.10.14.1 exploit?

EDIT: My masternode was ":1" when this happened. Then, shortly after the other address getting paid, my node was shown as ":0".
Click to expand...

Sounds like the miner kept the whole reward and no masternode was paid. Because enforcement is off, solo miners and other pools don't have to pay out the current 20% to masternodes. It's all in good faith. When enforcement is turned on, mid-November or 90%, they'll be orphaned.
 
oblox said:
Sounds like the miner kept the whole reward and no masternode was paid. Because enforcement is off, solo miners and other pools don't have to pay out the current 20% to masternodes. It's all in good faith. When enforcement is turned on, mid-November or 90%, they'll be orphaned.
Click to expand...

That was my first guess but when I saw this was paid to another address as a masternode, I started to wonder. If you go to drk dot mn/blocks dot html and search p2pool under Blocks Detail (last 24h), you will see MN payment instead of generation from mining. It lists the XwzmEE1cJ6HG84CgJvAt7ADmJ8W9Wh65Tq address as MN. It will be good to hear from the developers or elberethzone about this.

EDIT: I also think my MN did not went from ":1" to ":0" when the payment went to another address. It did that roughly after 1 hour. (But, I may be wrong here. I will check and confirm this if it goes down again.)
 
GermanRed+ said:
That was my first guess but when I saw this was paid to another address as a masternode, I started to wonder. If you go to drk dot mn/blocks dot html and search p2pool under Blocks Detail (last 24h), you will see MN payment instead of generation from mining. It lists the XwzmEE1cJ6HG84CgJvAt7ADmJ8W9Wh65Tq address as MN. It will be good to hear from the developers or elberethzone about this.

EDIT: I also think my MN did not went from ":1" to ":0" when the payment went to another address. It did that roughly after 1 hour. (But, I may be wrong here. I will check and confirm this if it goes down again.)
Click to expand...

XwzmEE1cJ6HG84CgJvAt7ADmJ8W9Wh65Tq that's the exploit address, probably from a p2pool node running 10.14.1.

Further blocks found by miner XhBLSR1HhoaWrdGgrjCHxJkCWWiFFhveHs used to pay to their own masternode ending in sek but now he just takes the full block reward directly. Again, because enforcement is off.

When grepping your ip in the masternode list from the daemon, is it listed as 1? Do you have green lights on poolhash.org? Drk.mn isn't updated so don't go off that.
 
oblox said:
XwzmEE1cJ6HG84CgJvAt7ADmJ8W9Wh65Tq that's the exploit address, probably from a p2pool node running 10.14.1.

Further blocks found by miner XhBLSR1HhoaWrdGgrjCHxJkCWWiFFhveHs used to pay to their own masternode ending in sek but now he just takes the full block reward directly. Again, because enforcement is off.

When grepping your ip in the masternode list from the daemon, is it listed as 1? Do you have green lights on poolhash.org? Drk.mn isn't updated so don't go off that.
Click to expand...

Yes, it is green on drk dot poolhash dot org but red on drk dot mn. Both started green. If I did not make a mistake, grepping masternode list was 1 until it reached the next port check time on drk dot mn. Here is the timeline as I remember:

RED on DRK dot mn; GREEN on POOLHASH ; 1 (grepping masternode list)
DRK dot mn port check (next check reached zero); Inactive on POOLHASH; 0 (gripping)
Restart remote darkcoind without starting masternode on local is enough to bring it back to 1 but sometimes it need to restart masternode from the local wallet as well.
 
GermanRed+ said:
RED on DRK dot mn; GREEN on POOLHASH ; 1 (grepping masternode list)
Click to expand...

poolhash is already updated, drk.mn is stil on 0.10.14.1 and therefore not reporting in a reliable way, so just forget it for now.

GermanRed+ said:
Restart remote darkcoind without starting masternode on local is enough to bring it back to 1 but sometimes it need to restart masternode from the local wallet as well.
Click to expand...

The second one (having to restart the Masternode from the local wallet) is a known issue and reported here: http://jira.darkcoin.qa/browse/DRK-104
 
crowning said:
poolhash is already updated, drk.mn is stil on 0.10.14.1 and therefore not reporting in a reliable way, so just forget it for now.



The second one (having to restart the Masternode from the local wallet) is a known issue and reported here: http://jira.darkcoin.qa/browse/DRK-104
Click to expand...

I think I got a mess here. All the masternode monitoring sites and my own daemon is not reporting the same status. What I am seeing is completely random in behavior. Sometimes, the grep said 0 while green on drk.mn and red on poolhash. Sometime, it is green on poolhash but red on drk.mn. When I run masternode stop on my local wallet, it does not change the masternode from 1 to 0. Masternode start on the local wallet won't change it from 0 to 1 either. It is just so unpredictable that it feels like someone else is running his masternode somewhere else. I did try to regen the key for the masternode. But, it did not help.
 
crowning said:
drk.mn hasn't updated yet and therefore reports everything wrong.
Click to expand...

Not so sure about. Well, we already know that yellows are new green and reds are just pure evil miners :) But why woudl SuchPool suddenly turn into red? O_O That, I don't get. If it was a flaw of the site then all the yellows should turn into red too.

Edit: Where the hell is everybody? IRC is quiet, no one has any clue what's going on in bitcointalk, No news from @elberethzone either.
 
Light said:
Not so sure about. Well, we already know that yellows are new green and reds are just pure evil miners :) But why woudl SuchPool suddenly turn into red? O_O That, I don't get. If it was a flaw of the site then all the yellows should turn into red too.

Edit: Where the hell is everybody? IRC is quiet, no one has any clue what's going on in bitcointalk, No news from @elberethzone either.
Click to expand...

There's a life outside internet :tongue:
 
You must log in or register to reply here.
Back
Top