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

[SpeedDemon13]

Got zero balance of CLAM with the BTC wallet.dat. Guess I'm unlucky...lol I do have a balance on my BTC wallet, but the wallet is encrypted.

[Apostle4444]

Got zero balance of CLAM with the BTC wallet.dat. Guess I'm unlucky...lol I do have a balance on my BTC wallet, but the wallet is encrypted.

Doesn't matter as long as it was active and had a balance before May.

[FFrost]

Isn't this all a bit untrustworthy since we have to import our wallet.dat into the wallet and trust that you don't steal our keys. Surely this is another pump and dump?

[yampi]

Isn't this all a bit untrustworthy since we have to import our wallet.dat into the wallet and trust that you don't steal our keys. Surely this is another pump and dump?

Transfer your funds to another wallet and never use the wallet you are going to import to CLAM ever again.

[dooglus]

Indeed, coins involved in, and created by, a coinStake transaction/block do not show up in getbalance until they have reconfirmed.

Is there some way I can get a list of all the addresses which have unspent coins?

I can use "listunspent" but it doesn't show the ones that have been involved in staking recently, not even if I use "listunspent 0". I'm guessing I need hundreds of confirmations before I can use those coins again - but I'd like to get a list of the addresses with funds so I can export their privkeys and import them into my main wallet.

Will have to check into the double dash; I would have swore the double dash was required but it wouldn't be the first FUBAR I had made.

I've checked. I was surprised the double-dash worked, but it did. And so did the single dash.

By the way, thankful to see a member with some clout involved in CLAMS.
You are always welcome.

Anyone who wants to give me free money will generally get my attention.

[ghostman9559]

I had a (very small) balance on my Doge wallet, and had 25 transactions all during February. My wallet however was stuck on a fork so I tried to resolve it by downloading the latest wallet, and eventually re-downloading the whole chain. The wallet has just updated though I've tried everything I could think of to get it working, and am at a loss unless I needed transactions past February as well. I changed the previous .dat over to the new doge wallet, updated it, copy/paste to the clam wallet, and still no clams to be found...

[dooglus]

Sorry, but I am not handing over my private keys. This looks like a risky precedent. You should have thought of some way for the owners to prove they had the required wallet private key by generating a public key, or sequence of public keys, or sending dust or similar. Any protocol that requires the private keys is suspect.

You don't need to hand over your private keys, any more than you hand over your private keys when you run bitcoin-qt.

Your private keys are used to sign transactions, the same way as they are in Bitcoin.

The difference here is that all private keys which had non-dust balances on some date in May this year were sent 4 clams.

[dooglus]

Also, I forgot to mention.

Although the -salvagewallet flag did work, and did end up giving me some clams, while it was running the debug.log was spewing out lots and lots of messages like this:

Code:

******* exception encountered *******
/path/to/clamd[0x53a75c]
/path/to/clamd[0x422647]
/path/to/clamd[0x47e127]
/path/to/clamd[0x49e975]
/path/to/clamd[0x480011]
/path/to/clamd[0x4a4678]
/path/to/clamd[0x5658fb]
/path/to/clamd[0x56713d]
/path/to/clamd[0x53fe93]
/path/to/clamd[0x4500f3]
/path/to/clamd[0x4529b9]
/path/to/clamd[0x41839a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f406b3bbec5]
/path/to/clamd[0x41d88b]


******* exception encountered *******
/path/to/clamd[0x53a75c]
/path/to/clamd[0x422647]
/path/to/clamd[0x47e127]
/path/to/clamd[0x49e975]
/path/to/clamd[0x480011]
/path/to/clamd[0x4a4678]
/path/to/clamd[0x5658fb]
/path/to/clamd[0x56713d]
/path/to/clamd[0x53fe93]
/path/to/clamd[0x4500f3]
/path/to/clamd[0x4529b9]
/path/to/clamd[0x41839a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f406b3bbec5]
/path/to/clamd[0x41d88b]


