public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Chris Riley <criley@gmail•com>
To: Teweldemedhin Aberra <teweldemat@gmail•com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP - Dead Man's Switch
Date: Mon, 11 Dec 2017 13:28:03 -0500	[thread overview]
Message-ID: <CAL5BAw1ayaiD07PJ4MRqcKaXdet5KW131en69vbw5gebWTF8nA@mail.gmail.com> (raw)
In-Reply-To: <CAEA=K3QiDtuHJNBLbZxaw6eSGhYWC5++vKJEX2Shxs7vb9bZ-A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3263 bytes --]

Hi,
1. If there are 16.4 million mined and 4 million are lost, that results in
12.4 million in circulation vs 14.4 million.
2. Satoshi addressed this as have numerous other people (
https://bitcointalk.org/index.php?topic=198.msg1647#msg1647 ) - lost coins
decrease supply, increasing value of the remaining coins.
3. This assumes this is a problem.  Bitcoin is divisible, 100 million,
potentially more if necessary. (
https://en.bitcoin.it/wiki/Help:FAQ#How_divisible_are_bitcoins.3F)
4. Why is it okay to steal bitcoins from people who's bitcoins have been
"dormant" for a fixed period, 10 years in your example?
5. What happens to bitcoins that, say, Hal Finney still had (if any) and he
put in cold storage while he is in ultimate cold storage (
https://en.wikipedia.org/wiki/Hal_Finney_(computer_scientist)#Death) ?
Ditto for someone, say, in a coma for 11 years, in jail for 11 years or any
other similar event?  Or a 20 year old sets aside coins for retirement.
The following year, the system is changed, and when he looks again after
not paying attention for a decade or two, they are gone.
6. This encourages censorship by miners for people attempting to move coins.
7. This has been discussed many times before and everyone is welcome to
fork bitcoin code and the block chain and convince people to follow this
chain and code.  Then you can see if you can get many people to agree that
this is a good idea.








On Mon, Dec 11, 2017 at 12:30 PM, Teweldemedhin Aberra via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:

> It is estimated that about 4 million of the about 16.4 Bitcoins ever mined
> are lost forever because no one knows the private keys of some Bitcoin
> addresses. This effectively mean there are actually only 14.4 million
> Bitcoins in circulation even though 16.4 million are mined. There is no way
> of eliminating the human errors that cause these losses of Bitcoin from
> circulation, while the number of Bitcoin that will ever be mined is capped
> at 21 million. This means the total number of Bitcoins that are in
> circulation will eventually become zero, bringing the network to an end.
>
> The solution this BIP proposes is to implementing a dead man's switch to
> Bitcoin addresses. The dead man's switch causes the Bitcoins assigned to
> dormant addresses to automatically expire. A Bitcoin address is deemed
> dormant if it is not used in transactions for some fixed length of time,
> say ten years.
>
> The calculation of the miner's reward should take into account the
> Bitcoins that has expired. This means there is a possibility that miner's
> reward can increase if sufficient number of Bitcoins expire.
>
> Ref:
>
> http://fortune.com/2017/11/25/lost-bitcoins/
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
> <#m_2495265241835744459_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

[-- Attachment #2: Type: text/html, Size: 6278 bytes --]

  parent reply	other threads:[~2017-12-11 18:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 17:30 Teweldemedhin Aberra
2017-12-11 18:12 ` Douglas Roark
2017-12-11 18:12 ` Nick Pudar
2017-12-11 18:26   ` Pieter Wuille
2017-12-11 18:13 ` Radoslaw Biernacki
2017-12-11 18:28 ` Chris Riley [this message]
2017-12-11 18:34 ` Luke Dashjr
2017-12-12  1:10   ` Teweldemedhin Aberra
     [not found]     ` <CALC81COEqhkX04MyJ=hxGgapVTqSeSYXJJUgutxWp5GbZmSSmQ@mail.gmail.com>
     [not found]       ` <5a2f9240.0abddf0a.0333.1139@mx.google.com>
2017-12-12 14:02         ` Ricardo Filipe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAL5BAw1ayaiD07PJ4MRqcKaXdet5KW131en69vbw5gebWTF8nA@mail.gmail.com \
    --to=criley@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=teweldemat@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox