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

24Kilo

sr. member

Activity: 672

Merit: 250

Quote from: hash.so on March 02, 2014, 07:07:53 PM

But if I take the old code, add your changes and connect to "your" network, I can still create a new fork? At least to me it seems that way, I don't think you fixed the underlying issue.

Also your fork is not the longest

84922 vs 84913

You are not connecting to 'our' network... you are connecting to the network which the dev team compiled and supplied widows wallet is on... we did not create our own network... we only fixed the pool wallet so it would connect to the personal wallet network... that is what seems to have caused the fork.

Agreed - my Windows server wallet is about 2 blocks ahead... hmmm...

Jilixi

full member

Activity: 196

Merit: 100

Quote from: hash.so on March 02, 2014, 07:07:53 PM

Quote from: ny2cafuse on March 02, 2014, 06:54:30 PM

Quote from: Jilixi on March 02, 2014, 06:53:18 PM

Quote from: ny2cafuse on March 02, 2014, 06:51:51 PM

Quote from: hash.so on March 02, 2014, 06:46:43 PM

I don't think it fixed the issue.

edit: new wallet was started with "-rescan -reindex"

Delete everything but your wallet.dat file and restart. We're pegging blocks on CripToe.

-Fuse

Please stop with the risk of everyone moving there and causing yet another fork? can we please calm down? You asume everyone to compile from your code and just go with it. Waiting for Dev ann

Do you understand that if we are on the highest chain, it will be the proper fork? Essentially, the dev will need to verify the code, pull it, and then create a block checkpoint. Highest fork wins, mate. Right now, the pool is on the highest fork, and climbing. That's how this works.

-Fuse

Edit: Also, when a coin forks, you can't just wait around. You need to fix the issue before the forks grow too far apart and other forks happen. The only thing my change does was limit connections between nodes by only allowing newer clients to connect. It blacklists the old clients which probably caused the issue in the first place. Check my pull request on github, nothing fancy there.

But if I take the old code, add your changes and connect to "your" network, I can still create a new fork? At least to me it seems that way, I don't think you fixed the underlying issue.

Also your fork is not the longest

84922 vs 84913

I can confirm this, you are not on the longest chain.

Sparkzor

member

Activity: 112

Merit: 10

Quote from: barryzand on March 02, 2014, 07:10:15 PM

with this difficulty and current blocksize were getting more coins an hour then with the old blocksize lol Cool

But we don't know which blockchain is the correct one.

The coins that is mined at criptoe is worthless if it's not the longest blockchain as I understand it.

barryzand

hero member

Activity: 574

Merit: 500

Growcoin Chief

with this difficulty and current blocksize were getting more coins an hour then with the old blocksize lol Cool

hash.so

full member

Activity: 126

Merit: 100

Quote from: ny2cafuse on March 02, 2014, 06:54:30 PM

Quote from: Jilixi on March 02, 2014, 06:53:18 PM

Quote from: ny2cafuse on March 02, 2014, 06:51:51 PM

Quote from: hash.so on March 02, 2014, 06:46:43 PM

I don't think it fixed the issue.

edit: new wallet was started with "-rescan -reindex"

Delete everything but your wallet.dat file and restart. We're pegging blocks on CripToe.

-Fuse

Please stop with the risk of everyone moving there and causing yet another fork? can we please calm down? You asume everyone to compile from your code and just go with it. Waiting for Dev ann

Do you understand that if we are on the highest chain, it will be the proper fork? Essentially, the dev will need to verify the code, pull it, and then create a block checkpoint. Highest fork wins, mate. Right now, the pool is on the highest fork, and climbing. That's how this works.

-Fuse

Edit: Also, when a coin forks, you can't just wait around. You need to fix the issue before the forks grow too far apart and other forks happen. The only thing my change does was limit connections between nodes by only allowing newer clients to connect. It blacklists the old clients which probably caused the issue in the first place. Check my pull request on github, nothing fancy there.

But if I take the old code, add your changes and connect to "your" network, I can still create a new fork? At least to me it seems that way, I don't think you fixed the underlying issue.

Also your fork is not the longest

84922 vs 84913

24Kilo

sr. member

Activity: 672

Merit: 250

Quote from: Jilixi on March 02, 2014, 06:53:18 PM

Please stop with the risk of everyone moving there and causing yet another fork? can we please calm down? You asume everyone to compile from your code and just go with it. Waiting for Dev ann

Thanks for the compliments!

