[ANN][SCRYPT] KlondikeCoin ★ Cryptsy.com ★ Prepaid VISA Cards ★ 0% Premine [KDC] - page 176.

SparkIt

hero member

Activity: 714

Merit: 529

Kheg, for god sake.
It's possible that this is a temporarily solution. I don't know. Even if it's not, what does it matter? If the pool team did the same thing the developers was going to do, but did it faster should devs decline the help and then rewrite the same thing?
I think it's a good thing that the community is helping the developer team, don't you?

I'm not one of the developers but I and a few more are helping them anyway. Is that wrong too?

Oh and Kheg, no offense but what are you doing to help the community at the moment? Except deprecate the developer team.

Criptoe started for a little while there btw, then you shut it down Sad

Gorbash

full member

Activity: 126

Merit: 100

Criptoe down? Sad

roastbeef

full member

Activity: 196

Merit: 100

Can someone verify that https://chunkypools.com/kdc/ looks correct?

Kheg

member

Activity: 196

Merit: 10

Quote from: KlondikeCoin on March 02, 2014, 07:57:43 PM

Quote from: 24Kilo on March 02, 2014, 07:54:02 PM

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/klondikecoin

At 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.

Wait wait wait... you're telling me that a "fix" was pushed by someone OTHER than the dev team? And you're asking us to willingly get on a fork run/started by a rogue pool?

That's freaking ridiculous.

To top it off, that means Criptoe has had EXCLUSIVE access to this fork for how long now at a ridiculously low difficulty?

I'm sorry... this is bullshit. Totally unacceptable on every level.

SparkIt

hero member

Activity: 714

Merit: 529

Quote from: ny2cafuse on March 02, 2014, 08:30:08 PM

Quote from: roastbeef on March 02, 2014, 08:23:56 PM

I'm getting errors from the coin daemon using the code from https://github.com/ny2cafuse/klondikecoin

Delete all the files from your config folder, with the exception of your wallet.dat file, and restart.

-Fuse

Should we do this with our personal wallets too?

roastbeef

full member

Activity: 196

Merit: 100

Forgot to remove the blockchain. Redownloading it now. Stratum should be up in a few minutes.

https://chunkypools.com/kdc/

ny2cafuse

legendary

Activity: 1582

Merit: 1002

HODL for life.

Quote from: roastbeef on March 02, 2014, 08:23:56 PM

I'm getting errors from the coin daemon using the code from https://github.com/ny2cafuse/klondikecoin

Delete all the files from your config folder, with the exception of your wallet.dat file, and restart.

-Fuse

Edit: Error is probably: "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."

KlondikeCoin

member

Activity: 84

Merit: 10

Quote from: roastbeef on March 02, 2014, 08:23:56 PM

I'm getting errors from the coin daemon using the code from https://github.com/ny2cafuse/klondikecoin

What errors are you getting and what nodes are listed in your conf?

roastbeef

full member

Activity: 196

Merit: 100

I'm getting errors from the coin daemon using the code from https://github.com/ny2cafuse/klondikecoin

KlondikeCoin

member

Activity: 84

Merit: 10

Cryptofountain confirmed using new build

@roastbeef - you can use the below as nodes to sync from as they are confirmed updated

kdc.cryptofountain.com
kdc.criptoe.com

ny2cafuse

legendary

Activity: 1582

Merit: 1002

HODL for life.

Quote from: roastbeef on March 02, 2014, 07:59:29 PM

ok, I can set this up. do you have new nodes?

You can add me right away with :

Code:

addnode:kdc.criptoe.com

My peer info list, as follows:

Code:

