KDC CripToe has closed temporarily closed registrations.
We do truly appreciate the hash-rate... but we do not want to own the network... and miners are piling in on KDC Criptoe... and this going to result in a lot of coins turning into dust for many people... all the way around.
Can another pool operator please speak with the dev team and take the risk to use our fix so we can do as much as we can to protect miners hard work and hash-rate.
Thanks! I have pm'd some pool ops. @roastbeef - there was a problem with the update, a fix was supplied by another user and the wallet can be grabbed from here: https://github.com/ny2cafuse/klondikecoinAt the moment that will put you on the new official/unofficial chain. We will confirm 100% asap if we need to rollback or anything else. I'm currently updating some of our nodes and the block explorer so we can get a better idea of whats going on. The windows wallet will also need to be recompiled. The official github will be updated once we are 100% happy this has resolved everything. ok, I can set this up. do you have new nodes?
|
|
|
KDC CripToe has closed temporarily closed registrations.
We do truly appreciate the hash-rate... but we do not want to own the network... and miners are piling in on KDC Criptoe... and this going to result in a lot of coins turning into dust for many people... all the way around.
Can another pool operator please speak with the dev team and take the risk to use our fix so we can do as much as we can to protect miners hard work and hash-rate.
Thanks! Is there something I need to do besides use the latest code from github? I see my pool has the same difficulty as yours.
|
|
|
How does this work? If I had 100 scrypt miners, I'd have about 100MH/s maybe. One of those $10 USB ASICs does 333MH/s in sha256. What does it do to make this fair?
|
|
|
yo! we just set up a test flap pool on our new host. just found our first block too. feel free to give it a try. https://chunkypools.com/flap/- 1% PROP - SSL Note: If you've signed up on our old pool.chunky.ms system, you won't need to re-register because our account system is shared between coins.
|
|
|
hello! we just launched a test Swansoncoin pool on our new host. it's screaming! https://chunkypools.com/ron/- 1% PROP - SSL If you have an account on our pool.chunky.ms system, you won't need to re-register here.
|
|
|
If you guys think that it's prudent to move the fork twice, then you're badly mistaken. It's human nature for someone who has just updated something to give that something less attention for a period of time. If you get your car's brakes fixed, you don't check them again for a while. I updated, and I was told it would be AT LEAST a week until I had to worry about it again.
Pardon me for taking the dev at his word and not checking this thread or paying attention to my PMs over the weekend.
|
|
|
keep it down then. ok, fine nice attitude considering this is your fault This is your fault. Dev working hard ro make this coin better, you are pool owner - then make YOUR job and READ thread of coins that you host. READ messages, that dev sent you. STOP complaining, you are making money and this is YOUR JOB. I'm not going to get in a fight with all of you. The point is, the guy told me it would be 7-10 days. Then he completely reneged on that. I keep up with my pools. I can't possibly read every message in all threads of all coins that I host.
|
|
|
you are in this list: *"Del137", "coinmarket.io", "GREEDYJOHN", "Imperative", "Thecivico88" *"ethought", "virtualdn", "f1ndm3h", "redmist", "destructor3" *"f1ndm3h", "MoNxO", "def_ender", "userpacman", "SwagMiner" *"DESUChANE6", "whoiis", "Fckbankscoin", "InCoinsWeTrust", "coincrow" *"aaron_m", "hash.so", "chinbadboy", "rustylezaz", "sakkosekk" *"ahnonamis", "roastbeef", "Jiyome", "bittick", "adam9317" *"taken2", "btcltcdigger", "Ya", "ress", "Altcoinfaucet" *"Danz0r77", "KeyserSozeMC", "LitcoinCollector", "Hepic", "patyjm" *"xhash", "hashfun", "paulus51", "dasource", "GregH37" *"djslick", "mysticcrypto", "cyrilbf", "Pattes", "cdoyle14" *"yogg", "blaster51", "stas", "NJRiot", "rednalexa" you should have received an update message for gravity 3 Yeah! I read it a few minutes ago when my blockchain was forked! Jesus Christ, you didn't think moving the fork up 5 days after telling people it would be 7-10 days would be a problem?
|
|
|
keep it down then. ok, fine nice attitude considering this is your fault
|
|
|
keep it down then.
listen... the coin was dead... again... you wouldnt have made anything.
if middlecoin would have pushed hashrate to 22-25ghash and beyond.
diff would become 200-300. and all your miners would have left.
so your pool would have become an empty pool as well.
we had this set at block 21203. i wonder if you even would have updated by then.
we announced this all through twitter, facebook, irc channels, emails, did huge giveaways, wrote updatecheck bots
what pool are we talking about here.
DUDE I updated on Feb 7th. You told me it would be 7 to 10 days before the fork hit. I didn't even think to check back because I had at least a week. This is your fucking fault. At least own it.
|
|
|
ppl we wont refund anything.
thats that.
further.... the coin would be dead ( and you would have nothing at all ) if we didnt update this.
we invested more then 10! million coins to get
a) updates through b) keep multipools off ( 2 million a day to send only 5ghash ) c) made upgrade rewards
not to speak of the time we invested.
if we didnt all do this... the coin would most certain be completely dead.
we did as asked by the community.
we warned that this could happen, multiple times.
anyways... the coin is now back alive again and is usable.
no more blocklengths of 15 minutes or more.
so if you think you lost something, we lost a whole lot more ( even own money )
it might increase in value soon when we have finished the projects.
there will be no more updates for a while.
also the multipools are still on this.
I'm not asking for refunds. I can repay all my users for like $30. Who gives a shit. What I am worried about is reputation damage. It looks like we're the irresponsible pool owners, when in fact it was Leafcoin's shitty decisions that caused this mess. You released a coin without doing any research, then your coin goes to difficulty purgatory, and instead of giving pools ample time to update and just waiting it out (RonPaulCoin did this the right way), you got impatient and changed the fork block height THREE times! I updated our daemon twice, and still got shafted here. Terribly irresponsible moves by the Leafcoin dev team. Not sure if I even want to open the pool back up.
|
|
|
Hey LEAFCOIN thread, looking for a place to mine LEAF? Join us at Chunky Pool!
You a at wrong chain. Congratulations. No shit. We updated the daemon 3 days ago. Not very responsible of the devs to release 3 times in a week, moving the fork closer and closer. I was told it would be a week before the fork hit anyway.
|
|
|
Has the LEAF blockchain forked? I have a miner in my pool whose wallet is not showing his deposit. His wallet is synced up, and the blockexplorer @ cryptexplorer.com shows the correct deposit. I can't think of anything else besides a forked blockchain.
Yes, because of update, since block 18818. This is correct chain: http://explorer.leafco.in/chain/LeafCoinhttp://cryptexplorer.com/chain/LeafCoin was not yet updated and is on wrong fork. Hmm, looks like my pool is on the wrong fork. We just updated on Feb 7th! What the fuck! In order to correct this issue, do I need to redownload the blockchain once I have updated?
|
|
|
|