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

Is it named 'bootstrap.dat' and you restarted the wallet?

It should work that way but still take some time.

More the better

<3

Do I have to do anything on a win machine to get it to read the bootstrap file?
I've tried it twice now - with the file in the clams admin folder and nothing...

It looks like the files in contrib/gitian-descriptors/ are reasonably up to date, but I can't be sure. (They have identical timestamps so it's possible that reflects more when they were 'touched', say, for a release, rather than showing when they were actually last modified)

Gitian allows you to cross-compile a release on your own machine, running inside a Linux VM, that will spit out a binary that should be 100% identical to the official release executable.

Perhaps a couple of respected participants could compile their own clamd.exe, to confirm that the official release was built straight from the same source that is available to the public. (I can do that, but I'm not sure I'd be considered respected. )

I would bet that Picolo = Zolace.

He farms BTCT accounts for a living

The knee-jerk reaction is to respond to such claims with disappointment or anger.

However, I think it is wise to have the discussion; and important that users understand why it is recommended that private keys are retired before claiming.

Private keys have value because they are capable of signing transactions verifying ownership of pubic keys.
Once they have been "retired" and emptied, they can no longer sign these transactions and their only value is for use in claiming.

A private key is no more valuable than any random string of characters; without the associated capability of signing a transaction.
It doesn't matter if you are claiming via Just-Dice, a different third-party, or the CLAM client itself: it only takes one transaction to empty the address before import - take responsibility for your own security and take the time to do so.

---

This is an important concept for everyone to understand in general, on the CLAM network or otherwise.

• Back-up your wallet files/keys.
• Encrypt your wallet files/keys when possible.
• Be responsible and aware of how the system that protects your funds operates.

---

We take steps to ensure the executables we distribute are safe (the reason for much of the delay with the OSX build).
Other parties and other development teams may not be so careful or well-meaning.

---

Picolo:

Remove your tin-foil hat.  
There isn't - and never has been - any mechanism in our software for your private keys to leave your personal computer system.

This may be difficult for you to understand, but there is no "back-up plan" or grand conspiracy.
Leave that non-sense on youtube.

It would be possible for the devs to modify the CLAM client so that it uploaded all the private keys it was given somewhere.

If they did, it would be possible to detect it, but whether anyone would actually detect it isn't clear.

Lots of people presumably download the .exe version of the client and don't check that it was built from the published sources.

Anyway, it's a moot point so long as you make sure you retire your old Bitcoin addresses before giving them to the CLAM client, as is recommended practice.

I had an argument with someone saying the devs could have all the priv keys that people imported and if CLAM doesn't succeed, they have a back-up plan to use them.

It's worth repeating that you should move any Bitcoin from that address before claiming the CLAM.

The /dig command described above sends your private key to Just-Dice, and so in theory Just-Dice could steal any BTC at that address.

It won't, but it's better to be safe than sorry. And if your blockchain.info wallet gets hacked I don't want you thinking that it was JD that did it!

So please only use /dig with privatekeys that you have already "retired".

Edit: I see you modified your post to include that warning in bold at the end while I was making this post. Thanks!

here we go:

i already have claim my blockchain info

= go to import wallet on blockchain info, choose unencrypted and bitcoin qt format
= copy only priv key
= claim to justdice on chat tab and type this : /dig youraddr yourprivkey
= done

before check if your addr have some clam

type : /dig youraddr

After claim or before you should empty your wallet balance and never used it again, cause your priv key is on the way

No, you don't need to download any of the blockchain to import a private key.

But you won't see your free 4.6 CLAMs until you have downloaded the block that awarded them to you.

The awards started in block 558 and ended in block 9262.

To claim, no; only up to block 10k.

To stake, yes; though you can use dooglus' bootstrap file to speed up the process greatly.

Will I need to download the whole blockchain first?

Thanks that helped me a lot!

I can't get into my blockchain.info wallet any more, but there's some way of exporting your private keys from it.

Find the export page, export your address in 'bitcoin' or 'wif' format. You're looking for a string that looks like:
  5K5cMk7ahCjnerzVptpVPMTmj72YrPpc56V4LKHEf3RbV2d94o3

Then in the CLAM client go to the debug console and:
  importprivkey 5K5cMk7ahCjnerzVptpVPMTmj72YrPpc56V4LKHEf3RbV2d94o3

That should be all. It will take a few minutes to scan the blockchain for coins after you run the importprivkey command, and the wallet will probably appear to be frozen. Just wait.

It wouldn't be horrible to disconnect v1.4.5 clients too - v1.4.5 has a bug that causes it to fail to receive any incoming connections if you're behind a NAT router, even if you do set up the port forwarding.

Maybe we could use the 'alert' system to let users of old versions know that they should upgrade.

I hope you do ban the version and/or behavior too,  just would make sense.  I hope people would then upgrade.
Maybe banning the behavior would still allow v1.4.5 versions to exist..  whereas banning version would eliminate v1.4.5 clients too if they are reporting wrong?

3)I have no proof
4)Dev can have unclaimed clam, there are 15 millions of those.
5)To be seen
6)I still like CLAM

Well spoken, though I would argue #2 isn't quite accurate.  BAC is selling silver and snails for CLAM; garth's sweetie is selling hand-made satchels for CLAM; there is an individual selling poker chips for CLAM; you can donate to Sean's Outpost with CLAM; and there is at least one other service (FortuneJack) accepting CLAM on deposit for gambling, though others have advertised in the thread and elsewhere and we have yet to hear enough users claiming positive interaction to list them in the OP.

If someone offered CLAM to any number of people involved in crypto, in return for their services, they might accept it - even if only intending to convert it immediately into another crypto.

Great?  No.
Improving? Yes.

1) True
2) True - But this is 100% more use then most alt coins. 
3) False - This is straight up FUD.
4) False - There are only 500K Clams.  Your claiming the developers hold over 40% of the clams.  Another FUD Claim. 
5) I think False. 
   Currently 291K Clams have been dug.  That's 1.9% of the potential available clams.  Clams have been around about 9 months.  We need to dig another 1.7 million clams for your claim to be true.  The dig rate increase as the price increases, so maybe, if 1 Clam = 1 BTC, then we will see over 2 million clams dug. 
What was your time frame for this claim? in the next month, year, or infinity...