Fuse, myself, another private pool operator and another experienced miner just spent the last 6 hours working on a fix... running tests, compiling wallets, setting up temporary servers and whatever... we did this to help KDC recover from a rapidly deteriorating situation.

All the fixes have been pushed to Github for Klondikecoin to review... plus he just confirmed the technical coin dev team was asleep!!! Of course, they are humans and need and deserve sleep... but since this is a team effort we volunteered our time and resources instead of waiting for another few hours for them to wake up and KDC to slide into a real mess.

All the code and fixes is there for everyone to use.

I can confirm that the compiled Windows wallet on the KDC homepage works... I used to to run a solo mining server... it may need a slight fix... but it is on the right block chain and will confirming transactions.

BUT DO NOT MOVE KDC UNTIL ALL IS CONFIRMED BY DEV TEAM!!!

So no need for the panic... Criptoe is not hard-forking KDC or organising a hostile takeover... we just provided a much needed community service in a time of need.

phrozenspite

sr. member

Activity: 266

Merit: 250

Quote from: ny2cafuse on March 02, 2014, 06:54:30 PM

Quote from: Jilixi on March 02, 2014, 06:53:18 PM

Quote from: ny2cafuse on March 02, 2014, 06:51:51 PM

Quote from: hash.so on March 02, 2014, 06:46:43 PM

I don't think it fixed the issue.

edit: new wallet was started with "-rescan -reindex"

Delete everything but your wallet.dat file and restart. We're pegging blocks on CripToe.

-Fuse

Please stop with the risk of everyone moving there and causing yet another fork? can we please calm down? You asume everyone to compile from your code and just go with it. Waiting for Dev ann

Do you understand that if we are on the highest chain, it will be the proper fork? Essentially, the dev will need to verify the code, pull it, and then create a block checkpoint. Highest fork wins, mate. Right now, the pool is on the highest fork, and climbing. That's how this works.

-Fuse

that's how it's supposed to work anyways. look at the bitcoin fork last year, slush's pool found a bunch of blocks on a chain and was on the correct wallet, but they rolled it back to keep the exchanges and some others who were still running older versions of the software happy.

barryzand

hero member

Activity: 574

Merit: 500

Growcoin Chief

Quote from: ny2cafuse on March 02, 2014, 06:54:30 PM

Quote from: Jilixi on March 02, 2014, 06:53:18 PM

Quote from: ny2cafuse on March 02, 2014, 06:51:51 PM

Quote from: hash.so on March 02, 2014, 06:46:43 PM

I don't think it fixed the issue.

edit: new wallet was started with "-rescan -reindex"

Delete everything but your wallet.dat file and restart. We're pegging blocks on CripToe.

-Fuse

Please stop with the risk of everyone moving there and causing yet another fork? can we please calm down? You asume everyone to compile from your code and just go with it. Waiting for Dev ann

Do you understand that if we are on the highest chain, it will be the proper fork? Essentially, the dev will need to verify the code, pull it, and then create a block checkpoint. Highest fork wins, mate. Right now, the pool is on the highest fork, and climbing. That's how this works.

-Fuse

i hope so man... were getting lots of coins like this LOL

ny2cafuse

legendary

Activity: 1582

Merit: 1002

HODL for life.

Quote from: Jilixi on March 02, 2014, 06:53:18 PM

Quote from: ny2cafuse on March 02, 2014, 06:51:51 PM

Quote from: hash.so on March 02, 2014, 06:46:43 PM

I don't think it fixed the issue.

edit: new wallet was started with "-rescan -reindex"

Delete everything but your wallet.dat file and restart. We're pegging blocks on CripToe.

-Fuse

Please stop with the risk of everyone moving there and causing yet another fork? can we please calm down? You asume everyone to compile from your code and just go with it. Waiting for Dev ann

Do you understand that if we are on the highest chain, it will be the proper fork? Essentially, the dev will need to verify the code, pull it, and then create a block checkpoint. Highest fork wins, mate. Right now, the pool is on the highest fork, and climbing. That's how this works.

-Fuse

Edit: Also, when a coin forks, you can't just wait around. You need to fix the issue before the forks grow too far apart and other forks happen. The only thing my change does was limit connections between nodes by only allowing newer clients to connect. It blacklists the old clients which probably caused the issue in the first place. Check my pull request on github, nothing fancy there.

Jilixi

full member

Activity: 196

Merit: 100

Quote from: ny2cafuse on March 02, 2014, 06:51:51 PM

Quote from: hash.so on March 02, 2014, 06:46:43 PM

I don't think it fixed the issue.

edit: new wallet was started with "-rescan -reindex"

