From: Andrew C <achow101@gmail•com>
To: Johnson Lau <jl2012@xbt•hk>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Completing the retirement of the alert system
Date: Sat, 10 Sep 2016 09:23:44 -0400 [thread overview]
Message-ID: <bf57ea1e-87b6-52ae-3f92-23e62f936592@gmail.com> (raw)
In-Reply-To: <15713790962.be73b87e4580.3663496705131622210@xbt.hk>
On 9/10/2016 5:41 AM, Johnson Lau via bitcoin-dev wrote:
> 3. After a few months or so, publish the private key.
Why wait a few months? Why not just publish the key a few days after the
final alert?
next prev parent reply other threads:[~2016-09-10 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 0:42 Gregory Maxwell
2016-09-10 0:54 ` Eric Voskuil
2016-09-10 0:58 ` Peter Todd
2016-09-10 1:48 ` Gregory Maxwell
2016-09-10 2:19 ` Peter Todd
2016-09-10 1:31 ` Andrew C
2016-09-10 5:51 ` Wladimir J. van der Laan
2016-09-10 9:41 ` Johnson Lau
2016-09-10 13:23 ` Andrew C [this message]
2016-09-10 14:57 ` Johnson Lau
2016-09-10 15:36 ` Gregory Maxwell
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=bf57ea1e-87b6-52ae-3f92-23e62f936592@gmail.com \
--to=achow101@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jl2012@xbt$(echo .)hk \
/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