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

[kangertech]

Sorry guys for the stupid question but what is the advantage of knowing the source code 

[1714818582]

1714818582

[roede94105]

Sorry guys for the stupid question but what is the advantage of knowing the source code 

So millions of shitcoin clones can be created

Seriously though, it provides huge confidence since everyone can review the code.

[stonehedge]

Sorry guys for the stupid question but what is the advantage of knowing the source code  

So millions of shitcoin clones can be created

Seriously though, it provides huge confidence since everyone can review the code.

I think it is important to point out that the majority of the Darkcoin code has been open source for some time.  Today is significant because Darksend is being open sourced (the primary mechanism for handling anonymity).  I stand to be corrected but everything else, including masternode code has been open source for months.  Today is about gaining the trust of those who could benefit from Darkcoin payment systems by revealing to them how it works.

The other significance about today is that today is the day that the dev team are confident to say that Darkcoin and Darksend have been tested and thoroughly bug squashed and are no longer release candidates.  After today's announcement, Darkcoin can be considered freely available consumer technology for adoption by those who choose to adopt it

[stonehedge]

Oh and roede94105 is correct.

Expect hundreds of shitcoin clones to pop up within hours/days.  My personal opinion is that this will prove to be a positive factor for the Darkcoin project but time will tell.

[droptable]

Sorry guys for the stupid question but what is the advantage of knowing the source code 

if you have the executables (eg. the programm as "*.exe") you can see what a program does.
or more exact: you can be told what a program does, and test (by input) if it (probably) does that.

if you have the source you can see what a program does, and what it doesn't.
you can see the way it works, and what happens at every step.
you can find out if there are hidden functions, backdoors, bugdors, etc...

[GhostPlayer]

Sorry guys for the stupid question but what is the advantage of knowing the source code 

Above all said, the other big one is that others can freely contribute to the code, or create entirely new sub-systems and features.

That alone has enormous potential.

[AlexGR]

Sorry guys for the stupid question but what is the advantage of knowing the source code  

So millions of shitcoin clones can be created

Seriously though, it provides huge confidence since everyone can review the code.

I think it is important to point out that the majority of the Darkcoin code has been open source for some time.  Today is significant because Darksend is being open sourced (the primary mechanism for handling anonymity).  I stand to be corrected but everything else, including masternode code has been open source for months.  Today is about gaining the trust of those who could benefit from Darkcoin payment systems by revealing to them how it works.

The other significance about today is that today is the day that the dev team are confident to say that Darkcoin and Darksend have been tested and thoroughly bug squashed and are no longer release candidates.  After today's announcement, Darkcoin can be considered freely available consumer technology for adoption by those who choose to adopt it

I believe there are few pending issues, like the MN payment protocol which can be improved upon and we'll also have to see how the DarkSend operation withstands tampering attacks of the software, which will now be open-source. This could uncover a few bugs down the line.

[Drobek]

Hi there, in the wake of open sourcing comes a void filler - another of my basic MN security questions:

Is there any real danger in someone getting their hands on the remote config file with these values?

rpcuser=reallylongusername
rpcpassword=veryveryverylongpw
masternodeprivkey=7..._Masternode_Private_Key

the 1,000 DRKs should be still safe in the local wallet, right? Just want to be sure 

[stonehedge]

Hi there, in the wake of open sourcing comes a void filler - another of my basic MN security questions:

Is there any real danger in someone getting their hands on the remote config file with these values?

rpcuser=reallylongusername
rpcpassword=veryveryverylongpw
masternodeprivkey=7..._Masternode_Private_Key

the 1,000 DRKs should be still safe in the local wallet, right? Just want to be sure  

You cannot withdraw funds from your cold "wallet" without your wallet pass phrase.  Your funds are safe.

I personally prefer to treat all configuration files as if they are passwords.  The less known the better imho.  Its good practice.

[illodin]

Hi there, in the wake of open sourcing comes a void filler - another of my basic MN security questions:

Is there any real danger in someone getting their hands on the remote config file with these values?

rpcuser=reallylongusername
rpcpassword=veryveryverylongpw
masternodeprivkey=7..._Masternode_Private_Key

the 1,000 DRKs should be still safe in the local wallet, right? Just want to be sure 

I don't think you need the rpcuser and rpcpassword stuff in the remote MN at all. You should have the rpc port blocked by the firewall anyway.

[stonehedge]

Hi there, in the wake of open sourcing comes a void filler - another of my basic MN security questions:

Is there any real danger in someone getting their hands on the remote config file with these values?

rpcuser=reallylongusername
rpcpassword=veryveryverylongpw
masternodeprivkey=7..._Masternode_Private_Key

