Author

Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 482. (Read 1151252 times)

full member
Activity: 223
Merit: 100
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.
legendary
Activity: 2940
Merit: 1333
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. Smiley
newbie
Activity: 11
Merit: 0
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?
legendary
Activity: 1588
Merit: 1000
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.
full member
Activity: 223
Merit: 100
I just heard of this and now I'm scanning all my old wallets digging for clams. What a fun concept!
legendary
Activity: 1596
Merit: 1009
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..
legendary
Activity: 2940
Merit: 1333
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.
legendary
Activity: 2940
Merit: 1333
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.
newbie
Activity: 11
Merit: 0
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?
legendary
Activity: 1596
Merit: 1009
Why my clams are in stake, but not in spendable balance??
sr. member
Activity: 378
Merit: 250
Step into a world!! A P2P world!
Great idea.

Testing as soon as I arrive home.

 Wink
legendary
Activity: 2268
Merit: 1092
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 Smiley

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.
legendary
Activity: 2940
Merit: 1333
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.
sr. member
Activity: 342
Merit: 250
might I suggest an official IRC channel for Clams
full member
Activity: 176
Merit: 100
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 Smiley

http://www.blockchange.info/altcoins/digging-for-clams/
legendary
Activity: 1302
Merit: 1000
Bass Player
Well, I got 1 order of clams with an old wallet, neat stuff  Smiley
newbie
Activity: 34
Merit: 0
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. Sad
legendary
Activity: 2940
Merit: 1333
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]
legendary
Activity: 2940
Merit: 1333
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.
newbie
Activity: 34
Merit: 0
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...
Jump to: