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

[LeonardoDiCrypto]

You should change the Opening Page graphics, which states "If you own BTCs etc you already own clams". This is not true. I own BTCs, but I don't own any Clams. I find this statement mocking therefore.

How about "If you owned Bitcoin on 2014-05-12 at 12:48:17 (block 300377) then you can claim your CLAMs!"

Sounds more precise

Yes, and it would avoid frustrating people who believe they can claim but they cannot. By the way, I happened to own several Bitcoins in that period, but I didn't manage to claim my CLAMS

[dooglus]

Can someone please help me I am new to clams. I won quite a bit on just-dice.com I went to clamaddress to get an address and private key which is what I used to do with bitcoin and I then import the private key, but when i downloaded the wallet the only option for importing is a wallet.dat file. Can I dump my private key in the wallet and recover my funds? Please help. Thanks

I don't know the GUI client very well, but there's some way to open a debug console. It's on the 'help' menu.

Once you find it, type: importprivkey, then a space, then your private key, and hit return. It will rescan the blockchain, taking maybe 10 minutes.

You don't need to do that to generate an address. The CLAM client can generate its own addresses. Just check the 'receive' tab, or whatever it's called.

[1xhopeless]

Same here. I wanted invest in your project, but now coin really low so I better get rid of it... That's too bad

Nah, you just sound like you dont know what you are talking about. The coin is at $3.41 right now, if you did bother look at the coin price history. That's not low.


Even if it is low as you are saying,  a bright guy will buy not sell. Who sells when the price is low!!??

[disloyalrequests]

do token holders receive percentage of the platform’s income?

[BurtW]

Against all odds I believe I have proof of a private key collision!

It all started when 25 CLAMs just up and left my wallet without my permission.

The transaction is shown here.

Notice that my 25 clams left my address of xWAS3PbHr3FBdLsV1s8UYKuwXaJWMsTcjw and ended up at the new address of x8f8YKkNJk6mU92ZmerhWqwqqvZKnTaZ9Y where, at the time of this post, they sit.

The source address is valid and is mine:

validateaddress xWAS3PbHr3FBdLsV1s8UYKuwXaJWMsTcjw

{
"isvalid" : true,
"address" : "xWAS3PbHr3FBdLsV1s8UYKuwXaJWMsTcjw",
"ismine" : true,
"isscript" : false,
"pubkey" : "02fcba7ecf41bc7e1be4ee122d9d22e3333671eb0a3a87b5cdf099d59874e1940f",
"iscompressed" : true,
"account" : "Stake 43"
}

The new address is valid and is not mine:

validateaddress x8f8YKkNJk6mU92ZmerhWqwqqvZKnTaZ9Y

{
"isvalid" : true,
"address" : "x8f8YKkNJk6mU92ZmerhWqwqqvZKnTaZ9Y",
"ismine" : false
}

Digging into the source address we find that it was originally funded in the airdrop:

Date   In Block   Transaction ID   Sent   Received   Total Minted   Total Change
31 Oct 2017   1753170   e33f67ae6a7c48e47e01ed9e10a6811c7fccd4ffd29ad0875064462079076a76   25.0000 (0.013 BTC)   0.0000 (0.000 BTC)   0.0000 (0.000 BTC)   -25.0000
26 Oct 2017   1745987   29f0acb9a407110f3f669f37457d8db0b3eb5ad4879e64947860172a62175279   0.0000 (0.000 BTC)   25.0000 (0.013 BTC)   0.0000 (0.000 BTC)   25.0000
21 Jan 2015   305965   09d59571fa24ab78c29d06df5f68574997a0990010d1d78978fc4efa24568000   4.6055 (0.002 BTC)   0.0000 (0.000 BTC)   0.0000 (0.000 BTC)   -4.6055
16 May 2014   2091   ccac1b2ef05dd9054ffa8bb814cdc9bfb66df6e9aba826bfde11173036a78bc9   0.0000 (0.000 BTC)   4.6055 (0.002 BTC)   0.0000 (0.000 BTC)   4.6055

This means that the CLAM private key is either a BTC, LTC, or DOGE private key.

FACTS:  I have never owned LTC or DOGE and I only imported BTC private keys into my CLAM client.  The three possible source addresses for the airdrop are:

22:19:55 INFO: CLAM: [xWAS3PbH] has the same private key as: BTC: [1Nro9Wkp], DOGE: [DSztgmhT], and LTC: [Lh5kQj4e]