the 1,000 DRKs should be still safe in the local wallet, right? Just want to be sure 

I don't think you need the rpcuser and rpcpassword stuff in the remote MN at all. You should have the rpc port blocked by the firewall anyway.

You can't run darkcoind at all without RPC details.  The firewall has no effect because the server is localhost.

[Drobek]

Hi there, in the wake of open sourcing comes a void filler - another of my basic MN security questions:

Is there any real danger in someone getting their hands on the remote config file with these values?

rpcuser=reallylongusername
rpcpassword=veryveryverylongpw
masternodeprivkey=7..._Masternode_Private_Key

the 1,000 DRKs should be still safe in the local wallet, right? Just want to be sure  

You cannot withdraw funds from your cold "wallet" without your wallet pass phrase.  Your funds are safe.

I personally prefer to treat all configuration files as if they are passwords.  The less known the better imho.  Its good practice.

Great, thanks guys!

[rickraw]

I know in the grand scheme of things it doesn't matter, but I am going to be fairly irritated if some coin takes Darksend, rebrands it and uses it for a big pump.  Would be cool if the crypto community ostracized any coins who blatantly take and apply Darksend to their coins for the purpose of pumping.

[thelonecrouton]

I know in the grand scheme of things it doesn't matter, but I am going to be fairly irritated if some coin takes Darksend, rebrands it and uses it for a big pump.  Would be cool if the crypto community ostracized any coins who blatantly take and apply Darksend to their coins for the purpose of pumping.

Darksend requires masternodes. The masternode source has been open for months. Nobody has cloned a thousand masternodes yet. Hell the darksend diagram effectively open-sourced darksend+ months ago too - it's no secret how it works.

There will be a few new shitclones that will have a short pump, an inevitable dump, and the idiots will get taken for a ride as they always do, but there will be no serious competition after today anymore than there was before today.

What there will hopefully be after today is proof to anyone who cares (anyone to whom privacy is actually important) that darksend is trustworthy and can be safely adopted.

[splawik21]

I know in the grand scheme of things it doesn't matter, but I am going to be fairly irritated if some coin takes Darksend, rebrands it and uses it for a big pump.  Would be cool if the crypto community ostracized any coins who blatantly take and apply Darksend to their coins for the purpose of pumping.

i would cut the dick for every clone with darksend but you cant stop it:(

[stonehedge]

I know in the grand scheme of things it doesn't matter, but I am going to be fairly irritated if some coin takes Darksend, rebrands it and uses it for a big pump.  Would be cool if the crypto community ostracized any coins who blatantly take and apply Darksend to their coins for the purpose of pumping.

i would cut the dick for every clone with darksend but you cant stop it:(

I live in hope that newcomers to altcoins don't get burned and that those with some experience will be a little wiser where they put their faith.  There will be clones but I reckon there won't be as many as we fear.

Anyway...opensource!  Just think about what can be achieved with the world as your dev team?

[sdef2]

Would be nice if there was a way of making 'plugins' which add extra functionality to the masternode network.
It would require some kind of 'plugin' framework i guess.

Might speed up the way we can introduce new functionality (?).

[illodin]

I don't think you need the rpcuser and rpcpassword stuff in the remote MN at all. You should have the rpc port blocked by the firewall anyway.

You can't run darkcoind at all without RPC details.  The firewall has no effect because the server is localhost.

Thanks for the correction. I've basically never used the daemon, I just run the wallet.

[rickraw]

I know in the grand scheme of things it doesn't matter, but I am going to be fairly irritated if some coin takes Darksend, rebrands it and uses it for a big pump.  Would be cool if the crypto community ostracized any coins who blatantly take and apply Darksend to their coins for the purpose of pumping.

i would cut the dick for every clone with darksend but you cant stop it:(

I live in hope that newcomers to altcoins don't get burned and that those with some experience will be a little wiser where they put their faith.  There will be clones but I reckon there won't be as many as we fear.

Anyway...opensource!  Just think about what can be achieved with the world as your dev team?

Yeah, come on all reputable devs, invest some BTC and help make Darkcoin even better!

[stonehedge]

I don't think you need the rpcuser and rpcpassword stuff in the remote MN at all. You should have the rpc port blocked by the firewall anyway.

You can't run darkcoind at all without RPC details.  The firewall has no effect because the server is localhost.

Thanks for the correction. I've basically never used the daemon, I just run the wallet.

No probs.  I only know that because if you run the daemon without specifying rpcuser and rpcpassword it won't start and actually gives you an error message with a randomly generated password for you to use!