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

[NickCrypto]

Great Chart Gallery of Clams on BitScreener: https://bitscreener.com/coins/clams/chart_gallery

[BurtW]

I am an idiot.  Again.  Questions for you, dear reader:  Did you take my CLAM?  Would you kindly return them?

Previously I lost 25 CLAM when they got swept from xWAS3PbHr3FBdLsV1s8UYKuwXaJWMsTcjw.

Yesterday I lost another 25 CLAM when they got swept from xXWEQ27z4etYknwN9ZHd8M5YtwcfBY5njR.

My only hope is that the person sweeping my coins is a "white hat" and they give them back.  I also mention these embarrassing episodes so that others can learn from my stupidity.

Here is how I shot myself in the foot:

1  A long time ago when I first got into CLAM I was testing the client by importing random private keys I found on the internet into my wallet.
2  I knew that if I found a private key that had coins on it at the time of the airdrop I would get the free CLAM into my wallet.
3  I incorrectly assumed that if a private key did NOT have any coins at the time of the airdrop then the client would do nothing.
4  This is wrong.  Any time you import a private key you create a key pair in your wallet.  This makes sense to me now.
5  Since I imported well know private keys into my wallet this created little "time bombs" in my receive address list.
6  At some point I transferred CLAM on to these "time bomb" addresses.
7  Someone out there did the same thing I did, imported the same private keys, and they were able to sweep my coins.

Check out the private key for xXWEQ27z4etYknwN9ZHd8M5YtwcfBY5njR.  It is obvious without any further research this is a very bad private key to use:

dumpprivkey xXWEQ27z4etYknwN9ZHd8M5YtwcfBY5njR
Lg7s3TveHSrHbpmAZ5Vmt9an6nim2f4gekrLRR5bJeJe81XuHc8z

Private Key Hexadecimal Format (64 characters [0-9A-F]):
00000000000000000000000000000000000000000000000000000000000068F3

Private Key Base64 (44 characters):
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaPM=

Derp.

[almightyruler]

5  Since I imported well know private keys into my wallet this created little "time bombs" in my receive key list.
6  At some point I transferred CLAM on to these "time bomb" addresses.

? Why did you reuse addresses, particularly ones that you didn't originally create?

[BurtW]

5  Since I imported well know private keys into my wallet this created little "time bombs" in my receive key list.
6  At some point I transferred CLAM on to these "time bomb" addresses.

? Why did you reuse addresses, particularly ones that you didn't originally create?

When you import a private key and the private key did not contain any coins at the time of the airdrop then the CLAM address generated by the private key import appears in your receive address list just like any other empty unused receive CLAM address.  AFAIK there is no easy way, from the GUI, to see if a receive address in the list is an address generated by the program or is an address generated from a private key import.

Since they look exactly the same from the GUI, I received CLAM on to an address I thought/assumed was an address generated by the program.

I so not reuse address.  I sent CLAM to what I thought was a new/unused/empty address.

QUESTION:  Is there a way using the console to see if a CLAM receive address was generated by the program from a random private key generated by the program OR if it was generated from a private key import?

[inashed]

Are all coins created at the start or new coins will be created at the future (so people wont mine only transaction fees)

[Timetwister]

Are all coins created at the start or new coins will be created at the future (so people wont mine only transaction fees)

1 new CLAM is created per block (1 block per minute)

[almightyruler]

5  Since I imported well know private keys into my wallet this created little "time bombs" in my receive key list.
6  At some point I transferred CLAM on to these "time bomb" addresses.

? Why did you reuse addresses, particularly ones that you didn't originally create?

AFAIK there is no easy way, from the GUI, to see if a receive address in the list is an address generated by the program or is an address generated from a private key import.

Since they look exactly the same from the GUI, I received CLAM on to an address I thought/assumed was an address generated by the program.

[...]

QUESTION:  Is there a way using the console to see if a CLAM receive address was generated by the program from a random private key generated by the program OR if it was generated from a private key import?

I haven't used the CLAM GUI client for some time, so I'm probably used to the way Bitcoin Core works - you "Request Payment" which involves generating a new address (and optionally adding a label, amount, message etc). How does the CLAM client work?

I'm assuming you don't use labels for your addresses, which is why you ended up accidentally (re)using one of the imported ones?

[BurtW]

5  Since I imported well know private keys into my wallet this created little "time bombs" in my receive key list.
6  At some point I transferred CLAM on to these "time bomb" addresses.

? Why did you reuse addresses, particularly ones that you didn't originally create?

AFAIK there is no easy way, from the GUI, to see if a receive address in the list is an address generated by the program or is an address generated from a private key import.

Since they look exactly the same from the GUI, I received CLAM on to an address I thought/assumed was an address generated by the program.

[...]

QUESTION:  Is there a way using the console to see if a CLAM receive address was generated by the program from a random private key generated by the program OR if it was generated from a private key import?

I haven't used the CLAM GUI client for some time, so I'm probably used to the way Bitcoin Core works - you "Request Payment" which involves generating a new address (and optionally adding a label, amount, message etc). How does the CLAM client work?

I'm assuming you don't use labels for your addresses, which is why you ended up accidentally (re)using one of the imported ones?

No, I did not put a label on it because I did not know it was not an automatically generated address.

The way the GUI works is you go to the Receive tab and there is a list of addresses there.  You pick one, label it, and then use it.  That is just what I did.  But, as stated above, some of the addresses there were generated when I imported bogus private keys.  I used the Receive tab the way it was intended.  The thing I did wrong was to import bogus private keys with no coins at the time of the airdrop - so they looked just like any other address that is generated by the client.

