Bitcoin Forum
November 11, 2024, 02:12:48 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 15 16 17 18 19 20 »  All
  Print  
Author Topic: Let's add up the KNOWN lost bitcoins  (Read 65656 times)
unclemantis
Member
**
Offline Offline

Activity: 98
Merit: 10


(:firstbits => "1mantis")


View Profile
August 19, 2012, 07:55:53 PM
 #121

38669.33589602
Hello!

I noticed that this thread is lacking Stefan Thomas's great loss of 7000 BTC. With this included, the new total is:

45669.33589602

I'll come clean too, I got into this when CPU mining was the way (0.2 client).   I don't want to go into details be here is the damage:

27,000 BTC


New Total:  BTC72,669.33589602

OMG I feel for you. Must suck knowing that you threw away at CEILING Half a million dollars Sad

Here... You may use my vomit bucket. Just please don't jump off a building!

PHP, Ruby, Rails, ASP, JavaScript, SQL
20+ years experience w/ Internet Technologies
Bitcoin OTC | GPG Public Key                                                                               thoughts?
Dalkore
Legendary
*
Offline Offline

Activity: 1330
Merit: 1026


Mining since 2010 & Hosting since 2012


View Profile WWW
August 19, 2012, 07:59:47 PM
 #122

38669.33589602
Hello!

I noticed that this thread is lacking Stefan Thomas's great loss of 7000 BTC. With this included, the new total is:

45669.33589602

I'll come clean too, I got into this when CPU mining was the way (0.2 client).   I don't want to go into details be here is the damage:

27,000 BTC


New Total:  BTC72,669.33589602

OMG I feel for you. Must suck knowing that you threw away at CEILING Half a million dollars Sad

Here... You may use my vomit bucket. Just please don't jump off a building!

Nah, I am good.  First thing I did was do a forensic data scan on the drive to look for fragments.  I only found 5BTC literally.   What it told me is that Bitcoin was getting serious and I told myself I am going to make a second go at it.    BTC were worth .002 USD at the time so I didn't pay much attention.   

Hosting: Low as $60.00 per KW - Link
Transaction List: jayson3 +5 - ColdHardMetal +3 - Nolo +2 - CoinHoarder +1 - Elxiliath +1 - tymm0 +1 - Johnniewalker +1 - Oscer +1 - Davidj411 +1 - BitCoiner2012 +1 - dstruct2k +1 - Philj +1 - camolist +1 - exahash +1 - Littleshop +1 - Severian +1 - DebitMe +1 - lepenguin +1 - StringTheory +1 - amagimetals +1 - jcoin200 +1 - serp +1 - klintay +1 - -droid- +1 - FlutterPie +1
SgtSpike (OP)
Legendary
*
Offline Offline

Activity: 1400
Merit: 1005



View Profile
August 20, 2012, 10:19:36 PM
 #123

38669.33589602
Hello!

I noticed that this thread is lacking Stefan Thomas's great loss of 7000 BTC. With this included, the new total is:

45669.33589602

I'll come clean too, I got into this when CPU mining was the way (0.2 client).   I don't want to go into details be here is the damage:

27,000 BTC


New Total:  BTC72,669.33589602

OMG I feel for you. Must suck knowing that you threw away at CEILING Half a million dollars Sad

Here... You may use my vomit bucket. Just please don't jump off a building!

Nah, I am good.  First thing I did was do a forensic data scan on the drive to look for fragments.  I only found 5BTC literally.   What it told me is that Bitcoin was getting serious and I told myself I am going to make a second go at it.    BTC were worth .002 USD at the time so I didn't pay much attention.   
I'll buy that drive from you... well, if you haven't used it since then.  Cheesy
unclemantis
Member
**
Offline Offline

Activity: 98
Merit: 10


(:firstbits => "1mantis")


View Profile
August 21, 2012, 01:00:35 AM
 #124

38669.33589602
Hello!

I noticed that this thread is lacking Stefan Thomas's great loss of 7000 BTC. With this included, the new total is:

45669.33589602

I'll come clean too, I got into this when CPU mining was the way (0.2 client).   I don't want to go into details be here is the damage:

27,000 BTC


New Total:  BTC72,669.33589602

OMG I feel for you. Must suck knowing that you threw away at CEILING Half a million dollars Sad

Here... You may use my vomit bucket. Just please don't jump off a building!

Nah, I am good.  First thing I did was do a forensic data scan on the drive to look for fragments.  I only found 5BTC literally.   What it told me is that Bitcoin was getting serious and I told myself I am going to make a second go at it.    BTC were worth .002 USD at the time so I didn't pay much attention.   
I'll buy that drive from you... well, if you haven't used it since then.  Cheesy

I'll place a bid on that drive too.

SgtSpike you bid first.

PHP, Ruby, Rails, ASP, JavaScript, SQL
20+ years experience w/ Internet Technologies
Bitcoin OTC | GPG Public Key                                                                               thoughts?
jl2012
Legendary
*
Offline Offline

Activity: 1792
Merit: 1111


