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

[whywefight]

Hi
Can someone help me please.
How do I claim CLAM from my blockchain wallet?

Thanks

Yes, this guide will help. You can export your keys from Blockchain.info and then import them into the CLAMclient: http://bitcoin.stackexchange.com/questions/17318/migrate-from-blockchain-info-to-bitcoin-qt
As always it is recommended that you remove any BTC from that account before claiming your CLAMs.

If you would like more help then stop into the CLAMs IRC channel at: http://webchat.freenode.net/?channels=clams

Long Live the Great CLAM

Thanks for the help 
I go through all this and all i got is Invalid private key (code -5) 

same here!?

[xploited]

Hi
Can someone help me please.
How do I claim CLAM from my blockchain wallet?

Thanks

Yes, this guide will help. You can export your keys from Blockchain.info and then import them into the CLAMclient: http://bitcoin.stackexchange.com/questions/17318/migrate-from-blockchain-info-to-bitcoin-qt
As always it is recommended that you remove any BTC from that account before claiming your CLAMs.

If you would like more help then stop into the CLAMs IRC channel at: http://webchat.freenode.net/?channels=clams

Long Live the Great CLAM

Thanks for the help 
I go through all this and all i got is Invalid private key (code -5) 

same here!?

Theres a known issue with importing a BTC/DOGE or LTC key into the client using  importprivkey, it will be fixed in the next release. It was missed, but the influx of new users digging clams from sources other then wallet.dat files made it clear. 

The issue will be resolved in the next client release. Until then, just-dice.com's dig command will work.

[whywefight]

it looks like importing the whole doge wallet.dat via file works, having ids now

[xploited]

it looks like importing the whole doge wallet.dat via file works, having ids now

Yes, there are no issues with importing the wallet.dat file directly.  Only individual private keys.

[garthkiser]

Thanks.

How many addresses have not been digged up?
How BTC the address needed to have on May 14th 2014 not be considered a "dust address"?

Total supply of distributed CLAMs is 14,897,662
Only 224,553 were in circulation as of Nov 27, 2014
So you can do the math, that's alot of unclaimed CLAMs.

"Dust" Amounts:
DOGE:  0.01
LTC:    0.00001
BTC:    0.00001

[goozman96]

So how do I uncover my private keys if my wallet is already encrypted?

[garthkiser]

So how do I uncover my private keys if my wallet is already encrypted?

You can unlock the wallet for a specified number of seconds by entering this into the console:
walletpassphrase <passphrase> <number of seconds to unlock>

Then enter into the console: dumpprivkey <address>

[jd1959]

Only 31votes for CLAMS on https://www.cryptsy.com/coinvotes?

You don't want CLAMS on Cryptsy they stake your coins and make it almost impossible to withdraw anything but tiny amounts. I stopped trading there because of this very issue. Once bitten ...never twice

Jon  

[VTC]

Since the claim on clams is a fixed amount per btc address that had a balance in May, and not weighted to the balance in the address, doesn't this make the distribution skewed towards people that hold multiple address?

It's my understanding this was done to prevent large btc holders from have a lot of clams, but with a fixed claim per address this gives an unfair advantage to owners of services or exchanges that have a large amount of address.

Also, anyone with insider knowledge of when snapshot will take place could have divided say 5 btc into 50,000 address containing .0001 btc for less than .2 btc in fees total, then claim 230,000 clams.

[goozman96]

So how do I uncover my private keys if my wallet is already encrypted?

You can unlock the wallet for a specified number of seconds by entering this into the console:
walletpassphrase <passphrase> <number of seconds to unlock>

Then enter into the console: dumpprivkey <address>

Thank you good sir. I shall try this.

[goozman96]

To clarify, can I send the coins to another address in my wallet? Would that be safe? Since I won't be digging up the private key for that address. Right?

[Aggressor66]

Hi
Can someone help me please.
How do I claim CLAM from my blockchain wallet?

Thanks

Yes, this guide will help. You can export your keys from Blockchain.info and then import them into the CLAMclient: http://bitcoin.stackexchange.com/questions/17318/migrate-from-blockchain-info-to-bitcoin-qt
As always it is recommended that you remove any BTC from that account before claiming your CLAMs.

If you would like more help then stop into the CLAMs IRC channel at: http://webchat.freenode.net/?channels=clams

Long Live the Great CLAM

Thanks for the help 
I go through all this and all i got is Invalid private key (code -5) 

same here!?

Theres a known issue with importing a BTC/DOGE or LTC key into the client using  importprivkey, it will be fixed in the next release. It was missed, but the influx of new users digging clams from sources other then wallet.dat files made it clear. 

The issue will be resolved in the next client release. Until then, just-dice.com's dig command will work.

Thanks xploited 

[BayAreaCoins]

I'm now accepting CLAM for silver orders:

