Post
Topic
Board Announcements (Altcoins)
Re: [ANN][DASH] Dash | First Anonymous Coin | Inventor of X11, DGW, Darksend and InstantX
by
cryptonewb
on 12/10/2015, 18:48:40 UTC
This is not true. Darksend was closed source until RC5 in August/September 2014, when the source code was released. The rest of the Darkcoin source was open, but the Darksend portion was closed until Aug/Sept 2014. I helped write the official press release about Darksend being open-sourced, so I remember it well =)

and I think that worked out well, don't you?  I mean, we did have a bunch of complainers/trolls again, saying you can't close source it, but it is after all a company, Dash is, and we should use tactics that protect our intellectual property until it's needed to be open sourced, which is required to be taken seriously in the crypto world for good reason.  Still, while working on it, we don't need to let everyone see what we're doing.  We can hide until the big reveal just like Apple does.

There are no plans to close source anything. We're just going to build it privately, then open source it as soon as we launch  Smiley.

that's good news! Smiley
But why not build it publicly, so other developers/volunteers can help?

Also, now that you are online, can you please answer my newb questions:
1) How are the masternode locks enforced in the network? How do you force miners to not mine a double spent transaction?
2) Is it possible that there is a competing locked transaction? If that transaction has a higher fee (double spend attempt), I guess the miners rather confirm the transaction with the higher fee...
3) Masternodes don't get fees to lock transactions? What is the incentive to do the work? How are the masternode rewards distributed? How can the network "know" that masternodes are online and doing the work in stead of just being idle to have a lower bandwidth usage?
4) I wonder how you can have so much transactions per second? (the slide shows 500-1500) I read that bitcoin is limited to 7 transactions per second. I showed that it seems impossible to lock 350 transactions simultaneously with 3500 masternodes, unless you allow overlap. But that should be avoided, because it can happen that a masternode has the power to decide which of the 2 transactions he confirms during a double spend attack.