View Profile
January 27, 2013, 04:15:04 PM
 #125

Based on this thread and other sources, I have complied a list of all known loss: https://docs.google.com/a/ij.hk/spreadsheet/ccc?key=0Ahdy3Je_nYdOdFVocm4yTzhZOW1waWd6SFJIVHUwYUE#gid=0

Events are included if coins are recoverable only with blockchain hard-fork, burst-forcing of private key, or exploiting flaws in bitcoin protocol (including hash algorithms and public key encryption). The following events are excluded:
  • Thefts which the coins are spendable by the thief
  • Loss of password to a service, where the service provider holds the private key
  • Sending coins to a wrong address, unless evidence shows that private key of the address is unknown to anyone
  • Without basic information, e.g. "I lose coins but do not want to explain"

Events are classified into 5 major categories:
  • Unverifiable claim: an user claimed he/she lost bitcoin without showing related transaction/address. The amount could be an estimation. The user may have recovered the coins without telling the forum.
  • Suspicious claim: an unverifiable claim without a matching event on the blockchain.
  • Verifiable claim: transaction id / address is known. If it is spent in the future, it will be removed from the list.
  • Permanent loss: usually for output with an unspendable script. It is not recoverable without a hard fork.
  • Address with unknown private key: the address is created without knowing the private key. It is recoverable only with brust-forcing or exploiting flaws in bitcoin protocol
Amounts are exact except for unverifiable claims.

Amount of lost coins:
  • Total confirmed loss = permanent loss + unknown private key: 2,731.84195637
  • Total unverifiable claimed loss: 59,465.76900000
  • Total verifiable claimed loss: 9,006.66100000
  • Total loss: 71,204.27195637
  • Total suspicious claims: 7,208.00000000
  • Total loss minus suspicious claims: 63,996.27195637

I am sure there are cases missing. Please help me to complete the list!

If you like this list, please give some tips to 1CiZPrEJdN4FJcqdLdgVLzT8tgCXxT5ion . Thank you!

Donation address: 374iXxS4BuqFHsEwwxUuH3nvJ69Y7Hqur3 (Bitcoin ONLY)
LRDGENPLYrcTRssGoZrsCT1hngaH3BVkM4 (LTC)
PGP: D3CC 1772 8600 5BB8 FF67 3294 C524 2A1A B393 6517
SgtSpike (OP)
Legendary
*
Offline Offline

Activity: 1400
Merit: 1005



View Profile
January 28, 2013, 04:18:14 PM
 #126

Nicely done jl2012!
mb300sd
Legendary
*
Offline Offline

Activity: 1260
Merit: 1000

Drunk Posts


View Profile WWW
February 06, 2013, 07:10:19 AM
 #127

You can also add the unspendable bitcoins in transactions such as these.

http://blockexplorer.com/tx/81f591582b436c5b129f347fe7e681afd6811417973c4a4f83b18e92a9d130fd
http://blockexplorer.com/tx/111291fcf8ab84803d42ec59cb4eaceadd661185242a1e8f4b7e49b79ecbe5f3
http://blockexplorer.com/tx/ddddf9f04b4c1d4e1185cacf5cf302f3d11dee5d74f71721d741fbb507062e9e
http://blockexplorer.com/tx/305fbc2ec7f7f2bc5a21d2dfb01a5fc52ab5d064a7278e2ecbab0d2a27b8c392
http://blockexplorer.com/tx/aa62bdd690de061a6fbbd88420f7a7aa574ba86da4fe82edc27e2263f8743988

Theres quite a few of them if you look through strange transactions.

1D7FJWRzeKa4SLmTznd3JpeNU13L1ErEco
jl2012
Legendary
*
Offline Offline

Activity: 1792
Merit: 1111


View Profile
February 06, 2013, 07:54:50 AM
 #128


These are the well-known mtgox loss and already included.

Donation address: 374iXxS4BuqFHsEwwxUuH3nvJ69Y7Hqur3 (Bitcoin ONLY)
LRDGENPLYrcTRssGoZrsCT1hngaH3BVkM4 (LTC)
PGP: D3CC 1772 8600 5BB8 FF67 3294 C524 2A1A B393 6517
jerfelix
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile
February 06, 2013, 08:15:07 AM
 #129

You have a spectrum of losses here, ranging from definitely lost to possibly lost.  You are starting to cross into the territory where you can take some educated guesses at "possibly lost".

Not to totally derail this thread, but there was a thread last week that talked about the fact that the most popular amounts held in a Bitcoin Address are 1 satoshi and 50 BTC.  If I recall correctly, there were 2 Million BTC held in Bitcoin Addresses with 50 BTC.  Since 50 BTC almost certainly means that it was a mined coin with no transaction fees, then these must have been in the early days.

This would definitely be something I would have done... hear about Bitcoin, download the client with the built-in miner.  Run it for a few days, generate 50 Bitcoins, decide that was a worthless project and move on to the next idea.  I'm sure other people did that back in early 2009 too.  I would bet that the vast majority of 50 BTC accounts that are the result of CPU-based mining with no transaction fees are lost.

