From: Gregory Maxwell <greg@xiph•org>
To: gb <kiwigb@yahoo•com>,
Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Cc: bitcoin-core-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] [bitcoin-core-dev] Bitcoin Core update notice
Date: Sat, 22 Sep 2018 04:59:53 +0000 [thread overview]
Message-ID: <CAAS2fgQePRHfH5Aq4fi_q7+PWCuBdZfR3ac7YCw_EVAfR7b5uQ@mail.gmail.com> (raw)
In-Reply-To: <1537569586.4405.2.camel@yahoo.com>
On Sat, Sep 22, 2018 at 4:25 AM gb via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> If the bugfix can be backported to earlier versions why is the
Have been backported, not merely can be.
> hype/hysteria about "everybody" must immediately upgrade to 0.16.3
> currently being spread on the forums/reddit?
For instructions to be effective they need to be concise. Presenting
people with a complex decision tree is not a way to maximize wellfare.
The few parties that would be better off on some other version already
know that they have some reason to not run the latest stable, and can
do more research to find out their other options. The announcement
posted on the bitcoin core site, I think is adequately clear but if
you see an opportunity to improve it, please make suggestions.
> I don't see any effort to correct this misinformation either.
It's decent advice, not misinformation. You can run the fixed earlier
versions but they have other issues, I wouldn't recommend anyone run
older versions generally.
Reasoning about risk is complicated. For example, when people were
talking about only the crash component of the issue there were some
people stating "I don't care if I go down, an unlikely delay in
processing payments would not be a problem." But, in fact, a network
exploitable crash is pretty dangerous: an attacker can carve up the
network into partitions that will produce long valid forks and reorg
against each other, enabling double-spends. The best one sentence
advice available is to upgrade to the latest version. You'd probably
have to get up to two page explanations discussing trade-offs before
it makes sense to talk about running a fixed 0.14 or what not.
Theymos' language is stronger than I would have chosen, but I think
it's language that errors on the side of protecting people from harm.
prev parent reply other threads:[~2018-09-22 5:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 0:06 [bitcoin-dev] " Pieter Wuille
2018-09-21 22:39 ` [bitcoin-dev] [bitcoin-core-dev] " gb
2018-09-22 4:56 ` Andrew Chow
2018-09-22 4:59 ` Gregory Maxwell [this message]
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=CAAS2fgQePRHfH5Aq4fi_q7+PWCuBdZfR3ac7YCw_EVAfR7b5uQ@mail.gmail.com \
--to=greg@xiph$(echo .)org \
--cc=bitcoin-core-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=kiwigb@yahoo$(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