[KGC] The future is krugercoin and the future is now! [Official Launch]

[JohnnyCrypto]

Good hope cryptsy gets their wallet updated soon as well. 

I'm all synced up now on the right chain.

Had one small problem though. I did get stuck at block 1119999. With the new client.

So i ran the old client with the edited "start.bat" file. I then synced from 1119999>1121075.

I then ran the new client with the edited "start.bat" file.

Now everything is good, with correct chain nodes. 

Good luck everyone.

[1715035708]

1715035708

[almightyruler]

Had one small problem though. I did get stuck at block 1119999. With the new client.

I'm stuck at 1119999 again. It looks like -connect only restricts outbound connects, but will not disable inbound connects, so any peers on the wrong fork which you've communicated with previously will still be able to connect.

I think the only reliable way to properly upgrade may be to install a copy of the blockchain database from the correct chain. A checkpoint would probably not hurt, either.

This mess would probably not have happened if the KGW fork was properly scheduled!

[UniMatrixZ]

How about if you did a clean install of the client?

I just did it on my work computer, edited start.bat before I started the client.
And I did not create a conf file.

Let's see how it goes.

I wonder where the dev is, should be in his interest to fix this.

Make sure to backup wallet.dat before you do a clean install!

[almightyruler]

If you have a cable or DSL connection that assigns a different IP each time you drop and reconnect it would be a very good idea to do this. That way you are likely to be assigned a virgin IP that old peers on the wrong fork will not know about.

[UniMatrixZ]

miners-pool.eu down?

Edit: back up now 

[Nibiru]

How to get on the right chain (winwallet):

1. Go to your appdata folder and find Krugercoin folder, go into the Krugercoin folder.
2. Start notepad
3. Write the following:

listen=1
daemon=1
server=1
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=8772

Choose save as krugercoin.conf (not krugercoin.conf.txt)

Or if you already have a krugercoin.conf file, edit it to only contain the lines above.

4. Delete the following files in the Krugercoin folder

blk0001.dat
blkindex.dat
peers.dat

5. Now go to your krugercoin-qt folder and find start.bat, open it in notepad
6. Delete this line:

krugercoin-qt.exe -addnode=192.186.133.74 -addnode=84.22.96.60 -addnode=117.27.250.149

and replace with the following line

krugercoin-qt.exe -connect=84.104.23.68 -connect=94.181.11.189 -connect=krugercoin.miners-pool.eu

7. Save the file
8. IMPORTANT! Start your wallet using start.bat(otherwise it will sync using the wrong nodes)and let it sync, may take awhile.
9. Done 

Thanks for this I have updated the wallets with above information thanks --- Yes you are all right should of planned it better -- I have been on a bit of tight schedule with various stuff -- my apologies to those affected!

You are a great bunch off guys/girls and I really appreciate it!

# cheers to eaverybody helping .....

 

[Nibiru]

Maybe some dev could talk to Cryptsy and tell them to update their wallet? 

I created a ticket this morning. Waiting for answer.
But I don't know if Nibiru has already created his ticket

Yes have also sent ticket

[UniMatrixZ]

How to get on the right chain (winwallet):

1. Go to your appdata folder and find Krugercoin folder, go into the Krugercoin folder.
2. Start notepad
3. Write the following:

listen=1
daemon=1
server=1
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=8772

Choose save as krugercoin.conf (not krugercoin.conf.txt)

Or if you already have a krugercoin.conf file, edit it to only contain the lines above.

4. Delete the following files in the Krugercoin folder

blk0001.dat
blkindex.dat
peers.dat

5. Now go to your krugercoin-qt folder and find start.bat, open it in notepad
6. Delete this line:

krugercoin-qt.exe -addnode=192.186.133.74 -addnode=84.22.96.60 -addnode=117.27.250.149

and replace with the following line

krugercoin-qt.exe -connect=84.104.23.68 -connect=94.181.11.189 -connect=krugercoin.miners-pool.eu

7. Save the file
8. IMPORTANT! Start your wallet using start.bat(otherwise it will sync using the wrong nodes)and let it sync, may take awhile.
9. Done  

