[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[thelonecrouton]

http://www.reddit.com/r/Bitcoin/comments/2gv44m/darkcoin_i_just_solved_one_of_the_largest/

If you have a reddit account, our glorious leader might appreciate a few upvotes.

[dihydrogenmonoxide]

http://blog.anonymousbitcoinbook.com/2014/09/darkcoin-code-review-results/

Summary: I identified no significant security vulnerabilities in the closed source Darkcoin code. There are three privacy implementation issues that have been acknowledged by the Darkcoin development team and are being fixed; full disclosure of those issues will take place no later than 2014/10/18.

[coins101]

Fantastic, +101

[k0vic]

Well that sucks..

"I have identified a few privacy-related issues in the code. For the time being, I recommend that users pause use of Darksend+ for privacy purposes, or bolster them with other blockchain privacy tactics as part of a privacy-in-depth strategy, until the issues can be fixed; these issues were reported to the Darkcoin dev team on 2014/09/18, and acknowledged by email by the dev team on the same day. All will be fully disclosed by 2014/10/18 as part of “responsible disclosure” practices. I expect that they will be addressed sooner than 2014/10/18; if corrected Release Candidate binaries are made available before then, I will disclose the issues at that point. For the time being, I’m reserving the following IDs for the issues so that their status can be tracked:"

http://blog.anonymousbitcoinbook.com/2014/09/darkcoin-code-review-results/

[eduffield]

Well that sucks..

"I have identified a few privacy-related issues in the code. For the time being, I recommend that users pause use of Darksend+ for privacy purposes, or bolster them with other blockchain privacy tactics as part of a privacy-in-depth strategy, until the issues can be fixed; these issues were reported to the Darkcoin dev team on 2014/09/18, and acknowledged by email by the dev team on the same day. All will be fully disclosed by 2014/10/18 as part of “responsible disclosure” practices. I expect that they will be addressed sooner than 2014/10/18; if corrected Release Candidate binaries are made available before then, I will disclose the issues at that point. For the time being, I’m reserving the following IDs for the issues so that their status can be tracked:"

http://blog.anonymousbitcoinbook.com/2014/09/darkcoin-code-review-results/

I'll have everything he found fixed by Monday.

[k0vic]

Well that sucks..

"I have identified a few privacy-related issues in the code. For the time being, I recommend that users pause use of Darksend+ for privacy purposes, or bolster them with other blockchain privacy tactics as part of a privacy-in-depth strategy, until the issues can be fixed; these issues were reported to the Darkcoin dev team on 2014/09/18, and acknowledged by email by the dev team on the same day. All will be fully disclosed by 2014/10/18 as part of “responsible disclosure” practices. I expect that they will be addressed sooner than 2014/10/18; if corrected Release Candidate binaries are made available before then, I will disclose the issues at that point. For the time being, I’m reserving the following IDs for the issues so that their status can be tracked:"

http://blog.anonymousbitcoinbook.com/2014/09/darkcoin-code-review-results/

I'll have everything he found fixed by Monday.

You are the man.

[stonehedge]

I would point a few CPUs to mine for wages. That is a really good idea. A paid team that would give a stake etc. Really good idea.

or better yet. Is it possible to mine Darkcoin with a raspberry pi?

I know that you will probably only make a few duffs with it, but it would basically cost nothing to set up and run for eternity.

Darkberry pi?

The point is to utilise as many spare CPU cycles as we can find. No reason we can't use Pi! And if people want to direct their rigs to the pool for a few hours a month all the better. Or donate DRK indeed.

I'll drop him a line. We'll have to decide whether we work together or I start a separate pool. Testing was successful on Tuesday.

I'll go away and have a chat with Propulsion, Evan and a few others and if it fits into the bigger picture I'll announce something soon.

[illodin]

"I have identified a few privacy-related issues in the code."

I'll have everything he found fixed by Monday.

Looks like the review was a very good idea. Thank you Kristov!

[TaoOfSaatoshi]

Fantastic, +101

I stole your pic for my latest tweet, I hope you don't mind...

#getintothedark

@TaoOfSatoshi

[Walter_S]

Well that sucks..

"I have identified a few privacy-related issues in the code. For the time being, I recommend that users pause use of Darksend+ for privacy purposes, or bolster them with other blockchain privacy tactics as part of a privacy-in-depth strategy, until the issues can be fixed; these issues were reported to the Darkcoin dev team on 2014/09/18, and acknowledged by email by the dev team on the same day. All will be fully disclosed by 2014/10/18 as part of “responsible disclosure” practices. I expect that they will be addressed sooner than 2014/10/18; if corrected Release Candidate binaries are made available before then, I will disclose the issues at that point. For the time being, I’m reserving the following IDs for the issues so that their status can be tracked:"

http://blog.anonymousbitcoinbook.com/2014/09/darkcoin-code-review-results/

I'll have everything he found fixed by Monday.

So they are pretty minor tweaks to the code then?

[thelonecrouton]

"I have identified a few privacy-related issues in the code."

I'll have everything he found fixed by Monday.

Looks like the review was a very good idea. Thank you Kristov!

Agreed. I think it was a very positive review overall, and Evan seems confident that whatever Kristov is alluding to is quickly fixable. 

[coins101]

http://blog.anonymousbitcoinbook.com/2014/09/darkcoin-code-review-results/

Summary: I identified no significant security vulnerabilities in the closed source Darkcoin code. There are three privacy implementation issues that have been acknowledged by the Darkcoin development team and are being fixed; full disclosure of those issues will take place no later than 2014/10/18.

I didn't know he has been reviewing professionally for 4+ years.

That's even better news. No one who does this for a living would risk their reputation and future earning potential on being anything other than impartial and critical.

Great review indeed.

[georgem]

Darkberry pi?

The point is to utilise as many spare CPU cycles as we can find. No reason we can't use Pi!

But is it even possible to mine DRK with Raspberry Pi?
I don't think that the available CPU miners run on a raspberry.

Can someone confirm this?

[naxin]

I would point a few CPUs to mine for wages. That is a really good idea. A paid team that would give a stake etc. Really good idea.

or better yet. Is it possible to mine Darkcoin with a raspberry pi?

I know that you will probably only make a few duffs with it, but it would basically cost nothing to set up and run for eternity.

Darkberry pi?

The point is to utilise as many spare CPU cycles as we can find. No reason we can't use Pi! And if people want to direct their rigs to the pool for a few hours a month all the better. Or donate DRK indeed.

I'll drop him a line. We'll have to decide whether we work together or I start a separate pool. Testing was successful on Tuesday.

I'll go away and have a chat with Propulsion, Evan and a few others and if it fits into the bigger picture I'll announce something soon.

I mean go ahead and use your rasp pi, but you're not even going to generate a single penny if you ran it for an entire year. So it really is not worth your hassle to keep it running.

[Freckleg]

"I have identified a few privacy-related issues in the code."

I'll have everything he found fixed by Monday.

Looks like the review was a very good idea. Thank you Kristov!

Indeed Dark is growing up big thanks to Kristov, and Evan for asking the impartial review

[georgem]

I mean go ahead and use your rasp pi, but you're not even going to generate a single penny if you ran it for an entire year. So it really is not worth your hassle to keep it running.

I understand, but even an average multicore CPU doesn't create much more DRK per year. Difficulty is really high already.

A raspberry pi could be hooked to your network 24/7 and additionaly provide a node to the network, helping spread the blockchain.

[stonehedge]

I have sent Propulsion a message explaining my idea to mobilise the masses with a CPU miner that runs when idle.

I'm keen to either collaborate with Propulsion or if we can't find middle ground, I can put together a business case to do this separately.

I am thinking of setting the mining fee to be anything between 5-10% to make this useful to the dev team.  If I use Nomp then (probably small) payments will be made directly to contributors wallets and to the ringfenced development fund.

If we collaborate with the official DCT pool then I think increased fees will drive serious miners away.  There may be a way that we can use Propulsions platform but have two pools.  One for serious miners and one for dust sweepers donating a larger sum of their payouts directly to the development fund.

There are two major possible issues:

1)  Evan may already have this sorted as part of the Darkcoin Foundation
2)  Even with a load of people donating their idle cpu time it might just not be worth it.  Some maths to be done I think!

