for some reason it doesn't work, I enter my hashrate and when I click calculate it resets back to 2850.
same here...frustrating... cant even restart to 0
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 6346. (Read 9723733 times)
April 09, 2014, 06:47:52 AM
for some reason it doesn't work, I enter my hashrate and when I click calculate it resets back to 2850.
same here...frustrating... cant even restart to 0
April 09, 2014, 06:47:04 AM
DRK will be USD$101 in 2015.
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???
On January 1, 2015, DRK will be at $21.45 USD at the start of the day 0001 UTC (it will fluctuate a lot that day)
April 09, 2014, 06:46:31 AM
。。。where is this monkey
April 09, 2014, 06:44:16 AM
I have nVidia card. Where I can to download the miner for dark?
You can use sgminer depending on your card. sgminer works fine with my GTX690s - it's not super fast, but it works.
I've been trying to convince the cudaminer dev to support X11 - it does help now that scrypt ASICs are out and many of the more popular coins are looking to X11.
But as of right now, sgminer or nothing..
One hint - start your intensity very low and work your way up until you start getting >2% HW errors. Then STOP, and back the intensity down a little. It is more stable, at least for me.
April 09, 2014, 06:41:52 AM
April 09, 2014, 06:31:07 AM
I made a post about darkcoin innovations to keep a track of who is using them.
https://bitcointalksearch.org/topic/m.6139074
can you keep me updated when you see another coin adopting Evans work.
thanks.
https://bitcointalksearch.org/topic/m.6139074
can you keep me updated when you see another coin adopting Evans work.
thanks.
April 09, 2014, 06:18:51 AM
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
all you *should* have to do is drop your old wallet.dat file into the new Darkcoin wallet's .darkcoin folder (normally hidden in /home file in Ubuntu) or it's the darkcoin folder in /User/yourusername/AppData/Roaming/darkcoin in windows Vista, 7 and 8
*remove the old (newer) wallet.dat file first, don't merge. Just in case.*
If that doesn't work, something might be wrong with your old xcoin wallet.dat (which should be completely interchangeable with a darkcoind wallet.dat)
Interchangeable?
April 09, 2014, 06:10:06 AM
We have six masternodes running 
./darkcoind masternode list
{
"121.156.120.112:9999" : 1,
"23.23.186.131:9999" : 1,
"112.175.123.94:9999" : 1,
"162.243.234.7:9999" : 1,
"87.242.50.175:9999" : 1,
"142.161.23.40:9999" : 1
}
./darkcoind masternode list
{
"121.156.120.112:9999" : 1,
"23.23.186.131:9999" : 1,
"112.175.123.94:9999" : 1,
"162.243.234.7:9999" : 1,
"87.242.50.175:9999" : 1,
"142.161.23.40:9999" : 1
}
April 09, 2014, 05:57:09 AM
Really what you need is some form of validation of set-up. But that would create work for everyone, a bottleneck, accusations of opening up risks to the validators.
Maybe a 10 DRK test node to see if you have set-up correctly, then off you go with the 1,000 DRK for real.
Maybe a 10 DRK test node to see if you have set-up correctly, then off you go with the 1,000 DRK for real.
Would be cool to have a web tool or a locally run script that automatically checks your masternode's environment for various known security exploits.
April 09, 2014, 05:52:32 AM
P2pool node not updated or maintained.
P2pool owner, upgrade your wallet to last.
Please don't use following node.
Choose another node from here http://drk.poolhash.org/
P2pool owner, upgrade your wallet to last.
Please don't use following node.
Quote
# diff block_value fee atmptsblock version checkuri host
0.231911701217 25.0 1.0 996068371 765195f-dirty http://42.121.58.91:7903 _
0.231911701217 25.0 1.0 996068371 e0b17b3-dirty http://115.68.110.84:7903 _
371.739159336 20.587 0.1 1596702653236 e0b17b3-dirty http://176.12.62.100:7903 _
0.231911701217 25.0 1.0 996068371 765195f-dirty http://42.121.58.91:7903 _
0.231911701217 25.0 1.0 996068371 e0b17b3-dirty http://115.68.110.84:7903 _
371.739159336 20.587 0.1 1596702653236 e0b17b3-dirty http://176.12.62.100:7903 _
Choose another node from here http://drk.poolhash.org/
April 09, 2014, 05:47:17 AM
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...
The idea of masternodes is to create a very expensive network similar to mining, where users invest money to make money. If you decide to be malicious, the only power you have is to not allow transactions for that 2.5 minutes, in which case you forfeit the money the network will pay you.
If all nodes were able to do it, the network would be vulnerable to sybil attacks. See my conversation with Anonymint.
Really the concept sounds great -- I guess what I am really worried about is DOS attacks on the Master nodes. Some people will do due diligence, but I am betting that most won't (don't know how) and the result will be that DRK suffers a black eye because one person brings down Darksend for a time.
What protections are there against this other than urging master nodes owners to read up on net security?
Really what you need is some form of validation of set-up. But that would create work for everyone, a bottleneck, accusations of opening up risks to the validators.
Maybe a 10 DRK test node to see if you have set-up correctly, then off you go with the 1,000 DRK for real.
April 09, 2014, 05:43:13 AM
for some reason it doesn't work, I enter my hashrate and when I click calculate it resets back to 2850.
https://www.darkcointalk.org/threads/how-to-get-mining-info-from-our-irc-bot.211/
April 09, 2014, 05:40:32 AM
here a nice script for snort ids setup https://github.com/da667/Autosnort , maybe interesting for masternodes.
April 09, 2014, 05:38:28 AM
for some reason it doesn't work, I enter my hashrate and when I click calculate it resets back to 2850.
April 09, 2014, 05:17:52 AM
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...
The idea of masternodes is to create a very expensive network similar to mining, where users invest money to make money. If you decide to be malicious, the only power you have is to not allow transactions for that 2.5 minutes, in which case you forfeit the money the network will pay you.
If all nodes were able to do it, the network would be vulnerable to sybil attacks. See my conversation with Anonymint.
The network is still vulnerable to sybil attacks with expensive nodes, but only by wealthy entities, and they would have to invest heavily in darkcoin to be able to do so, which would have the effect of strengthening the coin. I crunched some of the numbers, and you'd need a LOT of sybil nodes (50%+) to be able to snoop on a significant number of DS transactions where multiple mixing stages are employed. Which might be potentially feasible for a very motivated large organisation, but can be mitigated by specifying a high number of mixing stages (5-20).
Also, as the above poster pointed out, DOS on master nodes may be a problem. E.g. if an attacker DOS'd all the genuine master nodes successfully (which is unlikely, but this is hypothetical), only their own sybil nodes would remain, meaning anonymity is gone for that period. One way to mitigate this might be to have some network health indicators in the client. E.g. monitor the number of alive master nodes over time, and if it drops dramatically, have a little amber warning light on the send page to communicate that darksend transactions may be less secure. Or a graph of alive master nodes over time might be even better.
April 09, 2014, 05:17:19 AM
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...
The idea of masternodes is to create a very expensive network similar to mining, where users invest money to make money. If you decide to be malicious, the only power you have is to not allow transactions for that 2.5 minutes, in which case you forfeit the money the network will pay you.
If all nodes were able to do it, the network would be vulnerable to sybil attacks. See my conversation with Anonymint.
Really the concept sounds great -- I guess what I am really worried about is DOS attacks on the Master nodes. Some people will do due diligence, but I am betting that most won't (don't know how) and the result will be that DRK suffers a black eye because one person brings down Darksend for a time.
What protections are there against this other than urging master nodes owners to read up on net security?
April 09, 2014, 04:59:47 AM
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...
The idea of masternodes is to create a very expensive network similar to mining, where users invest money to make money. If you decide to be malicious, the only power you have is to not allow transactions for that 2.5 minutes, in which case you forfeit the money the network will pay you.
If all nodes were able to do it, the network would be vulnerable to sybil attacks. See my conversation with Anonymint.
April 09, 2014, 04:58:37 AM
April 09, 2014, 04:45:39 AM
Are you all forgetting....DRK will be internet cash.
Anonymous, no charge backs, decentralised currency moved in and out directly from your own electronic wallet.
Electronic cash. Which other coin out there at the moment has that without a third party service? None.
$250. If you give me a number less than that, I'll kick the cat.
Anonymous, no charge backs, decentralised currency moved in and out directly from your own electronic wallet.
Electronic cash. Which other coin out there at the moment has that without a third party service? None.
$250. If you give me a number less than that, I'll kick the cat.
April 09, 2014, 04:39:32 AM
Where I can find DRK coin calculator which working fine?
Jump to: