From: Douglas Roark <joroark@vt•edu>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP - Dead Man's Switch
Date: Mon, 11 Dec 2017 10:12:02 -0800 [thread overview]
Message-ID: <b1a6d74d-f268-e239-ef0e-6ce6facc21f8@vt.edu> (raw)
In-Reply-To: <CAEA=K3QiDtuHJNBLbZxaw6eSGhYWC5++vKJEX2Shxs7vb9bZ-A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 773 bytes --]
With all due respect, this isn't a BIP. It's idle speculation regarding
what one person considers to be a problem and others may not. Please
read https://github.com/bitcoin/bips/blob/master/bip-0001.mediawiki and
try again. Among other things:
- Convince us this is a real issue, and that your data is accurate.
Who's to say which coins are truly lost? Maybe the people controlling
the keys are just laying low, wish to use their coins in 2112, etc.
- Propose formulas for how the miners will take everything into account,
and explain why they're acceptable.
- Write code that implements your ideas.
Good luck!
--
---
Douglas Roark
Cryptocurrency, network security, travel, and art.
https://onename.com/droark
joroark@vt•edu
PGP key ID: 26623924
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 895 bytes --]
next prev parent reply other threads:[~2017-12-11 18:12 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 [this message]
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
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=b1a6d74d-f268-e239-ef0e-6ce6facc21f8@vt.edu \
--to=joroark@vt$(echo .)edu \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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