I think the principle is sound and the cause worthy.  Now I just have to work out if it is practical and if I can collaborate with Propulsion or go with a separate NOMP.

[georgem]

2)  Even with a load of people cpu mining it might just not be worth it.  Some maths to be done I think!

That is true... what I would wish for is to have a raspberry pi that has somekind of X11 USB ASIC miner attached to it. Then we could make this work.

Hopefully by 2015 the first X11 USB ASIC miners will appear on the market.

[coins101]

Well that sucks..

"I have identified a few privacy-related issues in the code. For the time being, I recommend that users pause use of Darksend+ for privacy purposes, or bolster them with other blockchain privacy tactics as part of a privacy-in-depth strategy, until the issues can be fixed; these issues were reported to the Darkcoin dev team on 2014/09/18, and acknowledged by email by the dev team on the same day. All will be fully disclosed by 2014/10/18 as part of “responsible disclosure” practices. I expect that they will be addressed sooner than 2014/10/18; if corrected Release Candidate binaries are made available before then, I will disclose the issues at that point. For the time being, I’m reserving the following IDs for the issues so that their status can be tracked:"

http://blog.anonymousbitcoinbook.com/2014/09/darkcoin-code-review-results/

I'll have everything he found fixed by Monday.

Tuesday's cool  

[georgem]

Well that sucks..

"I have identified a few privacy-related issues in the code. For the time being, I recommend that users pause use of Darksend+ for privacy purposes, or bolster them with other blockchain privacy tactics as part of a privacy-in-depth strategy, until the issues can be fixed; these issues were reported to the Darkcoin dev team on 2014/09/18, and acknowledged by email by the dev team on the same day. All will be fully disclosed by 2014/10/18 as part of “responsible disclosure” practices. I expect that they will be addressed sooner than 2014/10/18; if corrected Release Candidate binaries are made available before then, I will disclose the issues at that point. For the time being, I’m reserving the following IDs for the issues so that their status can be tracked:"

http://blog.anonymousbitcoinbook.com/2014/09/darkcoin-code-review-results/

I'll have everything he found fixed by Monday.

Tuesday's cool  

Sacrificing another weekend for darkcoin. What a fella!