From: "Wladimir J. van der Laan" <laanwj@gmail•com>
To: Gregory Maxwell <greg@xiph•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Completing the retirement of the alert system
Date: Sat, 10 Sep 2016 07:51:17 +0200 [thread overview]
Message-ID: <20160910055117.GA5726@amethyst.visucore.com> (raw)
In-Reply-To: <CAAS2fgTYOUSm07N4NYDCsjjwSbAo_ye84UvbQF--3JzhLHkG0Q@mail.gmail.com>
On Sat, Sep 10, 2016 at 12:42:30AM +0000, Gregory Maxwell via bitcoin-dev wrote:
> The alert system was a centralized facility to allow trusted parties
> to send messages to be displayed in wallet software (and, very early
> on, actually remotely trigger the software to stop transacting).
>
> It has been removed completely in Bitcoin Core after being disabled for a while.
As it has been disabled in relevant software I think it's mostly symbolic at
this point, but yes, it makes sense to 'officially' retire the key. Let's
pin the date and make it widely known.
Doing this in organized fashion is much better than the whodunit that would
undoubtly follow when the key would simply leak, which could happen at any
time, as no one can know who it has spread to over all those years.
Re: timing, I'd say leave three months grace time after this announcement for
altcoins and such that may have accidentally have copied it to remove it, then
at the beginning of 2017 broadcast the final alert.
After that it's neutered, it's up to each of us that has the key to reveal it
or not or when. It's a historical curiosity then.
Wladimir
next prev parent reply other threads:[~2016-09-10 5:51 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 [this message]
2016-09-10 9:41 ` Johnson Lau
2016-09-10 13:23 ` Andrew C
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=20160910055117.GA5726@amethyst.visucore.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=greg@xiph$(echo .)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