Unique coin... and the name is terrific.

You have to overwrite the clam wallet with your, for example, a copy of your LTC wallet...
And then, from the command line, run "clam-qt --salvagewallet".

The LTC wallet COPY is processed, backed-up, and a new clam wallet is created...
Almost always containing 4.6 clams worth about $1.00...
So I wouldn't touch my BTC wallet for a few pennies...

But, who knows, stranger coins have caught on... and been pumped to da moon.

-----------------------------------------------------------------------

And within an hour I got an "interest earned" payout of 0.14% on my 4.6 clameroos. What is this?

The Bitcoin, Litecoin, and Dogecoin block chains are not referenced in real time.  There is no interaction between the different chains.  The Bitcoin, Litecoin, and Dogecoin block chains were dumped and processed shortly before launch and the CLAM distribution was frozen in time at that time.  So, the process of taking multiple "outputs" of CLAMS and accruing them into a single key would essentially opt-out an exchange from receiving CLAMS for the vast majority of their "outputs".  Indeed, in our conversation with Poloniex (who seem to responsibly handle their user's funds), their share of CLAMS was significantly smaller than would have been the case had they not combined outputs.  Thankfully for their users, they did still receive a small share of CLAMS - which they intend to distribute out to their users.

Very impressed with the honesty and character of Poloniex for this reason alone. They are the first and only exchange to do so.

Any transaction NOW, will not affect your share of CLAMS what-so-ever, as the block chain analysis on Bitcoin, Litecoin, and Dogecoin is frozen in time.  This is why, moving your Bitcoin, Litecoin, or Dogecoin to a separate wallet will not make you lose your distribution of CLAMS: it is only transaction gathering multiple "outputs" into a single wallet BEFORE the distribution and launch of CLAMS that would negatively affect your share.

---

Thanks for the How-To!  That is essentially the process, yes

Concerning the "girls":
If there are any gals out there who would like to help promote CLAMS, we are happy to help!
The one gal on our Dev team is just not the mascot-gal type  

---

Hope I am translating properly:

We launched CLAMS with whisper a bit ago.  Unfortunately, CLAMS is a horse-before-the-cart type of situation.  You see: when a user clams their CLAMS they are essentially minting the initial moneySupply.  This means that Users(Demand)==CLAMS(Supply).  We hope that this will aid CLAMS in maintaining a bit more of a balanced price-point at market - that was the hope anyways.  It also, however, means that CLAMS is an extremely small distribution crypto at the moment.  This makes it very difficult to push large volume.  However, with volume comes more users, and with more users comes more volume.... I think you get the point.

We are moving slowly and steadily, and as a development team: are still working hard on CLAMS.

---

Thank you very much for the vote of confidence, everyone
Indeed, the referenced code change is not a risk what-so-ever to your Bitcoin, Litecoin, or Dogecoin.

Awhile ago, a moderator on bitcointalk.org added a big red warning at the top of this announcement post.

We promptly requested (in a big green "everything is okay" message below it) that if anyone could point out a place in the code that made CLAMS capable of stealing anyone's coins - we would promptly DELETE CLAMS entirely.

To the moderator's credit, the warning was removed (Thank you, by the way).

I think the fact that no one has taken us up on that offer should be evidence enough for those who are concerned.

---

Phew!  
Still a couple more posts to respond to -> have some other social things to take care of; will be back in a bit to finish up responding.
Thank you everyone for being involved!

I keep getting the error "Warning: error reading wallet.dat! All keys read correctly, but transactiondata or address book entries might be missing or incorrect." I just copied the BTC wallet.dat into the CLAM folder in C:\Users\Mobile User\AppData\Roaming\Clam. I get the same error pasting the DOGE wallet.dat.

Do I need to rename the BTC wallet.dat or do I need to extract the privkeys?

Guys, I think it is easy to exploit this wallet. I haven't tested it but I will soon. My post got deleted that told you how. The dev does not want to face this fact. Perhaps he is using the exploit to get clams for himself to later sell.

My simple mistake, I misspelled "salvage" and put "salavage" instead...LOL....Got it....Thanks

So, this only works with BTC, LTC or DOGE? Or can others work too?

There is DRK and VRC that have high volume.

Hello and good luck with project, got my Clams and still have my BTC for the people that do not think it is safe. You can also transfer Btc to an exchange and make a new wallet just to be safe. Also with the --slavagewallet, easy to make a .bat file in the same folder where the clam-qt.exe is and put  clam-qt.exe --slavagewallet inside the bat file. Am also mining at the pool and would like to see information on my miner. Thanks and good luck.

so when I put the wallet.dat from bitcoin or ltc  to this location  "C:/Users/<YOUR_USERNAME>/AppData/Roaming/Clam/" folder.
there will be 2 wallet.dat file in the folder???
because when i run the clam qt it will generate wallet.dat  and plus I will add wallet.dat from ltc or btc