I would bet that 15-20% of coins are lost permanently.
dserrano5
Legendary
*
Offline Offline

Activity: 1974
Merit: 1029



View Profile
February 06, 2013, 07:11:40 PM
 #130

That might be why the limit is 21 millions. Satoshi would expect 1 million coins to get lost, so the remaining coins in circulation would make a nice round number. Just saying.
sublime5447
Legendary
*
Offline Offline

Activity: 966
Merit: 1000



View Profile
February 07, 2013, 01:17:40 AM
 #131

I have 5 coins stuck on a hard drive. I cleaned out the computer with compressed air and it quit working. I was told that the drive is good just the motherboard was bad.
knight22
Legendary
*
Offline Offline

Activity: 1372
Merit: 1000


--------------->¿?


View Profile
February 07, 2013, 01:26:20 AM
 #132

I have just lost 1 btc by sending it to a wrong instawallet address...   Sad

payb.tc
Hero Member
*****
Offline Offline

Activity: 812
Merit: 1000



View Profile
February 07, 2013, 01:27:49 AM
 #133

I have just lost 1 btc by sending it to a wrong instawallet address...   Sad

instawallet's owners have control of that wallet, so that coin is not lost.

sucks for you though.
sublime5447
Legendary
*
Offline Offline

Activity: 966
Merit: 1000



View Profile
February 07, 2013, 01:30:03 AM
 #134

I forgot but I also sent a coin to a wallet that cant be accessed. The customer sent a address that they couldnt get to. I lost the coin and they charged back. So I have 5 stuck on a hard drive and 1 that I believe cant be recovered.  
SgtSpike (OP)
Legendary
*
Offline Offline

Activity: 1400
Merit: 1005



View Profile
February 07, 2013, 02:51:04 AM
 #135

I forgot but I also sent a coin to a wallet that cant be accessed. The customer sent a address that they couldnt get to. I lost the coin and they charged back. So I have 5 stuck on a hard drive and 1 that I believe cant be recovered.  
Well, the 5 on the hard drive can be recovered so we cannot add to the list.  The 1, however, can be added.  Use the format as designated in the beginning of this thread to add it...!
jl2012
Legendary
*
Offline Offline

Activity: 1792
Merit: 1111


View Profile
February 07, 2013, 04:03:49 AM
 #136

I forgot but I also sent a coin to a wallet that cant be accessed. The customer sent a address that they couldnt get to. I lost the coin and they charged back. So I have 5 stuck on a hard drive and 1 that I believe cant be recovered.  
Well, the 5 on the hard drive can be recovered so we cannot add to the list.  The 1, however, can be added.  Use the format as designated in the beginning of this thread to add it...!

No, "The customer sent a address that they couldnt get to" does not mean no one could get to that address.

Donation address: 374iXxS4BuqFHsEwwxUuH3nvJ69Y7Hqur3 (Bitcoin ONLY)
LRDGENPLYrcTRssGoZrsCT1hngaH3BVkM4 (LTC)
PGP: D3CC 1772 8600 5BB8 FF67 3294 C524 2A1A B393 6517
payb.tc
Hero Member
*****
Offline Offline

Activity: 812
Merit: 1000



View Profile
February 07, 2013, 04:07:16 AM
 #137

No, "The customer sent a address that they couldnt get to" does not mean no one could get to that address.

yeah that actually could be in exactly the same category as the above "instawallet user couldn't get to coins, but instawallet owners can".
jl2012
Legendary
*
Offline Offline

Activity: 1792
Merit: 1111


View Profile
February 07, 2013, 04:10:54 AM
 #138

That might be why the limit is 21 millions. Satoshi would expect 1 million coins to get lost, so the remaining coins in circulation would make a nice round number. Just saying.

That's because on average we have 210384 blocks in every 4 years, and rounding up to 210000.

Donation address: 374iXxS4BuqFHsEwwxUuH3nvJ69Y7Hqur3 (Bitcoin ONLY)
LRDGENPLYrcTRssGoZrsCT1hngaH3BVkM4 (LTC)
PGP: D3CC 1772 8600 5BB8 FF67 3294 C524 2A1A B393 6517
SgtSpike (OP)
Legendary
*
Offline Offline

Activity: 1400
Merit: 1005



View Profile
February 07, 2013, 04:39:32 AM
 #139

No, "The customer sent a address that they couldnt get to" does not mean no one could get to that address.

yeah that actually could be in exactly the same category as the above "instawallet user couldn't get to coins, but instawallet owners can".

Ah, good point.  It could be someone else's legitimate address.  We'd need clarification from sublime on tha.
Doctor Mushies
Newbie
*
Offline Offline

Activity: 42
Merit: 0


View Profile
February 07, 2013, 04:58:54 AM
 #140

Could it be possible to send coins to an unused address, so that someone gets a surprise when they generate a new address? hmm...
Pages: « 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 15 16 17 18 19 20 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!