{
"addr" : "178.32.52.52:52640",
"services" : "00000003",
"lastsend" : 1393808796,
"lastrecv" : 1393808796,
"bytessent" : 83446074,
"bytesrecv" : 6236232,
"blocksrequested" : 73438,
"conntime" : 1393803778,
"version" : 70003,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "148.251.70.243:10691",
"services" : "00000003",
"lastsend" : 1393808796,
"lastrecv" : 1393808796,
"bytessent" : 99063554,
"bytesrecv" : 3221429,
"blocksrequested" : 84986,
"conntime" : 1393804960,
"version" : 70003,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "184.69.136.30:40517",
"services" : "00000003",
"lastsend" : 1393808796,
"lastrecv" : 1393808771,
"bytessent" : 90489688,
"bytesrecv" : 2994851,
"blocksrequested" : 79063,
"conntime" : 1393805640,
"version" : 70003,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "37.59.28.23:56680",
"services" : "00000003",
"lastsend" : 1393808796,
"lastrecv" : 1393808796,
"bytessent" : 36041264,
"bytesrecv" : 1905696,
"blocksrequested" : 36940,
"conntime" : 1393806389,
"version" : 70003,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : false,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "88.208.205.38:59736",
"services" : "00000003",
"lastsend" : 1393808801,
"lastrecv" : 1393808801,
"bytessent" : 29834277,
"bytesrecv" : 7708829,
"blocksrequested" : 30259,
"conntime" : 1393807955,
"version" : 70003,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : true,
"startingheight" : 4,
"banscore" : 0
},
{
"addr" : "94.23.152.226:54027",
"services" : "00000003",
"lastsend" : 1393808798,
"lastrecv" : 1393808798,
"bytessent" : 1399634,
"bytesrecv" : 189208,
"blocksrequested" : 5000,
"conntime" : 1393808771,
"version" : 70003,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
}

roastbeef

full member

Activity: 196

Merit: 100

Quote from: KlondikeCoin on March 02, 2014, 07:57:43 PM

Quote from: 24Kilo on March 02, 2014, 07:54:02 PM

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/klondikecoin

At 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?

KlondikeCoin

member

Activity: 84

Merit: 10

Quote from: 24Kilo on March 02, 2014, 07:54:02 PM

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/klondikecoin

At 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.

roastbeef

full member

Activity: 196

Merit: 100

Quote from: 24Kilo on March 02, 2014, 07:54:02 PM

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.

SparkIt

hero member

Activity: 714

Merit: 529

Oh, good. I thought something went wrong.
Didn't think that could happen with like 100% hashrate!

24Kilo

sr. member

Activity: 672

Merit: 250

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 just realised I had my whole mining farm pointed at KDC Criptoe from when we were testing... I pulled all my miners to help reduce hash-rate.

roastbeef

full member

Activity: 196

Merit: 100

I just put latest version of kdc from github up on chunky:

https://chunkypools.com/kdc/

0.8 diff -- is this correct?

barryzand

hero member

Activity: 574

Merit: 500

Growcoin Chief

Quote from: SparkIt on March 02, 2014, 07:47:59 PM

Quote from: 24Kilo on March 02, 2014, 07:43:24 PM

Quote from: SparkIt on March 02, 2014, 07:34:32 PM

Hey guys, I'm one of the community leaders.

To you guys who just got here and wonder what happened:
For a while after the fork everything went smooth, blocks were found and no issues were found. Some pools had forgot to update wallet so they were on their own block chain still finding 77KDC/block.

Then KDC forked and coins that were sent didn't arrive to the other wallet.
Some kind of wallet error was affecting every pool out there. Every pool went down until this was fixed. Criptoepool team started working on it and got it working. THOUGH THERE IS NO GREEN LIGHT FROM DEVELOPERS YET!

Wallets went to several different blockchains and KDC was forked.
Market at coinedup is temporarily halted until everything is fixed.

DO NOT SEND COINS TO ANOTHER WALLET UNTIL DEVELOPERS GIVES US THE GREEN LIGHT! BY SENDING COINS TO ANOTHER WALLET RIGHT NOW YOU CAN LOSE YOUR COINS!

I don't think criptoepool team wants to harm KDC.
Please don't DDOS their pool and start mining there instead.

