RC4 issues, bugs & feature requests

Status
Not open for further replies.
I'm on testnet testing windows wallet. Got over 6000 tdrk, set 8 rounds and amount to keep anonymized at 5000 drk. So far the wallet got 9 denominates and 2 "payment to yourself". After round 7 the wallet seems to get stuck with (19 locked) and 0 drk anonymized. It's been 3 hours and has not finished anonymizing. I guess this happens because of testnet? And mainnet is much better? (I haven't tried mainnet yet, probably will try it tomorrow.)
 
flare said:
Sure it gets attention, as every bug we had the last months.
Click to expand...

Thanks.

I only posted that because Evan's post yesterday said that it wasn't a bug but people were misunderstanding how Darksend works for large wallets. Good to hear the team will take a look.
 
There is an issue with using coin control to make payments to yrself to bundle inputs while Darksend+ is running,
sometimes the Darksend+ payment to yrself transaction will be processed before a manual payment to yrself has been processed. This leads to the manual payment to yrself not getting confirmed.

link here :

https://bitcointalk.org/index.php?topic=421615.msg8397861#msg8397861
https://bitcointalk.org/index.php?topic=421615.msg8398150#msg8398150
https://bitcointalk.org/index.php?topic=421615.msg8398191#msg8398191
https://bitcointalk.org/index.php?topic=421615.msg8398265#msg8398265

Chaeplin is testing it further.

solution looks to be simple :

Make sure you dont have darksend+ running when yr making payments to yrself with coin control.
Only switch it on when the manual payment to yrself has been confirmed (pref 6 times confirmed)

Maybe something can be done in code so these two payment to yrself (manual and those from Darksend+)
wont conflict with each other... maybe a warning to disable Darksend+ first before making manual payments to yrself ?
 
Not sure if this is a problem or not.. but I should have gotten a payment ( a few actually) for my MN

<jimbit_> this payment from wafflepool did not go to ME.. even tho I was the expected payee.
2014-08-17 14:56:54 120629 wafflepool 4182.75 5 1 Xy7NQQ5q4AqSjJags8eNbSRLWxAP9SeX7g RC4 (0.10.12.26+)
<jimbit_> payment should have went to XjYqHv5ibY9DujwbAjC84P1oS7JCyF9rUj
<jimbit_> both are running RC4
 
I have been having problems with transactions are not denominated when the transaction originated from my MN (testnet). To fix this I send the tDRK to another address on the client and it will start denominating about an hour later.
 
What actually happens to blocks solved on RC3 at the moment? Are those coins going to be lost from circulation when RC4 enforcement happens? I only ask because I'm getting so many non payments to my masternodes which are all RC4.

The payments at 1906 and 1913 today on this node didn't come through for example. http://drk.poolhash.org/masternode.html?srch&nmstr=XthmsSdS1gnqroQPCCYzsKnimtyDauQMgg

I'm totally confused...I'm getting more non payments in my expected payments list than payments. Firstly, is this simply because some pools haven't updated to RC4? Secondly, what happens to the masternode payments on RC3?
 
stonehedge said:
What actually happens to blocks solved on RC3 at the moment? Are those coins going to be lost from circulation when RC4 enforcement happens? I only ask because I'm getting so many non payments to my masternodes which are all RC4.

The payments at 1906 and 1913 today on this node didn't come through for example. http://drk.poolhash.org/masternode.html?srch&nmstr=XthmsSdS1gnqroQPCCYzsKnimtyDauQMgg

I'm totally confused...I'm getting more non payments in my expected payments list than payments. Firstly, is this simply because some pools haven't updated to RC4? Secondly, what happens to the masternode payments on RC3?
Click to expand...
The blocks on RC3 are going to pay RC3 masternodes since they are incompatible with RC4. I don't know if RC4 clients can pick up the block notifications via broadcast.
 
stonehedge said:
What actually happens to blocks solved on RC3 at the moment? Are those coins going to be lost from circulation when RC4 enforcement happens? I only ask because I'm getting so many non payments to my masternodes which are all RC4.

The payments at 1906 and 1913 today on this node didn't come through for example. http://drk.poolhash.org/masternode.html?srch&nmstr=XthmsSdS1gnqroQPCCYzsKnimtyDauQMgg

I'm totally confused...I'm getting more non payments in my expected payments list than payments. Firstly, is this simply because some pools haven't updated to RC4? Secondly, what happens to the masternode payments on RC3?
Click to expand...

afaik, the rc3 mn are getting paid.... anyone have the rc3 MN binary laying around?
 
For our three nodes we're seeing a less than 50% payment rate based on the expected payment list. In fact, on one of them we're only received about 4/11 payments in the last three days or so.

http://drk.poolhash.org/masternode.html?srch&nmstr=XthmsSdS1gnqroQPCCYzsKnimtyDauQMgg
http://drk.poolhash.org/masternode.html?srch&nmstr=XmG1tHe2NbRfbNb7ise7p4ihzsWLWLmLQj
http://drk.poolhash.org/masternode.html?srch&nmstr=Xk1uXbdeYr6oh2yaXPw76CiCGd97TwFrMU

At what point does it become viable to enforce? There were 820ish masternodes live on RC3 before RC4 was released and only about 650 live on RC4 now. Does that mean the nodes that didn't update are raking in the coins at the moment?

I've spent a lot of my spare time in the last few days contacting pools who are still on RC3 and afaik they are in a minority now. Or so I thought.
 
stonehedge said:
For our three nodes we're seeing a less than 50% payment rate based on the expected payment list. In fact, on one of them we're only received about 4/11 payments in the last three days or so.

http://drk.poolhash.org/masternode.html?srch&nmstr=XthmsSdS1gnqroQPCCYzsKnimtyDauQMgg
http://drk.poolhash.org/masternode.html?srch&nmstr=XmG1tHe2NbRfbNb7ise7p4ihzsWLWLmLQj
http://drk.poolhash.org/masternode.html?srch&nmstr=Xk1uXbdeYr6oh2yaXPw76CiCGd97TwFrMU

At what point does it become viable to enforce? There were 820ish masternodes live on RC3 before RC4 was released and only about 650 live on RC4 now. Does that mean the nodes that didn't update are raking in the coins at the moment?

I've spent a lot of my spare time in the last few days contacting pools who are still on RC3 and afaik they are in a minority now. Or so I thought.
Click to expand...
https://drk.mn/blocks.html#perversion
 
I'm having issues downloading the RC version for Windows from darkcoin.io. flare tells me that's probably github's servers having some issues and that if someone is experiencing this you can download from bamboo.darkcoin.qa
 
Hi everyone :) I have a couple of questions. My coins have finished denominating, I think, and now I get the insufficient funds message. I have a ton of mined coin entries that I don't believe have been denominated. They're still too small when combined. I suspect that's the issue. The only problem is that my wallet is still unlocked. I think that once you hit the insufficient funds point, the wallet should lock back up, no?

