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!

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.

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

Where can I find the old client?

Seems we may need a whole new wallet.

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:

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.

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

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 !