[inashed]

Are all coins created at the start or new coins will be created at the future (so people wont mine only transaction fees)

1 new CLAM is created per block (1 block per minute)

Thanks, I got excited expecting a premined coin without ico, thats is not the case, here.

[BayAreaCoins]

Are all coins created at the start or new coins will be created at the future (so people wont mine only transaction fees)

1 new CLAM is created per block (1 block per minute)

Thanks, I got excited expecting a premined coin without ico, thats is not the case, here.

This coin was premined and then those premined coins were gifted to the networks/burned.

No ICO. *gags*

[TheButterZone]

Number of connections 0
Last block time Tue Nov 28 02:30:40 2017
Current number of blocks 1792910

What console command do I use to get fucktarded v1.4.17 synced before all my CLAM gets swept out from under me like BurtW?

[almightyruler]

Number of connections 0
Last block time Tue Nov 28 02:30:40 2017
Current number of blocks 1792910

What console command do I use to get fucktarded v1.4.17 synced before all my CLAM gets swept out from under me like BurtW?

You can send funds without needing to be fully synced - your client only needs to be able to see the transactions that contributed to your balance. Unless you've received any extra funds in the past week you should be fine sending your entire balance, even if not synced, BUT, you do need to be connected to at least one peer to broadcast your transaction... (edit: if you're really stuck, you could copy the raw transaction and ask someone here to broadcast it to the network. The transaction is cryptographically signed with your keys so it cannot be modified by anyone else.)

[BurtW]

Number of connections 0
Last block time Tue Nov 28 02:30:40 2017
Current number of blocks 1792910

What console command do I use to get fucktarded v1.4.17 synced before all my CLAM gets swept out from under me like BurtW?

Unless you imported well known publicly known private keys into your wallet you do not have to worry about your CLAM being swept.  Most people are not as, umm, "creative" as me and they will not have any issues with this.

[TheButterZone]

I imported private keys from someone's peeled BTC coins that they had taken a picture of, uploaded to Imgur, and linked in #bitcoin-otc as a giveaway. Then it looks like 54bc57a62f9df20e160d1f2b70dcad26c3680619019c861a34f701cac7b80bc3 containing all of them & others, was a BTC wallet CLAM dig & cashout (months after I had told them I took the ones on the coins & how they could dig for CLAM with the rest of their BTC). They confirmed today that they'd done a comprehensive CLAM sweep of all wallets since I told them how, and cashed out to BTC.

It's possible whoever took the BTC part of the giveaway also dug the clams & didn't move them right away like I didn't? But it sure feels like an indian gift at this point. I wouldn't have even thought they were diggable anymore, considering the time that had elapsed between their giveaway & the time I read my bouncer scrollback, but because they said one of 'em wouldn't import, I figured it was worth a try to figure out which private key character(s) they had misread. If they had all the peeled privkeys imported to their BTC wallet, then clearly one of them would, and did, import.

A non-fucktarded CLAM client would have always swept private keys to a randomly-generated CLAM keypair & not left anything on the original private keys.

[BurtW]

I imported private keys from someone's peeled coins that they took a picture of, uploaded to Imgur, and linked in #bitcoin-otc as a giveaway. Then they swept their BTC wallet(s) for CLAM digs months later (AFTER I had told them I took the ones on the coins & how they could dig for CLAM with the rest of their BTC), so the ones they had indian-given disappeared from my CLAM wallet.

A non-fucktarded CLAM client would have always swept private keys to a randomly-generated CLAM keypair & not left anything on the original private keys.

Yes, this is basically the same issue I had.  The main thing I am trying to harp on and make sure everyone knows is that after all this happens you probably ended up with these swept CLAM address in your receive address list so LABEL THEM so you never accidentally use them again like I did.

So a client improvement suggestion would be that when importing private keys the client would:

1) sweep the CLAM to a randomly generated internal address.
2) do not put the swept CLAM address in the receive CLAM address list
3) maybe even delete the entire key pair and all references to the swept key pair and address from the client.

[BayAreaCoins]

Number of connections 0
Last block time Tue Nov 28 02:30:40 2017
Current number of blocks 1792910

What console command do I use to get fucktarded v1.4.17 synced before all my CLAM gets swept out from under me like BurtW?

Shouldn't you be able to sweep them with Just-dice.

Go to the "Chat" tab and type /dig

[TheButterZone]

For security, I'd rather use the client that locks up & requires force quit every single time despite having 16 GB of RAM, than a website.

Is there some way to see in the logs which private key you imported corresponds to which address in the Receive tab?

[Wolf Rainer]

A lot of Legendary trusted users following this coin. Why the price is so low?

We are far away from the ATH, only 6% of that. This days a lot of coins are getting a 8/12X pumps, and thats what clams needs. At 200k sats it was already very cheap.

Very low current supply (under 3 milions), very hard to get CLAMS without buying (you need Litecoin or Bitcoins, stacking is just worthless with low amounts).

Solid and "old" coin with active development and community, and one of the coins with the lowers marketcap on poloniex. With the current volume and price it will be very easy for whales and pump groups to take the price several times higher.

[TheButterZone]

Not sure how you read the above posts & not get that it should be nuked from orbit... just to be sure.

[Wolf Rainer]

Not sure how you read the above posts & not get that it should be nuked from orbit... just to be sure.

I dont get why you say that. You loses money?