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:
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
1Nro9WkpaKm9axmcfPVp79dAJU1Gx7VmMZTaking 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.
Show Posts
.
