I wonder how many people who hold DRK realize that DarkSend is closed source and could be doing one or all of the following?:
1. Creating more DRK for the devs so they can slowly cash out on exchanges to maximize profits.
2. Double spend DRK on exchanges or merchant (if any) who accept DRK.
3. Conceal the total amount of DRK that really exists given you can't actually trace where DRK came from on an open and public ledger like BTC and LTC has.
4. DarkSend could have malware that is running on your computer or scanning activity or key logging or even wallet stealing.
I'll never download anything crypto related to my computer that isn't open-source. That is just idiotic.
Old schedule...
- RC2 (magic numbers changed to darkcoin, DGW3) : May 14th
- RC2 (masternode payments) : May 25th
- RC3 (10 DRK limit and denominated change) : June 14th
- After this, I'll find someone to vet the code and open source.
- RC4 (Bugs, security issues)
- Testing, then opensourceThe masternode issues and the 3rd fork for the 25th actually messed up the schedule. I've been rewriting much of the code masternode technology (released yesterday, if you haven't updated please do!)
There's still some oddities with the election voting system that I'm going to tackle this next week. This I'll start working again on RC3 .
Improvements over this mixing solution are due to include the following features:
* Master Nodes These nodes handle the mixing through random selection -
They are responsible for being the authority of what goes into the joined transaction each session.
eduffield, 21 February 2014
https://bt.irlbtc.com/view/421615.msg5282966#msg5282966* I2P:
I'm implementing I2P into the masternodes. We're going to have our own private network just for DarkSend.
eduffield, 10 May 2014.
https://bt.irlbtc.com/view/421615.msg6643662#msg6643662* Ring signatures are going to be implemented in V2.
I will begin development immediately after I opensource V1.
eduffield, 12 May 2014.
https://bt.irlbtc.com/view/421615.msg6686819#msg6686819While ring signatures present their own compatibility problems with the core DarkSend and Master Node network, the lead developer has consider the issues and is seeking to implement adaptations:
Ring Signatures, RC3 Progress Report 22 May 2014
I've had some substantial progress on DarkSend and have figured out how to make our existing system as secure as ring signatures. Vastly improved security, no bloat (from the ring signatures) and without actually having to trust new cryptography (it hasn't been extensively tested like what DarkSend uses) . So I think it'll give us a HUGE advantage in the coming months. More to come soon, I'm going to start implementing this tomorrow.
https://bt.irlbtc.com/view/421615.msg6864666#msg6864666*IP obfuscation 12 May 2014
https://bt.irlbtc.com/view/421615.msg6694377#msg6694377