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.htm2015-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
scriptSig=e4324d438e1e6db0df6d356c) Addr Xtm8ciUeP6pVRWJLA3DLuELfuuR5btyDNp Height
250907 bestHeight 250897
2015-04-12 00:59:55 mnw - winning vote - Vin CTxIn(COutPoint
scriptSig=0cabc508663cc53e966b9ebd) Addr XqLmNGP9CGTHnms3XiRTfFZoHHwg73GTJw Height
250908 bestHeight 250898
2015-04-12 01:01:05 mnw - winning vote - Vin CTxIn(COutPoint
scriptSig=e6bb8e56f8d6b6e3aeba1b08) Addr XeVXEjY39VR8gTD69mLTaNcHeh3ohh3vdR Height
250909 bestHeight 250899
2015-04-12 01:02:38 mnw - winning vote - Vin CTxIn(COutPoint
scriptSig=28857d0b5f078200ee44eaa2) Addr XuwgPFZzpeGWu8TSwD3bSSajdc2B7TgJfX Height
250910 bestHeight 250900
2015-04-12 01:03:50 mnw - winning vote - Vin CTxIn(COutPoint
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
I hope so. The more attacks, the more solid DASH becomes.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 ?
ROFL.... I'm just having a good laugh because I can tease you and you're not upset with me... LOL... It's just funny that you're the only one that thought Evan went missing for a week... lol...You are being obsessive-compolsive moli What do you what rom this poor SpreadLight? Poor user is getting unwanted attention now lol
Are you gonna tie me to any user that has Light in their nick?
- please copy crash info (if any) provided in crash windowUdjinM6
- Win32 wallet crashed three times while DS mixing was running.
- After the last restart the wallet started getting collateral fees and so far it's got 5 collateral charges.
- Many DS inputs got locked on Coin Control and stayed unlocked (until the wallet was restarted).
- Some of my denominated inputs went from having 5 rounds to less rounds after sometime. Then they worked back up to 5 rounds again. Is this something new in the DS code?
I stopped my wallet after getting the 5th collateral fee and just now started it back up. So far it hasn't crashed and no collateral (yet). The DS rounds of some inputs went down and up and down again, making the completion bar go down and up and down... It seems taking longer for Darksend because of mixing twice..- please copy crash info (if any) provided in crash window
- could be connected with vvvv
- could be connected with ^^^^ will have a look
- yes, this can happen when mixing got a bit uneven because rounds now count from the shortest rounds "chain" i.e. if you have your inputs with 2 rounds and your inputs with 5 rounds mixing together they will end up with 2+1 = 3 rounds both. That means that you'll have some mixing done twice but otherwise shortest rounds "chain" could compromise you. However there is surely some place for optimization and smarter logic of choosing inputs to minimize that effect.
Yep and nope. Yep, because you sending many inputs and they are technically saying mixing together too. Nope, because mixing with your own outputs only instead of waiting for 3rd participant doesn't really help - it would be just the same as 2 participants mixing instead of 3 and therefore a lot less secure....
You mentioned "the shortest rounds 'chain'"... Does this mean now the denom inputs in our wallets are programmed to mix with each other and not necessarily have to wait/depend on other people for mixing pairs? I've noticed the DS message still says something like "Waiting for more entry (2/3)...", but are we at the point now denom inputs in a same wallet can be mixed internally with each other AND also with other external mixing pairs?
I got even more collaterals and that's ok if you have them ~ at every 10th mixing https://github.com/dashpay/dash/commit/ecd37e134eb1690fb008229b4f93a3ef5c6c66f9 - they are 10 times lower since 0.11.2: 0.1 DASH -> 0.01 DASH (but charging more often)
Your node has problems to connect to other nodes.2015-04-12 05:40:13 socket send error Connection timed out (110)
2015-04-12 10:50:07 socket recv error Connection reset by peer (104)
Hi, crowning, thank you for your reply.Your node has problems to connect to other nodes.
Does your network connection has hiccups or is VERY slow?
When you run a "ping" for a while, how are the response times? All almost equal (good) or with wide variations?
I had the same thing happen with 2 of my nodes. It looked like the server was fine. Dashd was running and responsive to commands. I restarted dashd anyway just to be sure. It lasted about 8 hours and then reset to 0. I have other nodes at the same location that had solid 0s. It looks like you have 5 chances to get dinged each day before your node gets delisted on the 6th one, so a 1 score shouldn't be a big deal.UPDATE:
At this very moment my MN's PoSe score fixed itself to "0" again. So, maybe, this kind of fluctuation in the score might be normal, after all.
Good findOK I think I`ve found visual bug
On new created wallet going to FILE/SENDING ADDRESS
when all is blank the Address label is not complete and it is impossible to change the width of the collumn.
Testing never enoughGood find
Just to keep you updated: I'll fix this, but unfortunately I can only reproduce it under Windows and my local build system for Windows is down for maintenance this weekend, so I'll need some more days to start this.