Quote from: Turpomann on April 18, 2014, 06:38:48 AM

Thanks. I've used peerblock for many years. If I remember correctly some aircoin pools are blacklisted by peerblock.
At least Okaypool was/is and maybe airpool.org was too. Can't remember anymore.

edit: With your suggested nodes, I seem to still have the same problem with synching. "0 hours remaining" and "Processed 43471 of 551316 remaining". Maybe I should try to synch the wallet again from the beginning.

edit2: Did not work! I'm not going to touch my wallet again until teamaircoin sort this "fork" out of the way.

Though it says you are not synched, you are... those nodes are not sending the block-data, they can't, they are invalid blocks.

You have to look at the first number... "43474", if that matches the block-chain, then you are synched, and can mine without issues.

Seems that another coin is using the same rooms as AIRcoin, for broadcasting. AIR should be rejecting them, for version mismatch, as I told them they needed to do before. However, until whatever coin, or hacked-program, stops broadcasting in the AIRcoin rooms, this will continue. (This can happen if you clone a coin, and don't designate a "private IRC channel for broadcasting, with a seed-confirmed password, or encrypted output"... if this is not a purposeful attack.)

The subversions are waaaay off... and old, so I assume this is not the AIR teams "new coin". Easy to block with a new update that just rejects subversion "/Satoshi:*/", since the only valid subversion is "/Satoshi2:*/"

Should not be difficult to find the culprit coin, as we know the block-height for the bad coin is "551325"
(Pssst, It is LTC)

Could be a check-point issue... did they turn-on auto checkpoints, but forget to tell it to generate checkpoints for AIR, so it made one for LTC instead?