I have no expertise in this subject but logically I think the right thing to do is to get the longest block chain and by this helping the developers. They will know which block chain is the longest and can pull the data from there and use it.
Can anyone with knowledge in this subject confirm or deny this?

Thanks... we mean no harm!!!

I feel quite responsible for dragging Criptoe into this as I have been the KDC supporter of the group. We have a very vested interest in seeing this resolved ASAP. We gave away over 1800KDC in block finder rewards leading up to the fork... we have invested heavily in the KDC community and pool to ensure success of KDC as a coin.

Causing forks and fracturing the community and blockchain is counterproductive for all of us... miners, pool operators, investors, merchants... everyone.

What we would like to see is another pool grab the fix we pushed to Github and use and create some stability for the time being. It will give all us a breathing space to test and deploy a proper fix.

Thanks!

What happened with pool? 700% shares

look at the "blocks" tab.. we found more of those lol

SparkIt

hero member

Activity: 714

Merit: 529

Quote from: 24Kilo on March 02, 2014, 07:43:24 PM

Quote from: SparkIt on March 02, 2014, 07:34:32 PM

Hey guys, I'm one of the community leaders.

To you guys who just got here and wonder what happened:
For a while after the fork everything went smooth, blocks were found and no issues were found. Some pools had forgot to update wallet so they were on their own block chain still finding 77KDC/block.

Then KDC forked and coins that were sent didn't arrive to the other wallet.
Some kind of wallet error was affecting every pool out there. Every pool went down until this was fixed. Criptoepool team started working on it and got it working. THOUGH THERE IS NO GREEN LIGHT FROM DEVELOPERS YET!

Wallets went to several different blockchains and KDC was forked.
Market at coinedup is temporarily halted until everything is fixed.

DO NOT SEND COINS TO ANOTHER WALLET UNTIL DEVELOPERS GIVES US THE GREEN LIGHT! BY SENDING COINS TO ANOTHER WALLET RIGHT NOW YOU CAN LOSE YOUR COINS!

I don't think criptoepool team wants to harm KDC.
Please don't DDOS their pool and start mining there instead.

I have no expertise in this subject but logically I think the right thing to do is to get the longest block chain and by this helping the developers. They will know which block chain is the longest and can pull the data from there and use it.
Can anyone with knowledge in this subject confirm or deny this?

Thanks... we mean no harm!!!

I feel quite responsible for dragging Criptoe into this as I have been the KDC supporter of the group. We have a very vested interest in seeing this resolved ASAP. We gave away over 1800KDC in block finder rewards leading up to the fork... we have invested heavily in the KDC community and pool to ensure success of KDC as a coin.

Causing forks and fracturing the community and blockchain is counterproductive for all of us... miners, pool operators, investors, merchants... everyone.

What we would like to see is another pool grab the fix we pushed to Github and use and create some stability for the time being. It will give all us a breathing space to test and deploy a proper fix.

Thanks!

What happened with pool? 700% shares

ny2cafuse

legendary

Activity: 1582

Merit: 1002

HODL for life.

Quote from: barryzand on March 02, 2014, 07:37:51 PM

always! i had it set though... but like i said.. i dont want to update wallet with these settings for now... i'm waiting for dev response before i fuck up anything lol.. having said that i trust your pool since you even helped the devs with this Wink

My only intention in my actions was to provide an immediate response to the problem at hand. I don't want to step on anyone's toes here. If I did, I apologize. I just have a vested interest in this coin succeeding, as well as my pool. If my fix doesn't solve the issue, then at least it's a step toward insuring that people update to the proper version. If it is the fix, then the devs need to keep on eye on these things in the future so this doesn't happen again.

Again, I'm sorry if I over-stepped my bounds. I'm just a take charge kind of guy, and I hate waiting around for things that I can try to fix myself.

-Fuse

Topic: [ANN][SCRYPT] KlondikeCoin ★ Cryptsy.com ★ Prepaid VISA Cards ★ 0% Premine [KDC] - page 176. (Read 554419 times)