Thanks for this I have updated the wallets with above information thanks --- Yes you are all right should of planned it better -- I have been on a bit of tight schedule with various stuff -- my apologies to those affected!

You are a great bunch off guys/girls and I really appreciate it!

# cheers to eaverybody helping .....

  

Wonderful!

I'm not sure if you really need to make a conf file unless you are going to solomine.
Testing without conf file at my work computer right now, just now at ~91% synced.
Let's see what happens at block 1119999.
Saw a few that got stuck at that block.

This solution does not work I'm also stuck at block 1119999
What to do now
 


Any ideas???

[ekoja]

where is the FUTURE?

[UniMatrixZ]

Good hope cryptsy gets their wallet updated soon as well.  

I'm all synced up now on the right chain.

Had one small problem though. I did get stuck at block 1119999. With the new client.

So i ran the old client with the edited "start.bat" file. I then synced from 1119999>1121075.

I then ran the new client with the edited "start.bat" file.

Now everything is good, with correct chain nodes.  

Good luck everyone.

Where can I find the old client?

Seems we may need a whole new wallet.

[JohnnyCrypto]

Good hope cryptsy gets their wallet updated soon as well.  

I'm all synced up now on the right chain.

Had one small problem though. I did get stuck at block 1119999. With the new client.

So i ran the old client with the edited "start.bat" file. I then synced from 1119999>1121075.

I then ran the new client with the edited "start.bat" file.

Now everything is good, with correct chain nodes.  

Good luck everyone.

Where can I find the old client?

Seems we may need a whole new wallet.

Here is the old client, if you would like to try out what i did above. 

http://www.sendspace.com/file/9zvvnz

[carloss]

The network is all messed up, even if I delete everything and connect only to nodes mentioned above, still can't get past the block 1119999.
I run freshly compiled client from git, and still getting this:

Code:

Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 1.89579
Before: 1d08e4b4  00000008e4b40000000000000000000000000000000000000000000000000000
After:  1d04b0ed  00000004b0ed7810c46a97810c46a97810c46a97810c46a97810c46a97810c46
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node krugercoin.miners-pool.eu
Disconnected krugercoin.miners-pool.eu for misbehavior (score=100)
received block f686dffe3bf6baa058b0
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 1.89579
Before: 1d08e4b4  00000008e4b40000000000000000000000000000000000000000000000000000
After:  1d04b0ed  00000004b0ed7810c46a97810c46a97810c46a97810c46a97810c46a97810c46
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 94.181.11.189
Disconnected 94.181.11.189 for misbehavior (score=100)

[UniMatrixZ]

Good hope cryptsy gets their wallet updated soon as well.  

I'm all synced up now on the right chain.

Had one small problem though. I did get stuck at block 1119999. With the new client.

So i ran the old client with the edited "start.bat" file. I then synced from 1119999>1121075.

I then ran the new client with the edited "start.bat" file.

Now everything is good, with correct chain nodes.  

Good luck everyone.

Where can I find the old client?

Seems we may need a whole new wallet.

Here is the old client, if you would like to try out what i did above.  

http://www.sendspace.com/file/9zvvnz

Worked like charm.
Ran the old client with modified start.bat synced from 1119999>1121075
The ran the new client with modified start.bat and I'm now synced 

This is not a workable solution for everybody, so devs we need a new wallet that will sync past block 1119999

[almightyruler]

The network is all messed up, even if I delete everything and connect only to nodes mentioned above, still can't get past the block 1119999.
I run freshly compiled client from git, and still getting this:

Code:

Difficulty Retarget - Kimoto Gravity Well
[...]
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node krugercoin.miners-pool.eu
Disconnected krugercoin.miners-pool.eu for misbehavior (score=100)

I have finally been able to sync the client on another computer, and the problem appears to be exactly what I described earlier in this thread: because KGW went into immediate effect rather than being scheduled for the future, everyone has created their own hard fork at the point they upgraded. It looks like krugercoin.miners-pool.eu were using the old client (and therefore old difficulty retarget algorithm) well past block 1120000, which is why their client is disagreeing with everyone who is trying to sync from before that point.