Remember, I only imported BTC private keys.  Therefore the only key that could have been mine is the private key for the Bitcoin address of 1Nro9WkpaKm9axmcfPVp79dAJU1Gx7VmMZ

Taking a closer look at that address you will see that the first transaction made on that address was on 2015-06-29 20:35:06.  Therefore this could not have been the address used to claim the CLAMS.  Also, I do not recognize this address as one of mine and my first CLAM transaction was on 4/19/2017 so I could not have moved the claimed CLAMs off the address on 2015-01-21 19:42:08!

My conclusion is that this address is an address that was generated by my wallet that collided with all this past activity.

The person that owned the DOGE address DSztgmhTsjfS7xxDPyVNeunmBbjaJMfz92 is the person that claimed the CLAMs and them moved them on 2015-01-21 19:42:08.

My client appears to have generated the same private key!

I expect this person noticed 25 CLAMS magically appear in their wallet and then moved them to another address.

I must have incredible luck - which I hope will someday translates into a win in the lottery

If you owned the DOGE address DSztgmhTsjfS7xxDPyVNeunmBbjaJMfz92, used it to claim CLAMs back in 2015, saw 25 CLAM magically appear in your wallet 2017-10-26 13:35:44, moved them 2017-10-31 14:16:16, and are feeling honest or guilty about it let's talk.

I would love another explanation.  Right now I am out 25 CLAMs.

[nikisev]

It holds around 3.5, which is positive. Still drop was dramatic enough. Any idea what happened? Why sudden selloff?

[BayAreaCoins]

Against all odds I believe I have proof of a private key collision!...

Wow.  It makes me wonder how random this random shit actually is.  

I've found empty a empty address on Directory.io, but for you to have your 25 CLAMS pwned by a DOGE address with 2 Dogecoins... at least you had this happen with 25 CLAMS and not 25 Bitcoins.

I must have incredible luck - which I hope will someday translates into a win in the lottery

Sounds like the opposite of luck to me!

[antaresus]

There are more than 1000000 Clams in this Just-dice.com address xJDCLAMZpJR8odWH3QiwdNwJkwvD6eJwzW, but the address sends only 25-50 Clams for staking. How can I do it in my wallet?

[BurtW]

There are more than 1000000 Clams in this Just-dice.com address xJDCLAMZpJR8odWH3QiwdNwJkwvD6eJwzW, but the address sends only 25-50 Clams for staking. How can I do it in my wallet?

Break it up into 25-50 CLAM "chunks" all on the same address.

[Faust Roland]

There are more than 1000000 Clams in this Just-dice.com address xJDCLAMZpJR8odWH3QiwdNwJkwvD6eJwzW, but the address sends only 25-50 Clams for staking. How can I do it in my wallet?

You can use this command for splitting the amount:

./clamd sendtoaddress $ADDRESS '{"amount":5,"count":200}'
or in gui in console without ./clamd

It takes 5 Clams 200x (i.e. 1000 Clams in total)

[antaresus]

There are more than 1000000 Clams in this Just-dice.com address xJDCLAMZpJR8odWH3QiwdNwJkwvD6eJwzW, but the address sends only 25-50 Clams for staking. How can I do it in my wallet?

Break it up into 25-50 CLAM "chunks" all on the same address.

There are more than 1000000 Clams in this Just-dice.com address xJDCLAMZpJR8odWH3QiwdNwJkwvD6eJwzW, but the address sends only 25-50 Clams for staking. How can I do it in my wallet?

You can use this command for splitting the amount:

./clamd sendtoaddress $ADDRESS '{"amount":5,"count":200}'
or in gui in console without ./clamd

It takes 5 Clams 200x (i.e. 1000 Clams in total)

Thank you.

[Michail1]

Against all odds I believe I have proof of a private key collision!
...
I would love another explanation.  Right now I am out 25 CLAMs.

It's a shame to hear of a loss.
Fortunately for you, it is less than $200.

Anoter explanation?   Your computer could be keylogged/infected.  (Unlikely if only a sub $200 loss).

[BayAreaCoins]

17:19:43 (411) <Ticker> → (1485941) <#BayAreaCoins> CLAM per BTC : 1851.85185185 ... 1618366 CLAM = 873.91764000 BTC ... ::: NEXT PRICE UPDATE IN ::: 112.62 Seconds !

This is how many CLAMS there are left to buy that are outside of Just-Dice invested.  