https://bitcointalk.org/index.php?topic=841485.msg9783804#msg9783804

[dooglus]

To clarify, can I send the coins to another address in my wallet? Would that be safe? Since I won't be digging up the private key for that address. Right?

There are two cases:

* If you plan to import the wallet.dat into the CLAM client, you should move your coins to a new WALLET first. The wallet.dat you import includes the next 100 addresses that wallet will generate, so when you think you're making a new address, you really aren't.

* If you plan to import just individual private keys into JD's /dig command, then there's no need to make a new wallet, just more the coins to a different ADDRESS.

[goozman96]

To clarify, can I send the coins to another address in my wallet? Would that be safe? Since I won't be digging up the private key for that address. Right?

There are two cases:

* If you plan to import the wallet.dat into the CLAM client, you should move your coins to a new WALLET first. The wallet.dat you import includes the next 100 addresses that wallet will generate, so when you think you're making a new address, you really aren't.

* If you plan to import just individual private keys into JD's /dig command, then there's no need to make a new wallet, just more the coins to a different ADDRESS.

The second option is what I did. Thank you for your help. I dug up ~18 clams.

[BayAreaCoins]

Sponge bob knew it!

[ranlo]

If anyone reads this that has the knowledge of how all of this actually works, please correct me if I'm wrong:

The coins in the initial distribution were sent to public addresses, accessible to the private keys. So what this means is that it doesn't matter if you claim them now or a year from now, they will still be accessible (basically, we have the coins already, we just haven't imported our address yet -- so it's like cold storage), correct?

[BayAreaCoins]

Has anyone posted in the Litecoin forums or the Dogecoin forums?

[dooglus]

If anyone reads this that has the knowledge of how all of this actually works, please correct me if I'm wrong:

The coins in the initial distribution were sent to public addresses, accessible to the private keys. So what this means is that it doesn't matter if you claim them now or a year from now, they will still be accessible (basically, we have the coins already, we just haven't imported our address yet -- so it's like cold storage), correct?

Exactly.

Except it's not like cold storage if your BTC (or whatever) wallet is online - because anyone stealing your BTC keys also gets your CLAM.

Notice that the distribution method has a funny side effect for the (very few) people who used the same private key on all three coins: they get three sets of 4.6 CLAM at their address.

For example:

All four of these addresses have the same private key. I don't know what it is, but it's the same:

   BTC: http://blockchain.info/address/1s9VR8ofhyTrTfRKTReckvUwQWmsBVjU4
  DOGE: http://dogechain.info/address/D61F2g5Sy7skPTr243RDAX65pYF5GFrYm6
   LTC: http://block-explorer.com/address/LL66kdSdkNDX7GMaVbQwtmzF9ct3zUy3Hf
  CLAM: http://khashier.com/address/x9AnPHyGwRTVtqmHfw4K3wDGAWp1FwDoTv

All three of BTC, DOGE, and LTC were funded on 12th May 2014 (the snapshot date) and so the CLAM address got 3 sets of 4.6 CLAMs.

Edit: I was wondering why anyone would use the same private key for three different coins. My best guess is that it's a "brain wallet" and the private key is the sha256 hash of a passphrase or something.

[ranlo]

If anyone reads this that has the knowledge of how all of this actually works, please correct me if I'm wrong:

The coins in the initial distribution were sent to public addresses, accessible to the private keys. So what this means is that it doesn't matter if you claim them now or a year from now, they will still be accessible (basically, we have the coins already, we just haven't imported our address yet -- so it's like cold storage), correct?

Exactly.

Except it's not like cold storage if your BTC (or whatever) wallet is online - because anyone stealing your BTC keys also gets your CLAM.

Notice that the distribution method has a funny side effect for the (very few) people who used the same private key on all three coins: they get three sets of 4.6 CLAM at their address.

For example:

All four of these addresses have the same private key. I don't know what it is, but it's the same:

   BTC: http://blockchain.info/address/1s9VR8ofhyTrTfRKTReckvUwQWmsBVjU4
  DOGE: http://dogechain.info/address/D61F2g5Sy7skPTr243RDAX65pYF5GFrYm6
   LTC: http://block-explorer.com/address/LL66kdSdkNDX7GMaVbQwtmzF9ct3zUy3Hf
  CLAM: http://khashier.com/address/x9AnPHyGwRTVtqmHfw4K3wDGAWp1FwDoTv

All three of BTC, DOGE, and LTC were funded on 12th May 2014 (the snapshot date) and so the CLAM address got 3 sets of 4.6 CLAMs.

Edit: I was wondering why anyone would use the same private key for three different coins. My best guess is that it's a "brain wallet" and the private key is the sha256 hash of a passphrase or something.

Very interesting! And thanks for the clarification, .

Now I just need to get things organized/cleaned up so I can deal with claiming CLAMs!