New clients trying to sync calculate retarget using KGW from block 1120000 and onwards, but krugercoin.miners-pool.eu has already calculated that block and added it to their chain using the old algo. So the local client will say hang on, the difficulty retarget that krugercoin.miners-pool.eu is suggesting is not the same as mine; disconnect for misbehaving.

I'm pretty sure this is going to have dire consequences for the network, because it means that anyone with their client below block 1120000 - either one that hasn't been started for at least a few days, or one that is syncing from scratch - will never get past block 1119999.

Let me repeat that again. New clients that are at block 1119999 or lower will never be able to proceed onto the correct chain.

[MinersPoolEU]

New clients trying to sync calculate retarget using KGW from block 1120000 and onwards, but krugercoin.miners-pool.eu has already calculated that block and added it to their chain using the old algo. So the local client will say hang on, the difficulty retarget that krugercoin.miners-pool.eu is suggesting is not the same as mine; disconnect for misbehaving.

You're right! The block 1120000 is on old algo, even miners-pool blockchain is broken! (1120000 was definitely not a good setting)
I shut down pool on miners-pool.eu, blockchain is broken, we have to wait a new version with checkpoints.

[UniMatrixZ]

That was not good , 2 days mining probably for nothing 
Well well back to mine something else.
Hope it will get solved quickly.

[carloss]

So these pools, including krugercoin.miners-pool.eu are using deprecated version and they are all on wrong chain? Correct?

[almightyruler]

New clients trying to sync calculate retarget using KGW from block 1120000 and onwards, but krugercoin.miners-pool.eu has already calculated that block and added it to their chain using the old algo. So the local client will say hang on, the difficulty retarget that krugercoin.miners-pool.eu is suggesting is not the same as mine; disconnect for misbehaving.

You're right! The block 1120000 is on old algo, even miners-pool blockchain is broken! (1120000 was definitely not a good setting)
I shut down pool on miners-pool.eu, blockchain is broken, we have to wait a new version with checkpoints.

I don't think you need to shut down your pool, so long as everyone (or at least the dev) accepts the miners-pool.eu blockchain as the de facto official chain.

There is a workaround I can think of:

1. Use the old client to sync, which should get to block 1121075 (when miners-pool.eu upgraded). If you're lucky it will stall here... if unlucky, it will pick up another chain.

2. Change to new client and it should sync completely.

Releasing a new version of the client that only activates KGW past block 1121075 should achieve the same thing.

This needs to be done ASAP.

[carloss]

Now I see I am already on block 1120097, so it seems I got past that barrier 1119999. This is with the recent client.

Code:

carloss@r9miner:~$ ~/krugercoins/src/krugercoind getinfo
{
    "version" : 70005,
    "protocolversion" : 60001,
    "walletversion" : 60000,
    "balance" : 288.00000000,
    "blocks" : 1120097,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 0.00024414,
    "testnet" : false,
    "keypoololdest" : 1394451663,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""
}

[Nibiru]

New clients trying to sync calculate retarget using KGW from block 1120000 and onwards, but krugercoin.miners-pool.eu has already calculated that block and added it to their chain using the old algo. So the local client will say hang on, the difficulty retarget that krugercoin.miners-pool.eu is suggesting is not the same as mine; disconnect for misbehaving.

You're right! The block 1120000 is on old algo, even miners-pool blockchain is broken! (1120000 was definitely not a good setting)
I shut down pool on miners-pool.eu, blockchain is broken, we have to wait a new version with checkpoints.

I don't think you need to shut down your pool, so long as everyone (or at least the dev) accepts the miners-pool.eu blockchain as the de facto official chain.

There is a workaround I can think of:

1. Use the old client to sync, which should get to block 1121075 (when miners-pool.eu upgraded). If you're lucky it will stall here... if unlucky, it will pick up another chain.

2. Change to new client and it should sync completely.

Releasing a new version of the client that only activates KGW past block 1121075 should achieve the same thing.

This needs to be done ASAP.

I have done a run with the old wallet and got over the block -- then ran new wallet and things seems to working now !