Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 6349. (Read 9723733 times)

Physical DRKs... we should have some by then. Preferably minted on silver...

Once the final logo is picked, I'd say the crowd is offered like 10-20 variants* based on it, with refinements and colors if possible. Just because something is better than the others doesn't mean it's the best at its current state, it might be able to get further optimization.

* And for those who may create them: I liked the black/gold logo of another design but since it's not getting much voting, I'd like to see a black/gold theme for the logo that will be picked. Gold in general is a color that is used for financial stuff. Black and gold, if done correctly, is quite classy.

We should turn this into a competition. Price is right style (the closest without going over).

What is the closing price January 1st, 2015 in USD (using cryptsy and bitcoinaverage.com)?

Winner gets???

DRK will be USD$101 in 2015.

For all you who have complaints about Darkcoin's image go to the https://www.darkcointalk.org/threads/official-logo-vote.229/
forum and vote for a logo. I would argue that if marketing Darkcoin is a challenge then we need the logo that gives the best possibility for greater adoption. To breakdown prejudice against the concept of being somehow illegal and fringe. Get over there and vote.

You know what has made Darkcoin successful is not necessarily Darksend, but the fact that it is the first X11 coin.
Just as litecoin was the first scrypt coin.

Awesome, hope it works for me

You're probably on windows 7 and don't actually have the latest wallet (last 2 days?)

Here's a great Story! https://www.darkcointalk.org/threads/the-birth-of-darkcoin.162/

What would be considered fruitful?  I have ~9Mh and make about 7 coins a day, which at 60 cents is $4.20.  Just trying to get a feel for what most people consider fruitful.

Look, Evan said this coin is now set in stone.  Nothing is going to change except features of the coin.  There will be no airdrop, a very stupid suggestion that would kill darkcoin.

I suggest in big letters, there be a link to the "story of darkcoin, please read before investing"

If you don't like it, don't invest.

Not only is there NO way this can be "fixed" it arguably was a good thing for coin distribution.

Hash coin.

Doing a list of coins that are using Evans work DGW, x11, anything else

So far have:

* Hirocoin - x11
* Quebecoin - x11 and DGW
* Limecoin - x11 and DGW
* VirtualCoin - x11
* GiveCoin - x11
* Einsteinium  Emc2 - switching to x11
* ElectronicYen - x11 (poss scamcoin)
* Muniti - x11
* Edgecoin - x11

I can't help you with a guide for doing it, but I will suggest that it's not going to be fruitful. At all. Unless you have a warehouse full of video cards all to yourself and hashpower exceeding 5% of total network...

i need darkcoin GPU SOLO Mining Guide.

i am already mining on pool, i got receved some coins in my windows wallet, but i am also receving some minor values in drk cons in my wallet.

Now i want to try solo mining, i can not figuire out how to do this. Anyone can help with step by step guide ?

How to use those below ?

I realize it's not a black and white issue, I'm suggesting that it be made into a black and white issue. Still testing, too...

I'd like DarkSend a lot more if it distributed the pool of darksends in the same way the memory pool currently distributes all sends. It's a good model for many reasons, why re-invent the wheel?

As it is, if one node is compromised or malicious, what stops it from hosing up darksend? Sure, that TX will fall out of the memory pool and eventually be not a sent transaction according to my client, but how about something that actively avoids the incident? Why shouldn't all clients hosting the full chain also be darksend nodes? For that matter, why is darksend optional? Why aren't all sends done in that manner automatically? Input volume, yes...

It's easy to be the idea guy when you don't have to do all the work... ;-)

Some of my questions are a bit noobish, but I wanted them answered for the sake of the noobs reading this thread. If you can barely comprehend BitCoin, this is a lot of new fancy stuff on top of it...

At the least, there should be some way to prevent discerning such nodes as that represents a less distributed model and a point of attack. The simplest way I know of doing that is to include it or tie it to another feature, not have it independently selectable and independently identifiable. My first thought is anything that hosts the full blockchain also functions as a darksend node by default, no user option to do otherwise. This works as a paradox because we still know which nodes are doing darksend, but it's equally futile to attack one of them as it is to attack a node for any other reason. Looking forward, this makes sense because you don't want a darksend node taking the BitCoin route of clients that don't hold the full chain once it gets so hugeness. It wouldn't be able to verify veracity of the claim from which the send it originating.

It may not be a concern today, but it will be eventually. If my ass speaketh, advise me of my ignorance that I might be rid of it.

You should have received an activation e-mail. I know some people (including myself) were having issues with Hotmail/Outlook accounts not getting the e-mail, but supposedly it's been fixed.

I believe Propulsion is the admin.

That's not really going to work. Upon starting the masternode up, it's going to need to sign the input with the 1000DRK to show you own it. After that all messages will use a separate key, so the wallet can be encrypted until the next restart.


In the initial message that you sign with the vin, you will sign your IP and darkcoin address to pay.  It's using ECDSA signatures like the "signmessage" and "verifymessage" commands.

Also the "tickets" into the election require 1 unspent output equal of 1000DRK. We know it's unique because of the vin. Pretty amazing what you can use bitcoin for, eh?


The 1000DRK needs to go into a single input and that vin gets passed around. When you start the masternode it locks that input, so it actually can't be spent. You'd have to shutdown the client and disable the masternode to move it. If you spent it somehow, the other clients look at the memory pool for changes and disable masternodes automatically (that's the error you got from me testing).

I know I already asked this before but I didn't have a chance to investigate further. I am trying to get my old wallet (xcoin) to sync so I can transfer my balance to new DarkCoin wallet

I'm not opposed to a setup like that. Maybe that can be V2. I'd argue our system is still decentralized though, there will be many masternodes each doing mixing for a small time.