Who is dumping dark coins with a bot on c-cex? 
Moby Dick?
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 6949. (Read 9723475 times)
February 10, 2014, 10:52:33 AM
Moby Dick?
February 10, 2014, 10:51:24 AM
putt...putt....putt
the little engine that could....
LOL G'Mornin
the little engine that could....
LOL G'Mornin
February 10, 2014, 10:41:55 AM
Who is dumping dark coins with a bot on c-cex?
February 10, 2014, 10:35:33 AM
eduffield, once the fork is done, may I recommend the following title?
[ANN][DRK] DarkCoin | First Anonymous Coin | CPU only | KGW | ASIC Resistant | No Premine
This makes us Vertcoin on steroids (which we are) thanks to you
[ANN][DRK] DarkCoin | First Anonymous Coin | CPU only | KGW | ASIC Resistant | No Premine
This makes us Vertcoin on steroids (which we are) thanks to you
February 10, 2014, 10:34:11 AM
Have the exchanges updated?
February 10, 2014, 10:28:08 AM
So, have all the pools updated? If so, only solo miners are at risk for being left behind
All except for yoba it seems, which is ~300Kh. So we're in the clear
February 10, 2014, 10:15:01 AM
So, have all the pools updated? If so, only solo miners are at risk for being left behind
February 10, 2014, 09:56:48 AM
Thanks! Do we need to restart miners?
No, without problems
February 10, 2014, 09:47:51 AM
Thanks! Do we need to restart miners?
February 10, 2014, 09:27:20 AM
February 10, 2014, 08:03:53 AM
Yobapool is tiny and CPUPool has been updated (or is in progress).
February 10, 2014, 06:38:55 AM
It looks like it is really hard to find a new block with current difficulty.
I mine with drk.smalltimeminer.com and it took us 13 hours (!) to find a new block.
On coinmine.pl/drk I also last block was found over 4 hours ago.
Waiting for difficulty to decrease.
I mine with drk.smalltimeminer.com and it took us 13 hours (!) to find a new block.
On coinmine.pl/drk I also last block was found over 4 hours ago.
Waiting for difficulty to decrease.
kgw will activate at block 15200
February 10, 2014, 06:33:21 AM
It looks like it is really hard to find a new block with current difficulty.
I mine with drk.smalltimeminer.com and it took us 13 hours (!) to find a new block.
On coinmine.pl/drk I also last block was found over 4 hours ago.
Waiting for difficulty to decrease.
I mine with drk.smalltimeminer.com and it took us 13 hours (!) to find a new block.
On coinmine.pl/drk I also last block was found over 4 hours ago.
Waiting for difficulty to decrease.
February 10, 2014, 05:14:11 AM
(11111 / (((Difficulty+51)/6) ^ 2)) ,,,,,,,,,,,,,,,,,
February 10, 2014, 04:39:36 AM
Hi,
Is there an easy to understand guide on how to mine darkcoin on osx? I'm new to mining and have been trying for hours and I'm no further forward. I've downloaded the standalone miner but can't get it to connect to the pool.
Any help very much appreciated.
D
Is there an easy to understand guide on how to mine darkcoin on osx? I'm new to mining and have been trying for hours and I'm no further forward. I've downloaded the standalone miner but can't get it to connect to the pool.
Any help very much appreciated.
D
type your command line here, and we will try to help
ior go on irc #darkcoin
I'm getting the following when I try to compile..
chmod +x ./nomacro.pl
./nomacro.pl
./configure CFLAGS="-03"
-bash: ./configure: No such file or directory
not ./nomacro.pl
use
autogen.sh
Ok, thanks for that. I ran ./autogen.sh then got the following types of message...
Makefile.am:18: warning: source file 'x5/shavite.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
Makefile.am:18: warning: source file 'x5/cubehash_sse2.c' is in a subdirectory,
Makefile.am:18: but option 'subdir-objects' is disabled
February 10, 2014, 02:31:43 AM
>You only have to move files when going from the xcoin wallet to the darkcoin wallet
Yes, my current wallet is Xcoin-wallet (v.8.6.2).
What do you mean with "purple file above"?
Btw, I suppose wallet doesn't sync because of Usergate.
[/quote]
I'm sorry, I'm getting tired, LOL, but if you look at my post above, I wrote the windows path (vista or 7) for the wallet data. Just put the stuff in the xcoin folder into the darkcoin folder and you'll be good to go
February 10, 2014, 02:27:51 AM
Thanks for new wallet, but I don't understand what's all about. I've used v.6.2 before and does it mean that I missed all the coins that I got earlier?
Upgrading to the new wallet wont cause you to lose coins.
That being said you should ALWAYS make a backup copy to keep somewhere else. I have heard of people formatting their hard drive or computer crashing and losing all their coins because they didnt backup the wallet.dat file, which can NEVER be recovered.
Thank you. I'll check it when wallet would be synchronized. Now, unfortunately, there are no connections.
I'm worried about it because I've already mined some coin when developers have done changes with it, so I missed that upgrade and got nothing of mining.
P.S. would you give me some nodes, please? I already added this ones:
addnode 23.23.186.131 add
addnode 50.16.206.102 add
addnode 50.19.116.123 add
addnode 98.165.130.67 add
If you had an old wallet, there is no need to re-sync. Just put the old wallet's info in the purple file above into the new one. In fact, if you're just upgrading another DarkCoin wallet, after making a backup just in case, you just start the new .exe file and it uses the old wallet's info. You only have to move files when going from the xcoin wallet to the darkcoin wallet
>You only have to move files when going from the xcoin wallet to the darkcoin wallet
Yes, my current wallet is Xcoin-wallet (v.8.6.2).
What do you mean with "purple file above"?
Btw, I suppose wallet doesn't sync because of Usergate.
February 10, 2014, 02:22:59 AM
OK, panic over, some familiar little clockies with confirmations................phew.
Tante, before I forget, with azure, the clock is always ticking unless you completely delete the machines you've put all that effort into configuring. I kicked myself once and decided to shut them all down last night due to the whale, then I kicked myself even harder just now when I realised that they have to be completely deleted in order to stop the clock.
Tante, before I forget, with azure, the clock is always ticking unless you completely delete the machines you've put all that effort into configuring. I kicked myself once and decided to shut them all down last night due to the whale, then I kicked myself even harder just now when I realised that they have to be completely deleted in order to stop the clock.
oh bother.... LOL
thanks for letting me know
Done, I have 186 dollars credit still... eh, not too terrible
February 10, 2014, 02:20:17 AM
Thanks for new wallet, but I don't understand what's all about. I've used v.6.2 before and does it mean that I missed all the coins that I got earlier?
Upgrading to the new wallet wont cause you to lose coins.
That being said you should ALWAYS make a backup copy to keep somewhere else. I have heard of people formatting their hard drive or computer crashing and losing all their coins because they didnt backup the wallet.dat file, which can NEVER be recovered.
Thank you. I'll check it when wallet would be synchronized. Now, unfortunately, there are no connections.
I'm worried about it because I've already mined some coin when developers have done changes with it, so I missed that upgrade and got nothing of mining.
P.S. would you give me some nodes, please? I already added this ones:
addnode 23.23.186.131 add
addnode 50.16.206.102 add
addnode 50.19.116.123 add
addnode 98.165.130.67 add
If you had an old wallet, there is no need to re-sync. Just put the old wallet's info in the purple file above into the new one. In fact, if you're just upgrading another DarkCoin wallet, after making a backup just in case, you just start the new .exe file and it uses the old wallet's info. You only have to move files when going from the xcoin wallet to the darkcoin wallet
February 10, 2014, 02:19:01 AM
OK, panic over, some familiar little clockies with confirmations................phew.
Tante, before I forget, with azure, the clock is always ticking unless you completely delete the machines you've put all that effort into configuring. I kicked myself once and decided to shut them all down last night due to the whale, then I kicked myself even harder just now when I realised that they have to be completely deleted in order to stop the clock.
Tante, before I forget, with azure, the clock is always ticking unless you completely delete the machines you've put all that effort into configuring. I kicked myself once and decided to shut them all down last night due to the whale, then I kicked myself even harder just now when I realised that they have to be completely deleted in order to stop the clock.
Jump to: