Topic: Let's add up the KNOWN lost bitcoins - page 18. (Read 65669 times)

18,907.12000001
+      1.12
18,908.24000001

don't ask.

Surprisingly, it's now been recovered!
http://forum.bitcoin.org/index.php?topic=18371.msg342784#msg342784

19,272.30000001
-   365.18000000
----------------
18,907.12000001

Another 365.18 gone forever...  http://forum.bitcoin.org/index.php?topic=18371.msg232955#msg232955

18,907.12000001
+  365.18000000
----------------
19,272.30000001

18,907.12000001
+               0.02
--------------------
18,907.14000001

Looks like the new wallet encryption feature has caused coins to enter the void:
http://forum.bitcoin.org/index.php?topic=8728.msg203511#msg203511


18,838.32000001
        3.79000000
      10.00000000
      55.00000000
+     0.01000000
--------------------
18,907.12000001

As per the above story: 

18,838.31000000
+      0.01000001
-----------------
18,838.32000001

wow, u r generous

In block 124724, I deliberately and specifically underpaid myself by 0.00000001 ฿, which is colloquially known as "1 Satoshi" after ฿'s creator and due to a lack of a good name for that amount of ฿ money.

To make absolutely sure that I was doing it on purpose, I set the reward value to 49.99999999, which meant that I inadvertently threw away the transaction fees which I could have allocated to myself.

I did it as a tribute to our missing Satoshi: we are missing Satoshi, and now the blockchain is missing 1 Satoshi too, for all time.

Before this, the total *awarded* ฿ would have been (assuming my calculations are correct):

฿20999999.97690000

Now, since I underpaid myself, the total *awarded* ฿ can only be:

฿20999999.97689999

--assuming everyone else pays themselves the maximum until the end of time.

So, this is a provably missing amount of the fees+1 Satoshi from the blockchain, from block 124724, which appears to be 0.01 + 0.00000001 ฿.

I did this by creating an option in my heavily customized client (derived from the git fork of bitcoind) which allows me to arbitrarily suspend the normal block reward calculation and underpay myself. The code itself only checks to ensure that I haven't *overpaid* myself. It doesn't at all care that I've *underpaid* myself.

I view this as a freedom in the protocol, and not a drawback.

blockexplorer.com has a display bug for that block which has not been corrected yet.

+ Robert's 4 that he didn't calculate in to the number. 

18,834.31
+      4.00
----------
18,838.31

18,814.31
+0,020.00
----------
18,834.31

Lost it accidentally from a disk crash..

I just lost about 4 btc on my broken hard drive... thank goodness most of my btc was NOT stored on that hard drive. I'm saving the hard drive, just in case this is one day worth thousands, and I'll be able to justify some data recovery thing.

Another huge loss of 7208 BTC:  http://forum.bitcoin.org/index.php?topic=11104.0

11,606.31
+7,208.00
----------
18,814.31

-----------
11,406.22
      50.00+
        0.09+
    150.00+
-------------
11,606.31

(top two are from the post above, my friend threw away his 150 btc, just cause he thought it was stupid and useless xD)

My friend forgot his password, I think he lost at least 30.

I lost about 0.09.

I leave 0.01 btc in various wallets here and there

I may forget about one at some point.

May have deleted .01 off an aws ec2, and one when deleting a local vm.

If you previously had 1% of the supply, you now have 1.00054% (210,000 / (21,000,000 - 11,406.22) * 100)%

If you previously had 0.9994568% of the supply, congratulations, you now have 1%

Lost blocks aren't truly lost. They are just not counted. Using a duplicate transaction hash in the generation transaction, though, WILL make them disappear.

11,456.22
-     50.00
-----------
11,406.22

here again, u have to know the block # ur lookin for.

It's only like 50,000 blocks back.  OCD hath its privileges.

His loss was pretty easy to find.  There aren't many transactions like it.  Finding one specific .01 transaction would be a lot harder.  You'd have to look at something else that you know, like one of the addresses, or the transaction ID.

You can also skip blocks by typing www.blockexplorer.com/b/[BLOCK#]