This is good to know, thanks! I'll try it again and report back.

OK, fair enough. I reformat Windows partitions on sight, so I'm unable to try it for myself. I'm glad you found something that works, anyway.

Did your client get back on the right fork pretty quickly when you fixed the clock and restarted it?

http://khashier.com/ shows the right fork, btw.

EXCHANGE CLAMS for BTC or BTC for CLAMS HERE!

PM me what you can offer (BTC/CLAM or CLAM/BTC) and we can arrange a deal

Certainly, as long as you can access the private keys you and import into clams.  I don't use electrum, but I'll take a look into the process for you.

Tha access to a mac for the dev team has been the issue with the OSX release. None of us are mac users, and given the nature of the coin were not comfortable endorsing a community compiled version.  Once the current release is finished, which I'm working very hard on getting ready I had planned on looking at the build system.

We use gitian builder to compile the client so to provide a deterministic way that other people can verify nothing fishy is going on.  The new build system will allow us to compile the osx client in the same manner, cross compiling through gitian.

There is sadly no real ETA, but it is first on my list once the current release is done.

So basically I have to give up my private keys in order to use CLAM? I haven't quite understood that yet.

It should be safe, how?

I'm not doubting CLAM. probably someone already probed their code and found nothing malicious... But having to give your private keys isn't really a good thing.

Nevertheless, I'll try this with old addresses when my wallet finishes syncing

loving this coin now

it reopened just-dice

So, like I mentioned, if you don't trust the client, then the solution is to move your coins to a new address/wallet, and then you can import your private keys from the time of the snapshot and there is nothing to worry about. I myself have been too lazy to do this up to this point, but I'm planning to do it soon.