Quote from: mycointr on February 09, 2014, 08:13:19 PM

Quote from: wzttide on February 09, 2014, 08:07:52 PM

Quote from: mycointr on February 09, 2014, 08:03:57 PM

Quote from: tf2honeybadger on February 09, 2014, 07:53:47 PM

Quote from: mycointr on February 09, 2014, 07:49:07 PM

also i think right behaviour is deleting chain at all nodes only leave s4w3d0ff 's
nodes need to re download chain from s4w3d0ff.
or this broken chain issue will continue.
also wallet must contain only s4w3d0ff 's node hardcoded.
so things will get fixed..

This is essentially what the new client will do. Everyone's local copy of the blockchain will be wiped, and the client will redownload from known good nodes. Additionally, the new client will reject any connection to the current or previous client to prevent the evil fork monster from spreading to the new client. This is an extreme measure, and it will require EVERYONE to update to continue using CGA.

problem is 'there aren't known good nodes'
anomalypools nodes chain is different than s4w3d0ff 's.
It's forking, your node is forking too.
My suggestion is getting s4w3d0ff 's node 'good', every other is bad atm.

EDIT : I know anomalypools chain is different because of my 2 coins..

anomalypool's chain is the only one with hashpower, sawedoff's node didn't have any. And is down. So his chain is broken anyway.

We can't build a coin on a node which is down.

@awesomeperson451: We have a list of all "old" nodes, checking your finding against it now, thanks!

problem is: your pool has 0 latency to your node.
all blocks found by pools-people other than your pool are not accepted by your node i think.

There will be 5 nodes hardcoded.

make a ping to node1.cga.anomalypool.com and then make a ping to anomalypool.com, these are 2 different IP addresses, in fact they are 2 different physical machines.

node1.cga.anomalypool.com will be hardcoded, NOT anomalypool.com