11.2 - Dash Release

Yes, I can also confirm that 5 of my nodes haven't been paid in over 5 days as well.

Having said that, I'm not ready to throw in the towel on my faith that it will be sorted out. It has worked before, something must need to be fixed, and if anyone can do it, it's Evan. Hang in there!
 
TaoOfSatoshi said:
Yes, I can also confirm that 5 of my nodes haven't been paid in over 5 days as well.

Having said that, I'm not ready to throw in the towel on my faith that it will be sorted out. It has worked before, something must need to be fixed, and if anyone can do it, it's Evan. Hang in there!
Click to expand...

It doesn't look like 5+ days is unusual. I just pulled some data from eight nodes and 7 of 8 had consecutive payments cycles of more than 5 days.
 
orangecycle said:
It doesn't look like 5+ days is unusual. I just pulled some data from eight nodes and 7 of 8 had consecutive payments cycles of more than 5 days.
Click to expand...
So, it would seem, if the number of nodes is correct, and blocks have been producing at around their normal rate, that something has run amok with enforcement.

eduffield Could you please shed some light on this if you get a second?
 
Arghhh.. To those who have long time without MN payments: few parts of new masternode manager module was vulnerable so attacker was able to enter list more then once with his MNs and got some extra... Evan patched the reference node so payments should come back to more regular schedule from now...

That was my fault... Sorry... :sad:
 
UdjinM6 said:
Arghhh.. To those who have long time without MN payments: few parts of new masternode manager module was vulnerable so attacker was able to enter list more then once with his MNs and got some extra... Evan patched the reference node so payments should come back to more regular schedule from now...

That was my fault... Sorry... :sad:
Click to expand...
That's OK bud, we could never be mad at you with the amount you do around here. Good to have an explanation, and good to hear it's been fixed! I never doubted you guys for a second.
 
UdjinM6 said:
Arghhh.. To those who have long time without MN payments: few parts of new masternode manager module was vulnerable so attacker was able to enter list more then once with his MNs and got some extra... Evan patched the reference node so payments should come back to more regular schedule from now...

That was my fault... Sorry... :sad:
Click to expand...
So... credit to thelazier who found this hole?
 
UdjinM6 said:
Arghhh.. To those who have long time without MN payments: few parts of new masternode manager module was vulnerable so attacker was able to enter list more then once with his MNs and got some extra... Evan patched the reference node so payments should come back to more regular schedule from now...

That was my fault... Sorry... :sad:
Click to expand...

No problem - glad to have you in the team. Given the delays, the attacker stole about 150 extra blocks per day. Thanks for bringing this to an end.
 
UdjinM6 said:
Arghhh.. To those who have long time without MN payments: few parts of new masternode manager module was vulnerable so attacker was able to enter list more then once with his MNs and got some extra... Evan patched the reference node so payments should come back to more regular schedule from now...

That was my fault... Sorry... :sad:
Click to expand...
Great job. Keep up the great work. Everyone makes mistakes important part is to learn from them.
 
UdjinM6 , I found in my debug.log...

2015-04-12 00:51:56 mnw - winning vote - Vin CTxIn(COutPoint

(20c6c0e04bb5eb991f7800bbaf1d4a52b28a96a93b09f45621547c737c82cd40, 0), scriptSig=)

Addr XiFBuoJuRscLfF8aViUZMh5rjKhigcN6oa Height 250906 bestHeight 250896

2015-04-12 00:58:10 mnw - winning vote - Vin CTxIn(COutPoint

(0a628d885cf27a5fae0e651249c71279e907fbddd4c9e4acc231abeaa593db40, 0),

scriptSig=e4324d438e1e6db0df6d356c) Addr Xtm8ciUeP6pVRWJLA3DLuELfuuR5btyDNp Height

250907 bestHeight 250897

2015-04-12 00:59:55 mnw - winning vote - Vin CTxIn(COutPoint

(33cc4b19f01553b414bedfeb88ff39fc35b60d2b0c33aca07d6fcb1f32a63b92, 0),

scriptSig=0cabc508663cc53e966b9ebd) Addr XqLmNGP9CGTHnms3XiRTfFZoHHwg73GTJw Height

250908 bestHeight 250898

2015-04-12 01:01:05 mnw - winning vote - Vin CTxIn(COutPoint

(8e92386f954c621dff417316781c8f732bf91e47dff9f96b3852e656d925a1f7, 0),

scriptSig=e6bb8e56f8d6b6e3aeba1b08) Addr XeVXEjY39VR8gTD69mLTaNcHeh3ohh3vdR Height

250909 bestHeight 250899

2015-04-12 01:02:38 mnw - winning vote - Vin CTxIn(COutPoint

(a53c95bf8578dc0593524d0440c83accaf92662cc3ea10f6e71b8f4962bab93e, 0),

scriptSig=28857d0b5f078200ee44eaa2) Addr XuwgPFZzpeGWu8TSwD3bSSajdc2B7TgJfX Height

250910 bestHeight 250900

2015-04-12 01:03:50 mnw - winning vote - Vin CTxIn(COutPoint

(ac714466f00d7ebda0e80dcae484d2c7369afb9cd22c803dfbfb70fc516ab59e, 0),

scriptSig=418f288bf7b030b59af1cead) Addr XjmJxnnsj9TCYtmcS1Dd14mhy93AkfFAfQ Height

250911 bestHeight 250901


2015-04-12 01:05:41 mnw - winning vote - Vin CTxIn(COutPoint

(36a6e9b46abdbbf570fff1994b5da506927b4d9ef48c09ab315cad756b627a99, 1), scriptSig=)

Addr Xfuho8Z9K5DdWqYnDw3XcopXQWYKdAg9LR Height 250912 bestHeight 250902
Click to expand...
Do the transactions (in boldface) from block 250907 to block 250911 belong to the bad actor? Their scriptSig are different than other normal scriptSigs. And those addresses belong to the same person: https://chainz.cryptoid.info/dash/wallet.dws?857577.htm
 
so there are bad actors/hackers that actively trying to cheat the system, especially with such new code releases? are they looking through the change logs/new code to find vulnerabilities ?
 
jiggytom said:
so there are bad actors/hackers that actively trying to cheat the system, especially with such new code releases? are they looking through the change logs/new code to find vulnerabilities ?
Click to expand...
I hope so. The more attacks, the more solid DASH becomes.

Can someone explain to me what the reference node is?

Ok, so poking back in this thread, it looks or sounds like the reference node is a node that keeps tabs on all the masternodes. When they enter the system, when they are no longer pinging, etc... and controls which masternodes are up for voting as the current working masternode.

Is this correct?
 
Last edited by a moderator:
Today, my son's mn finally got paid. Last payment was April 7. So it should be on track again :)

Question:

Is there any way that the reference node could be integrated into each wallet, with another consensus thingy (love my vocabulary, LOL) It seems necessary, therefore it needs to be decentralized. If all it does is keep track of where each masternode is on the list, a secondary, short blockchain could be added, who's older info expires at some point. Say it holds a month's worth, and dumps the older info to keep it short and sweet ??

I know the node does more, more like serves up eligible masternodes to be voted in, we don't just go down a list, right? If we did, then it would be too predictable as to which masternode would be next, no?
 
Last edited by a moderator:
Not to cause panic or anything but havn't heard from Evan for almost a week :) Hope he is OK
 
You must log in or register to reply here.
Back
Top