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

[tombtc]

And just a little message for LTC BAGholders!!

[tifozi]

Development Update - 6/6/2014 - Masternode Payments

https://darkcointalk.org/threads/development-update-6-6-2014-masternode-payments.1126/

thx!

And don't forget to thank the unsung crowd of President Chaeplin, fernando, eltito, propulsion, so many voluntary testers and others who are constantly working behind the scenes, not to mention the perma troll fighters (you know who they are).

I am one of those who hasn't forgotten AnonyMint either and how he initially shaped the Darksend MN discussions and how Evan took everything to another level. It is good to remember it from time to time.

[greyskies]

Development Update - 6/6/2014 - Masternode Payments

https://darkcointalk.org/threads/development-update-6-6-2014-masternode-payments.1126/

thx!

And don't forget to thank the unsung crowd of President Chaeplin, fernando, eltito, propulsion, so many voluntary testers and others who are constantly working behind the scenes, not to mention the perma troll fighters (you know who they are).

Not surprised these XC trolls are in fact massive DRK supporters 

Stay classy.

[Propulsion]

Development Update - 6/6/2014 - Masternode Payments

https://darkcointalk.org/threads/development-update-6-6-2014-masternode-payments.1126/

thx!

And don't forget to thank the unsung crowd of President Chaeplin, fernando, eltito, propulsion, so many voluntary testers and others who are constantly working behind the scenes, not to mention the perma troll fighters (you know who they are).

Not surprised these XC trolls are in fact massive DRK supporters 

Stay classy.

Thank you.

[tifozi]

Development Update - 6/6/2014 - Masternode Payments

https://darkcointalk.org/threads/development-update-6-6-2014-masternode-payments.1126/

thx!

And don't forget to thank the unsung crowd of President Chaeplin, fernando, eltito, propulsion, so many voluntary testers and others who are constantly working behind the scenes, not to mention the perma troll fighters (you know who they are).

Not surprised these XC trolls are in fact massive DRK supporters 

Stay classy.

Did you know that Chaeplin is the man who developed the X11 p2pool https://github.com/chaeplin/p2pool-drk

You do realize that XC used X11 (albeit to defame it, very unsuccessful in doing so) ?

Stay classy ? You are new to crypto. I used to be like this. In 5-6 months you will be a LOT smarter and thank the XC experience. Most of us learned the hard way. Any further discussion, you can contact me on IRC or PM.

[choose-username]

Sad news chaps...

I have put a few hundred coins on sale because I will soon need to pay for some bills in July.

They are on the market for 0.1 BTC  

Few hundred for 0.1 BTC ? Typo ?

Per each DRK?

[Freckleg]

And we have a cup and a handle now only needed to pick it up

[coins101]

Sad news chaps...

I have put a few hundred coins on sale because I will soon need to pay for some bills in July.

They are on the market for 0.1 BTC  

NNNNNNNNNNnoooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo oooooooooooooo, you can tell all you want but not this.

I might sell a few when the price hits $300/DRK.

ok...I'm gonna sell some stocks instead 

[coins101]

Sad news chaps...

I have put a few hundred coins on sale because I will soon need to pay for some bills in July.

They are on the market for 0.1 BTC  

Few hundred for 0.1 BTC ? Typo ?

Per each DRK?

was 200 x 0.1 BTC around mid July.

Now, off the market.

[TanteStefana2]

We want to make it clear that automatic checkpointing is a temporary solution that will be removed from the code as soon as we feel it is safe to do so. Though it is clearly beneficial for use as a failsafe mechanism while we perfect the code that powers Darksend, in the long term, the presence of a centralized checkpointing server on the network is unacceptable.

Sorry for my ignorance if this is covered elsewhere, but why is a centralised server necessary? Why couldn't for example new versions of the mining code contain a key which must be included in each solved block after a certain date for that block to be considered valid by those that have updated correctly? Thanks.

Because not everyone updates their client in a timely manner.  If the miners do not update, then the blockchain will fork.  It will fork until most of the clients are updated and it has a strong enough blockchain in the system to resist any forking.  This should only be required until all the dust settles.  I think Evan will keep it in place a little longer so that if there are any other issues while perfecting DarkSend, it will be there to keep things going.  Once Darksend is opened sourced it will be removed if not before then.

