[ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin"

[ElectronicFerocious]

If that's you, fix your clock!

Sorry!

Fixed

From IRC:

16:46 < dooglus> you can probably find ntp for windows to keep your clock right
16:47 < dooglus> see http://www.satsignal.eu/ntp/setup.html
16:51 < ElectronicFeroc> this is perfect, thanks

Did you use that? Did it fix the problem? Was it easy? Etc.

Feedback would probably help others who have trouble stopping their clock drifting.

I tried that one initially but after inputting some ntp servers I was still over 20 seconds off from time.gov after a reboot.. and I couldn't really tell if it was running.

Now i'm using NetTime sync tool from here: http://www.timesynctool.com

Works like a charm. Will sync your clock every x minutes/hours/days. I'm using the minimum 15 minute interval and it runs in the system tray so you can tell its working. (i'm always within 1 or 2 seconds from time.gov now)  Recommended

[1714207089]

1714207089

[1714207089]

1714207089

[1714207089]

1714207089

[dooglus]

I tried that one initially but after inputting some ntp servers I was still over 20 seconds off from time.gov after a reboot.. and I couldn't really tell if it was running.

Now i'm using NetTime sync tool from here: http://www.timesynctool.com

Works like a charm. Will sync your clock every x minutes/hours/days. I'm using the minimum 15 minute interval and it runs in the system tray so you can tell its working. (i'm always within 1 or 2 seconds from time.gov now)  Recommended

ntp takes up to an hour to start doing its thing, but then works very well.

Your clock appears to lose about 2 seconds per minute. So in a 15 minute interval you'll lose 30 seconds, which it enough to harm your chances of successfully staking.

ntp is meant to figure out how much your clock loses, and then speed it up to compensate, so it's always right. That's better than having 15 minutes of drift followed by a sudden correction.

[ElectronicFerocious]

ntp takes up to an hour to start doing its thing, but then works very well.

Your clock appears to lose about 2 seconds per minute. So in a 15 minute interval you'll lose 30 seconds, which it enough to harm your chances of successfully staking.

ntp is meant to figure out how much your clock loses, and then speed it up to compensate, so it's always right. That's better than having 15 minutes of drift followed by a sudden correction.

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

[ElectronicFerocious]

Ok, still no luck with that link, even after an hour the clock continues to drift.

Since i'm running windows Server 2008 i followed the instructions here http://support.microsoft.com/kb/816042

Now set to sync every 60 seconds

[dooglus]

Ok, still no luck with that link, even after an hour the clock continues to drift.

Since i'm running windows Server 2008 i followed the instructions here http://support.microsoft.com/kb/816042

Now set to sync every 60 seconds

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.

[ElectronicFerocious]

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.

Yep, it did immediately. Here's a screenshot showing the tail end of my inadvertent 'attack' fork before restarting the client at 13:30 on Dec 2. No orphans since getting serious about fixing the clock drift issues: http://imgur.com/x3ahsJh

Thank you dooglus, creativecuriosity and xploited for your infinite patience on IRC   

[marcotheminer]

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

[russianptr]

i use electrum for BTC and therefore have no wallet.dat ...

how can I import my electrum wallet to look for CLAMs ?

[xploited]

i use electrum for BTC and therefore have no wallet.dat ...

how can I import my electrum wallet to look for CLAMs ?

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.

[galbros]

The new website looks great!

What is the status of the wallet for OS X?

This reddit post suggests a Mac wallet would be out months ago but I don't see one listed.  Is this still on the agenda?  Thanks!

Getting dooglus to repoen just-dice with CLAMS was a real coup for the coin.  Congrats!

[xploited]

The new website looks great!

What is the status of the wallet for OS X?

This reddit post suggests a Mac wallet would be out months ago but I don't see one listed.  Is this still on the agenda?  Thanks!

Getting dooglus to repoen just-dice with CLAMS was a real coup for the coin.  Congrats!

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.

[inkha]

claams.com to convert CLAMs to BTC using the latest price from the exchange.

[unamis76]

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

[jwinterm]

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

You have to import your private key (that held coins at the time of the snapshot) into the CLAMs wallet. I haven't done this yet, but from what I understand it should be safe, however, best practice would be to transfer your btc/ltc/doge to a new wallet, and then you can import your private keys with no fear of anything fishy (clammy?) going on, since all your coins are in a different wallet.

[unamis76]

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

You have to import your private key (that held coins at the time of the snapshot) into the CLAMs wallet. I haven't done this yet, but from what I understand it should be safe, however, best practice would be to transfer your btc/ltc/doge to a new wallet, and then you can import your private keys with no fear of anything fishy (clammy?) going on, since all your coins are in a different wallet.

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

[chilly2k]

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

   Just to be sure you understand.  You do NOT have to give up your private keys to USE clams.  It's just a regular old alt coin as far as usage goes.

You DO have to provide your private keys in order to DIG any clams.  This is the processes you use to claim your clams from the initial distribution.   

[Joca97]

loving this coin now

it reopened just-dice

[unamis76]

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

   Just to be sure you understand.  You do NOT have to give up your private keys to USE clams.  It's just a regular old alt coin as far as usage goes.

You DO have to provide your private keys in order to DIG any clams.  This is the processes you use to claim your clams from the initial distribution.   

Yes, I understood that. The problems remains: private keys have to be used.

[jwinterm]

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

   Just to be sure you understand.  You do NOT have to give up your private keys to USE clams.  It's just a regular old alt coin as far as usage goes.

You DO have to provide your private keys in order to DIG any clams.  This is the processes you use to claim your clams from the initial distribution.   

Yes, I understood that. The problems remains: private keys have to be used.

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.

[xploited]

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

   Just to be sure you understand.  You do NOT have to give up your private keys to USE clams.  It's just a regular old alt coin as far as usage goes.

You DO have to provide your private keys in order to DIG any clams.  This is the processes you use to claim your clams from the initial distribution.   

Yes, I understood that. The problems remains: private keys have to be used.

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.

This is the approach we suggest everyone takes to be 100% safe.

I didn't do it with my addresses where I wrote the code for this and I'm 100% confident its safe but moving your BTC/LTC or DOGE to a different address before you import takes the risk to 0.