Stouse49, thanks for sending me the wallet. I did manage to find 160 private keys by using a simple program to hunt for magic bytes in the wallet file directly. Many of the recovered keys report an error on importing to the GLX client. I can't be sure that I did the base58 encoding 100% correctly for GLX (I had to hack pycoin to support GLX specs) but the keys that were successfully imported do have the same sequence of raw bytes in the new wallet as they do in the original wallet. It's possible the 'error' keys are simply corrupt, but it's also possible that the encoding I hacked in is completely wrong.
There were 103 keys successfully imported, but a rescan doesn't match any of them against a transaction.
It could just be an empty wallet with a pool of keys that were never used, or it could be that the base58 import format isn't quite correct ('close enough' isn't going to work.)
Could also be that the wallet is truncated (it is less than a default wallet size of 128k) or corrupt, and it originally held more valid+used private keys...
I know this post is from 2 years ago, but I just had another go at recovering funds from the Cryptsy wallet.
This time my recovery efforts considered the entire wallet.dat file to be a byte stream full of keys - my system doesn't care about file formats, magic numbers, indexes, metadata, whatever; just whether each 32 bytes of raw data can be mapped to an address that's in the blockchain.
Again... zero matches. It seems the keys/addresses in this wallet have never been referenced in the Galaxycoin blockchain. So it's either an empty wallet that was created but never used, or perhaps a wallet from another coin.
FYI, there are 91584 different addresses present in the Galaxycoin blockchain.