I'm guessing that it forks when multiminers come in to mine.  Those are pools that don't follow what is going on and are not part of our community, so the drop in, with old clients and a lot of hash power, and screw everything up.  Not on purpose, but that is the result.  I believe Evan said in another post, that the client will eventually ignore bad players like that, but don't think that's working yet

[TanteStefana2]

Sad news chaps...

I have put a few hundred coins on sale because I will soon need to pay for some bills in July.

They are on the market for 0.1 BTC  

NNNNNNNNNNnoooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo oooooooooooooo, you can tell all you want but not this.

I might sell a few when the price hits $300/DRK.

ok...I'm gonna sell some stocks instead 

Seriously?  Are you going to sell your APPLE instead or GOOGLE?  LOL.  You're too sweet!

[blajde]

We want to make it clear that automatic checkpointing is a temporary solution that will be removed from the code as soon as we feel it is safe to do so. Though it is clearly beneficial for use as a failsafe mechanism while we perfect the code that powers Darksend, in the long term, the presence of a centralized checkpointing server on the network is unacceptable.

Sorry for my ignorance if this is covered elsewhere, but why is a centralised server necessary? Why couldn't for example new versions of the mining code contain a key which must be included in each solved block after a certain date for that block to be considered valid by those that have updated correctly? Thanks.

Because not everyone updates their client in a timely manner.  If the miners do not update, then the blockchain will fork.  It will fork until most of the clients are updated and it has a strong enough blockchain in the system to resist any forking.  This should only be required until all the dust settles.  I think Evan will keep it in place a little longer so that if there are any other issues while perfecting DarkSend, it will be there to keep things going.  Once Darksend is opened sourced it will be removed if not before then.

I'm guessing that it forks when multiminers come in to mine.  Those are pools that don't follow what is going on and are not part of our community, so the drop in, with old clients and a lot of hash power, and screw everything up.  Not on purpose, but that is the result.  I believe Evan said in another post, that the client will eventually ignore bad players like that, but don't think that's working yet

But that doesn't matter once the identifier is implemented since it will pick correct fork and return orphans and redirect to identified?

[TanteStefana2]

But that doesn't matter once the identifier is implemented since it will pick correct fork and return orphans and redirect to identified?

I believe so, not being very technical myself and just trying to understand what's been said elsewhere 

[coins101]

This looks sustainable over the next 10 days

[tuneman1980]

Is DarkCoin on the rise?  Keep an eye on it here.  http://cryptocoinstats.com/pricetracker.php

[eltito]

But that doesn't matter once the identifier is implemented since it will pick correct fork and return orphans and redirect to identified?

Properly updated clients will contact the checkpoint server and request the current correct status of the network.  The client will compare the answer it receives with the information it currently sees, and correct itself if necessary.  A client may be on the wrong fork for a block or two in such a scenario.

Presumably the majority of people will update their clients properly.  All of the "lynch pin" clients will undoubtedly do so (exchanges, pools, etc.).  The rest of us will follow suit because we are keen to have DRK which are actually usable.  

Since there is only one checkpoint server orchestrating the whole show, everyone on the correct client gets the same information and we can all carry on business as usual.

Those who didn't update their clients and end up on the wrong fork will (I assume) simply continue mining worthless DRK until they pull their heads out, get it together and update.  As long as they don't make up more than 50% of the network, they're irrelevant.

[rickraw]

Time to buy?

[eltito]

Time to buy?

IT'S ALWAYS TIME TO BUY

[komodovpn]

Is DarkCoin on the rise?  Keep an eye on it here.  http://cryptocoinstats.com/pricetracker.php

your graphs suck

this one way better https://bitcoinwisdom.com/markets/mintpal/drkbtc

[jeffminer]

Development Update - 6/6/2014 - Masternode Payments

https://darkcointalk.org/threads/development-update-6-6-2014-masternode-payments.1126/

bumping this as it is hard to find info on this thread 

Darkcoin rocks!