******* exception encountered *******
/path/to/clamd[0x53a75c]
/path/to/clamd[0x422647]
/path/to/clamd[0x47e127]
/path/to/clamd[0x49e975]
/path/to/clamd[0x480011]
/path/to/clamd[0x4a4678]
/path/to/clamd[0x5658fb]
/path/to/clamd[0x56713d]
/path/to/clamd[0x53fe93]
/path/to/clamd[0x4500f3]
/path/to/clamd[0x4529b9]
/path/to/clamd[0x41839a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f406b3bbec5]
/path/to/clamd[0x41d88b]

[ghostman9559]

So I'm guessing the reason why I didn't get any clams is that my wallet was forked, and therefor could not be verified, or sent clams regardless of me being eligible for them.

[kbroadfoot]

Well, I got 1 order of clams with an old wallet, neat stuff 

[garthkiser]

Here's a short article I wrote about CLAMS, my new favorite cryptocurrency. Read it then prepare for all the copycats by spreading dust to 100's of bitcoin accounts

http://www.blockchange.info/altcoins/digging-for-clams/

[istvandv]

might I suggest an official IRC channel for Clams

[dooglus]

Also, I forgot to mention.

Although the -salvagewallet flag did work, and did end up giving me some clams, while it was running the debug.log was spewing out lots and lots of messages like this:

I just tried again on another wallet.

This time clamd exited when it had finished doing the -salvagewallet:

Code:

******* exception encountered *******
/home/chris/Programs/clams/src/clamd[0x53a75c]
/home/chris/Programs/clams/src/clamd[0x422647]
/home/chris/Programs/clams/src/clamd[0x426e48]
/home/chris/Programs/clams/src/clamd[0x563543]
/home/chris/Programs/clams/src/clamd[0x5655a5]
/home/chris/Programs/clams/src/clamd[0x567c57]
/home/chris/Programs/clams/src/clamd[0x44e7a4]
/home/chris/Programs/clams/src/clamd[0x4529b9]
/home/chris/Programs/clams/src/clamd[0x41839a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fc217f1bec5]
/home/chris/Programs/clams/src/clamd[0x41d88b]
Flush(false)
DBFlush(false) ended               0ms
StopNode()
Flushed 0 addresses to peers.dat  60ms
Flush(true)
DBFlush(true) ended               0ms
Clam exited

I deleted the wallet.dat, copied the same wallet back in, tried again, and the same thing happened.

I think previously it carried on running when the -salvagewallet was done.

[almightyruler]

Here's a short article I wrote about CLAMS, my new favorite cryptocurrency. Read it then prepare for all the copycats by spreading dust to 100's of bitcoin accounts

Short term solution for the coming copycat coins is to ignore blocks past early May 2014, that way people won't be rewarded for trying to pre-emptively game any new clones.

Whether the copycat devs are smart enough to figure this out remains to be seen.

[Parana]

Great idea.

Testing as soon as I arrive home.

 

[Matt9301]

Why my clams are in stake, but not in spendable balance??

[rkfig]

Close to emptied my dogecoin wallet, followed steps in OP, showing 23.0272787 clam in the clam wallet, but I am unable to unlock the clam wallet or send. I have verified through the dogecoin wallet that I am using the right password. Any ideas?

[dooglus]

Why my clams are in stake, but not in spendable balance??

It seems like you have to wait for 510 confirmations after "staking your coins before they are spendable again.

At 1 confirmation per minute, that corresponds to around 8.5 hours.

[dooglus]

I noticed a couple more things about Clams:

1) The clams github repository is a fork of blackcoin and so has no issue tracker of its own; that leaves me nowhere to submit bug reports without bothering the blackcoin people.

2) I experimented with importing various wallets. I found that simply using -rescan instead of -salvagewallet found more funded private keys in almost every case. There's something very wrong with -salvagewallet - so much so that not using it is almost always better than using it.

[Matt9301]

Why my clams are in stake, but not in spendable balance??

It seems like you have to wait for 510 confirmations after "staking your coins before they are spendable again.

At 1 confirmation per minute, that corresponds to around 8.5 hours.

But are confirmed in the transaction list, there are 29413 confirms..