public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <greg@xiph.org>
To: Peter Todd <pete@petertodd.org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Completing the retirement of the alert system
Date: Sat, 10 Sep 2016 01:48:40 +0000	[thread overview]
Message-ID: <CAAS2fgQSQMojm6srKD_enNYu=bw04JPgH1S6__920qjVGh5EFQ@mail.gmail.com> (raw)
In-Reply-To: <20160910005802.GA24954@fedora-21-dvm>

On Sat, Sep 10, 2016 at 12:58 AM, Peter Todd <pete@petertodd.org> wrote:
> Good to do this sooner rather than later, as alert propagation on the P2P
> network is going to continue to get less reliable as nodes upgrade to software

Yes, this was one of my motivations for doing this soon.

It would only require about 2 LOC to have Bitcoin Core vomit out a
blob containing the final alert to any old protocol version peers that
connect.  I don't know how other people would feel about that, but I
wouldn't mind implementing it, and it would greatly improve the
likelihood that they continue to to get once propagation of it is
gone. This could be left in the codebase for a couple years or until
other changes made those old versions p2p incompatible for other
reasons.


  reply	other threads:[~2016-09-10  1:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-10  0:42 [bitcoin-dev] Completing the retirement of the alert system Gregory Maxwell
2016-09-10  0:54 ` Eric Voskuil
2016-09-10  0:58 ` Peter Todd
2016-09-10  1:48   ` Gregory Maxwell [this message]
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
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='CAAS2fgQSQMojm6srKD_enNYu=bw04JPgH1S6__920qjVGh5EFQ@mail.gmail.com' \
    --to=greg@xiph.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=pete@petertodd.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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