Delete everything but your wallet.dat file and restart. We're pegging blocks on CripToe.

-Fuse

Please stop with the risk of everyone moving there and causing yet another fork? can we please calm down? You asume everyone to compile from your code and just go with it. Waiting for Dev ann

ny2cafuse

legendary

Activity: 1582

Merit: 1002

HODL for life.

Quote from: hash.so on March 02, 2014, 06:46:43 PM

I don't think it fixed the issue.

edit: new wallet was started with "-rescan -reindex"

Delete everything but your wallet.dat file and restart. We're pegging blocks on CripToe.

-Fuse

niceman

sr. member

Activity: 336

Merit: 254

CoinMine.pw

You are kidding me?
You make Hard fork and don't even change version in official GitHub sources? All exchanges with 50 coins should monitor this thread to find what you changed rules?

Jilixi

full member

Activity: 196

Merit: 100

Quote from: bentmar on March 02, 2014, 06:49:09 PM

Shouldnt we wait for dev to announce a new wallet instead of creating new forks?

As far as I know this doesnt fork it, it fixes an issue.

ny2cafuse

legendary

Activity: 1582

Merit: 1002

HODL for life.

KDC.CripToe.Com is running at highest block height with the my code change. WE ARE MINING, FOLKS.

-Fuse

bentmar

member

Activity: 84

Merit: 10

Shouldnt we wait for dev to announce a new wallet instead of creating new forks?

hash.so

full member

Activity: 126

Merit: 100

From a wallet with the fixes:

Code:

{
   "version" : 80602,
   "protocolversion" : 70003,
   "walletversion" : 60000,
   "balance" : 19906.35908113,
   "blocks" : 84892,
   "timeoffset" : 0,
   "connections" : 3,
   "proxy" : "",
   "difficulty" : 0.86805923,
   "testnet" : false,
   "keypoololdest" : 1391463292,
   "keypoolsize" : 101,
   "paytxfee" : 0.00000000,
   "mininput" : 0.00001000,
   "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}

and old wallet

Code:

{
   "version" : 80601,
   "protocolversion" : 70002,
   "walletversion" : 60000,
   "balance" : 19938.49485507,
   "blocks" : 84905,
   "timeoffset" : -1,
   "connections" : 54,
   "proxy" : "",
   "difficulty" : 0.86482884,
   "testnet" : false,
   "keypoololdest" : 1393734951,
   "keypoolsize" : 101,
   "paytxfee" : 0.00000000,
   "mininput" : 0.00001000,
   "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}

I don't think it fixed the issue.

edit: new wallet was started with "-rescan -reindex"

hash.so

full member

Activity: 126

Merit: 100

Quote from: ny2cafuse on March 02, 2014, 06:07:55 PM

Can someone verify the highest block height known right now?

-Fuse

84889

edit: derp, missed the new page

rynomite

newbie

Activity: 3

Merit: 0

My solo mining efforts have never been this good. Hope I'm on the right chain with this new wallet and get to keep some of them

24Kilo

sr. member

Activity: 672

Merit: 250

personal wallets seem to be on the right blockchain which is the longest... Placebo, Sparkzor and I are on the same blockchain.

I have a solo mined found block with 53 confirms and quite a few more... with no orphans yet.

ny2cafuse

legendary

Activity: 1582

Merit: 1002

HODL for life.

Quote from: KlondikeCoin on March 02, 2014, 06:10:28 PM

Absolutely,

if a community fix can be sorted asap i'm happy to take a look and approve it and push everyone to update - Karl & Dave usually handle the bulk of the code however i cannot get hold of them as they both have work commitments early in the morning and have gone to sleep - as the update seemed to have gone fine. Dave usually wakes up at obscure times so should get my messages in the next few hours.

@fuse, i'll take a look

Klondike, and others...

https://github.com/ny2cafuse/klondikecoin. Pull request submitted.

Like I said, it could be a version issue, but without the original code, I can't verify. However, this is to test that anyway. It increases the version and protocol number and limits connections to only clients running that version(tested and verified). Essentially shutting out older clients. It's a first step to making sure everyone is updated. It may also solve the issues we are seeing, but I can't tell until we see it large scale.

If you decide to compile and use this code, you will need to connect to another pool or node running it. But the pool or node will need to be on the correct chain. I'm reindexing (klondikecoind -reindex) right now to rescan the blocks, and I'm coming back up. Try the following addnode if you use the code:

Code:

addnode:kdc.criptoe.com

Like I said, it might not work, but it eliminates the variable.

-Fuse

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