Another question, I just need to confirm what these entries mean:

mvLa3T.jpg


Where it says "DarkSend" rounds, that shows either "3" which means it made 3 rounds as I requested, and is completed, or "-2 or -3" as they have either completed a single or no rounds (and need to still do 2 or 3 rounds to be denominated to the point I requested). I requested 3 rounds in options.

So, basically, at this point, my wallet is a denominated as it can be. I would like for it to lock itself back up at this point but it doesn't. Is there a "safe" work around, where I can lock it back up without causing the wallet trouble? I see DarkSend is idle, so I don't think I'll be charged a fee. It's just that I'm doing a tutorial and would like to be able to tell people they can now.... blah blah blah. It'd be nice if it were a little more eloquent than closing the wallet and reopening it, but if that's all we can do, that's what I'll write :)

Thanks for any help : )
 
TanteStefana said:
Another question, I just need to confirm what these entries mean:

mvLa3T.jpg


Where it says "DarkSend" rounds, that shows either "3" which means it made 3 rounds as I requested, and is completed, or "-2 or -3" as they have either completed a single or no rounds (and need to still do 2 or 3 rounds to be denominated to the point I requested). I requested 3 rounds in options.
Click to expand...
These "-3" entries are fee denominations. As you know a DS+ transaction is requiring 0.0125DRK fee. The wallet is splitting these values off and keeping them separate, so that they can be used as needed (for the next DS+ transaction) this was introduced to increased anonymity level.
 
flare said:
These "-3" entries are fee denominations. As you know a DS+ transaction is requiring 0.0125DRK fee. The wallet is splitting these values off and keeping them separate, so that they can be used as needed (for the next DS+ transaction) this was introduced to increased anonymity level.
Click to expand...
Oh, how smart! Love it!

OK, I found a couple of things that I think are wrong in the wallet. First, at the bottom of the Send tab where we see DarkSend Status =>, DarkSend is spelled darkSend . Next, When you see my list above, it's very redundant. It used to list all the addresses with, say 10 coins under one heading of 10, not each address under it's own heading. There should only be one 100 then 50, and 10 or however DarkSend breaks it down, then when you open that "folder", you should see the list of addresses with 10, etc... coins in it. It used to be this way, but now it's spread out in an inefficient way :)

Oh, I just realized... Will the fact that those 3 pre-prepared amounts have the same address cause a connection between the denominated amounts when they are paid? Should they perhaps have their own address? Or?

 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top