(Assuming there isn't a whale digger leaking us slowly and stealthily.)

[dooglus]

Against all odds I believe I have proof of a private key collision!

It all started when 25 CLAMs just up and left my wallet without my permission.

[...]

I would love another explanation.  Right now I am out 25 CLAMs.

This is fascinating. Do you still have the BTC wallet that you imported? Was it created by Bitcoin Core? What is the date of the first transaction in the BTC wallet? I'm thinking the wallet could have been created and stolen before the CLAM airdrop. Bitcoin Core back then used to pre-generate 100 addresses when it created a wallet, so that the next 100 addresses it used would be in any backups you made. Could it be that the BTC address was lying dormant in your wallet before the CLAM airdrop?

It's curious that the corresponding DOGE address was funded just 2 days before the airdrop happened. Was the attacker seeding the DOGE chain with a view to later carrying on exactly this kind of attack?

Kind of a personal question, but has the BTC wallet ever held enough coins to make it worth stealing? Have you experienced any such thefts? Are you the same BurtW was in trouble with the alphabet boys a while back? Could they have messed with any of this stuff? How does the timing match up there?

I'd love to get to the bottom of this, but am not very hopeful about it.

It's a shame to hear of a loss.
Fortunately for you, it is less than $200.

Anoter explanation?   Your computer could be keylogged/infected.  (Unlikely if only a sub $200 loss).

While possible, it seems like a weird thing for the attacker to do. Why only steal 25 CLAMs when the wallet contained much more? Why steal them using a very old DOGE private key? It just doesn't seem to add up.

[noeeel]

Hi all, I have not read the thread, buy can you give me a quick note, why the price decreased so drastically a few weeks ago? Was there an event that caused this drop?

[Arya Aditama]

if like this the thread i know some people make that big rank in this forum, because simple explain but make people understand about the project mission and join in this project, very interesting

[BurtW]

Against all odds I believe I have proof of a private key collision!

It all started when 25 CLAMs just up and left my wallet without my permission.

[...]

I would love another explanation.  Right now I am out 25 CLAMs.

This is fascinating. Do you still have the BTC wallet that you imported? Was it created by Bitcoin Core? What is the date of the first transaction in the BTC wallet? I'm thinking the wallet could have been created and stolen before the CLAM airdrop. Bitcoin Core back then used to pre-generate 100 addresses when it created a wallet, so that the next 100 addresses it used would be in any backups you made. Could it be that the BTC address was lying dormant in your wallet before the CLAM airdrop?

It's curious that the corresponding DOGE address was funded just 2 days before the airdrop happened. Was the attacker seeding the DOGE chain with a view to later carrying on exactly this kind of attack?

Kind of a personal question, but has the BTC wallet ever held enough coins to make it worth stealing? Have you experienced any such thefts? Are you the same BurtW was in trouble with the alphabet boys a while back? Could they have messed with any of this stuff? How does the timing match up there?

I'd love to get to the bottom of this, but am not very hopeful about it.

It's a shame to hear of a loss.
Fortunately for you, it is less than $200.

Anoter explanation?   Your computer could be keylogged/infected.  (Unlikely if only a sub $200 loss).

While possible, it seems like a weird thing for the attacker to do. Why only steal 25 CLAMs when the wallet contained much more? Why steal them using a very old DOGE private key? It just doesn't seem to add up.

I am working on a theory that does not involve an address collision and is just me shooting myself in the foot.  There is a new thread about this subject.  If you could answer my question here:

https://bitcointalk.org/index.php?topic=2344004.msg23896718#msg23896718

then I will import your questions above and answer them there, tomorrow morning.

Basically I would like to know if there is any way to differentiate between private keys generated by the wallet and private keys imported into the wallet.  If the private key was generated by the wallet that is one thing and would indicate an actual address collision but if I can prove that I (or someone?) imported the address then, well, that would be interesting.

[kang_kung]

Even though the price drop a bit but I'm still holding it.

[dooglus]

if like this the thread i know some people make that big rank in this forum, because simple explain but make people understand about the project mission and join in this project, very interesting

Congratulations. This is the least intelligible post I have ever read on this forum. Please post a CLAM address within 24 hours to claim your prize.

[Sikkan666]

Hi all, I am able to claim some clams when looking up an old wallet addy, however, that addy is on blockchain.info and All I can do (as far as I know) is to export priv keys. That is somehow going to make me been able to import into clam wallet (which I have no active connection too) and claim it?

I need some guidance

anyone have a working peer-list I can add to the conf file so the wallet syncs? And how do I import my private keys? Is that even possible?

Best regards