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

[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..

[bitsire]

I just heard of this and now I'm scanning all my old wallets digging for clams. What a fun concept!

[Zer0Sum]

I just heard of this and now I'm scanning all my old wallets digging for clams. What a fun concept!

That's not even the interesting part.

There's a shortage of new scrypt coins and a glut of overpriced scrypt ASICs...
If they attract some serious hashing power Clams will rock.

[rkfig]

Deleted everything and started over in case I just screwed up somehow. Still telling me the password is incorrect, but I have double verified that it is the correct one in the original dogecoin wallet. Ideas?

[dooglus]

Deleted everything and started over in case I just screwed up somehow. Still telling me the password is incorrect, but I have double verified that it is the correct one in the original dogecoin wallet. Ideas?

I had no trouble working with encrypted wallets. I just did a 'clamd walletpassphrase $pass 3600' then a 'clamd dumpprivkey $addr' to get the unencrypted private key. Then I could import the private key into my main clam wallet.

By the way, I'm new to proof of stake "mining".

Does it do any kind of brute-force search to mine blocks? I see stuff about a "target" and see it using a fair bit of CPU.

Also, I mined block 31337, bitches.

[maccd123]

multibit copy over does not work for me although i have plenty of transactions in MAY in Bitcoin , much more than in my BTC wallet ( which did credit 4.6)

have tried


importwallet multibit.key

and

importPrivkey xxxxxxxxxxxxx ( taken from multibit logs)

NO Coins

anyone have success with multibit wallet?

any help would be appreciated

Q

Dont copy over Clam wallet.dat........ import .key to Clam wallet-qt file....type importPrivkey xxxxxxxxxxxxx  to debug option.

[rkfig]

Deleted everything and started over in case I just screwed up somehow. Still telling me the password is incorrect, but I have double verified that it is the correct one in the original dogecoin wallet. Ideas?

I had no trouble working with encrypted wallets. I just did a 'clamd walletpassphrase $pass 3600' then a 'clamd dumpprivkey $addr' to get the unencrypted private key. Then I could import the private key into my main clam wallet.

By the way, I'm new to proof of stake "mining".

Does it do any kind of brute-force search to mine blocks? I see stuff about a "target" and see it using a fair bit of CPU.

Also, I mined block 31337, bitches.

Gives an error that the passphrase is incorrect. Exact same command on the original dogecoin wallet works perfectly however. Thanks for trying though.

[SuperClam]

Dooglas and about a dozen other folks:


It has been a crazy weekend for us; with the giveaway at Poloniex (thank you again Polo), attempting to finalize update #1, and continuing work on update #2.

There are about 3 pages of posts I have been intending to respond to - I haven't forgotten (and am not ignoring) you folks.

The refrigerator is empty and I have an opportunity to do a little grocery shopping while the other half watches the troop of children.

I intend to thoroughly pick through all of the posts when I get back in a few hours.


Thank you to everyone who has been involved in this ride with us -> Great things to come, and much work ahead

Cheers!

SuperCLAM.

[SuperClam]

how did you generate the chain ? you said you would post the script .

We have been hammering away at new development and haven't had a chance to get the scripts ready to be released yet, sorry triplef.

The process was simply to download the chains, use open source tools to parse out addresses with a balance, identify outputs/addresses that a balance below "dust" and remove them, then get it all together into a list of sendMany's.

Not all that complicated or difficult, but a pain none-the-less.

[SuperClam]

Watch my video for windows users on the first page for more help!!

I never properly thanked you -> I am sure a lot of people have been helped by your video already, and the contribution the CLAMS community is greatly appreciated

You should head on over to the Sub-Reddit and post the video, in case someone runs into us over there!

CLAMS Sub-Reddit

[SuperClam]

Sorry if this was asked before(I may have over looked it) Does the multipool have any plans on adding x11/13/15/(whatever # that comes out next week)?

Indeed, there have been plans to add additional Algorithms, including SHA256 as well others.

If the pool sees more interest in the coming days, we are definitely planning on putting some time into expanding and improving it.

At the present, the next change will likely be the addition of more Stats.  Because the pool uses Pearl Payouts, our first priority is to get the per miner percentage of total hash contribution which payouts are based off of

Speaking of which, a payout should be kiting it's way out to miners soon!

[SuperClam]

Does my Doge wallet need to be up to date?(17 weeks...) I have my Litecoin wallet fully updated, and that one worked.

Whether or not your DOGE/LTC/BTC client is sync'd or up to date does not matter what-so-ever.

The only thing that matters in claiming CLAMS is that the wallet had a balance mid-May when the distribution was sent.