Separate names with a comma.
Please sign up to discuss the most innovative cryptocurrency!
Discussion in 'Testing' started by eduffield, Sep 3, 2014.
Perhaps a brief a mouse over description?
****** PLEASE UPDATE TO v9.13.5 (Stable) OR 10.13.5 (RC) *******
- This should fix the endless splitting bug
- Overview updates when you update settings and click OK now
I think if you put the "Anonymized: xxx DRK" in a bigger box, users will be happy when they see their anon money rolling in (like a jackpot-- lol ---) then you can forego the Progress bar...
What about this?
So now we are bringing back threshold?
Unless I misunderstand, they won't see any anonymized money rolling in at all until the denominated amounts make it all the way through every round of mixing. So I could have some denominations at 7/8 rounds and still show zero anonymized and think that it's not working.
This may be outside the scope (something for the wallet redesign), but I think all the Darksend stuff needs a separate tab with a very clear overview of everything...show your initial input, how it was denominated, and then the status (how many rounds complete) of each denomination.
That said, I think the progress bar is a very good thing and should come back.
Where do you see a threshold? I just see the option to stop if for some reason people want to stop anonymization at a certain point.
In that example there is a "Amount to anonymize" setting, that's how the progress bar is calculated
For some reason the wallet does not format correctly for my screen. No idea why.
Edit: And for some reason during the initial agreement to the terms and service, the text is a huge landscape tower where I had to manually move the top off screen with the alt key just to agree.
My bad, I overlooked that.
Evan, out of curiosity, has the "kick old protocol versions off the network" been added yet, or does that come a little bit later in the testing process?
Mac OS X? --> http://jira.darkcoin.qa/browse/DRK-12
Linux Mint 17.
This is nothing which will be "added" - we are simply increasing the internal protocol version used and deny connection from "old" clients.
What Qt version do you get in your "About Qt" Dialog?
The Darkcoin Wallet is using 4.8.6 but it seems that I have both qt4 and qt5 installed on the system.
Progress bar is defo a requirement and I like the idea that DS doesn't start automatically. As to whether we go for low/med/high or 2/4/8 rounds or whatever I'm not sure.
Putting my non-techy hat on for a minute.. If i wanted to send money anonymously then why would I go for the low option or the medium option? To a non-techy it will probably confuse them a bit? I'm sure this discussion has already been had in the past but if not it's probably something worth discussing...?
Evan, if we have 1000 drk to be anonymized and we stop the anonymizing midway, we have 0 anon drk, right? This is like a batch processing. I'm thinking if somehow we can have 1 drk anonymized at a time and throw the 1 anon drk in the box, then the next drk.. and so on..
So the RC5 client will deny connections from anybody running RC2, for instance?
Exactly what I was trying to say. It's like batch processing. One denomination may finish before another, but each denomination must make it all the way through the Darksend process before you have any anonymized coins at all.
I think this is good - but - does Anon actually STOP right now? Maybe it should have a progress bar pop-up when you click STOP to show when the current Anon funds have and/or will be completed.
Exact, they are not backward compatible on protocol level - actually this was already done with RC3 and RC4
Would it be possible for someone to spoof the version number?
If users compile it themselves they could simply bump the protocol version of a previous client and compile it? Is there any way to prevent this, e.g. check for a certain block of code that is unique and required for the current protocol version and compare that to the stated version, and then error out if they don't match?
Edit: never mind, I guess they could change that logic before compiling too!
Unless if the threshold is built into the code, 1 drk gets anonymized at a time.. AND FAST... then shows up on the "Anonymized: xxx DRK" box... It can be like a jackpot ... lol... Hey, i think it can happen
That's great. The simpler the better.
Of course, it's just a number in the code - but to achieve what?
20% additional mining payments (not paying MNs).
The 20% are not depending on the client versoin but the stratum protocol. that's a different story (unfortunately).