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:
addnode:kdc.criptoe.com
Like I said, it might not work, but it eliminates the variable.
-Fuse