From: Gregory Maxwell <greg@xiph•org>
To: theymos <theymos@mm•st>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP proposal: Inhibiting a covert attack on the Bitcoin POW function
Date: Thu, 6 Apr 2017 00:17:17 +0000 [thread overview]
Message-ID: <CAAS2fgS9dOxJDU0WU87aSJhvYbYu60kVnO6acE0G7QJFw4AQLQ@mail.gmail.com> (raw)
In-Reply-To: <1491433518.2765667.935644008.2B153D86@webmail.messagingengine.com>
On Wed, Apr 5, 2017 at 11:05 PM, theymos via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> This seems to be a serious security problem. Would it be possible to have
> a flag-day softfork included in Bitcoin Core as soon as 0.14.1? I think that a trigger
> 3-6 months from release should be sufficient for enough of the economy to upgrade,
> given the severity of the issue.
Not 0.14.1 because that is in RC already and will hopefully be out in a week.
I think the speed of adoption depends a lot of the level of support
from the community. I don't believe there are any technical hurdles to
implementing this relatively quickly (and I specifically propose using
the users choice of the segwit commitment or a modified form in order
to lower the technical complexity and risk).
> BIP 141 says that the the commitment is optional if there are no SegWit transactions in
> the block, so will today's SegWit-ready miners always produce it even when optional
> according to BIP 141, as required by this softfork?
This is the default behavior as of 0.13.2, but I haven't gone out to
measure this which is why the backwards compatibility section of the
BIP isn't written yet.
While I'm posting, I've had a dozen off-list emails that presented me
with some FAQ:
Many people asked what other protocol upgrades beyond segwit could run
into the same incompatibility.
Many proposed improvements to Bitcoin require additional
transaction-dependent commitment data.
Examples include:
(1) Segwit.
(2) UTXO commitments. (non-delayed, at least)
(3) Committed Bloom filters
(4) Committed address indexes
(5) STXO commitments (non-delayed).
(6) Weak blocks
(7) Most kinds of fraud proofs
-- to state a few.
Unfortunately, putting *any* commitment to data dependent on the right
hand side of the hash tree in the left hand side (e.g. coinbase) means
a massive increase in the computation required for covert boosting,
because it means you can't use the left+right side combinations to
eliminate most of the hashing.
It's plausible, in fact, that this extra computation could completely
nullify the ASICBOOST advantage-- though this depends a lot on the
fine details of the implementation.
This proposal does not itself propose nullifying ASICBOOST entirely,
it proposes severely handicapping the covert form of it, and
eliminating the differential advantage for boosting miners related to
the use of transaction-dependent commitments.
Basically there are two completely separate concerns: that boosting
can produce a monopoly advantage which could be severely harmful to
the ecosystem, and that the efficient implementation of _covert_
boosting can severely harm many useful protocol improvements. My
proposal only addresses the second concern, by (I believe) completely
leveling the playing field so that opposing commitments will not break
boosting any worse, and by making covert boosting less appealing in
general.
Use of the segwit-style commitment even in non-segwit blocks is sufficient
because the segwit commitment commits to all transactions (except
the coinbase) and not just segwit ones.
(It was designed this way so that lite clients that needed witness
data could work with just one tree).
next prev parent reply other threads:[~2017-04-06 0:17 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 21:37 Gregory Maxwell
2017-04-05 23:05 ` theymos
2017-04-06 0:17 ` Gregory Maxwell [this message]
2017-04-06 0:39 ` Joseph Poon
2017-04-06 0:40 ` Joseph Poon
2017-04-06 1:32 ` Gregory Maxwell
2017-04-06 2:09 ` Joseph Poon
2017-04-05 23:25 ` Anthony Towns
2017-04-05 23:42 ` Joseph Poon
2017-04-06 2:10 ` Jonathan Toomim
2017-04-06 20:21 ` Jared Lee Richardson
2017-04-06 2:31 ` Peter Todd
2017-04-06 2:39 ` Bram Cohen
2017-04-06 2:49 ` Peter Todd
2017-04-06 3:11 ` Erik Aronesty
2017-04-06 3:23 ` Peter Todd
2017-04-06 3:23 ` David Vorick
2017-04-06 3:42 ` Peter Todd
2017-04-06 5:46 ` Thomas Daede
2017-04-06 6:24 ` Jonathan Toomim
2017-04-06 12:04 ` David Vorick
[not found] ` <CAMZUoK=oDAD9nhFAHkgncWtYxjBNh3qXbUffOH57QMnqjhmN6g@mail.gmail.com>
[not found] ` <CAMZUoKn8tr3LGbks0TnaCx9NTP6MZUzQ8PE6jDq1xiqpYyYwow@mail.gmail.com>
2017-04-06 13:55 ` Russell O'Connor
2017-04-06 16:49 ` Marco
2017-04-06 17:04 ` Alex Mizrahi
2017-04-06 17:13 ` Alex Mizrahi
2017-04-07 12:59 ` Jannes Faber
2017-04-07 13:28 ` Erik Aronesty
2017-04-06 17:31 ` Jared Lee Richardson
2017-04-06 17:26 ` Jared Lee Richardson
2017-04-06 15:36 ` Alex Mizrahi
2017-04-06 17:51 ` Jorge Timón
2017-04-06 7:24 ` bfd
2017-04-06 9:17 ` Luke Dashjr
2017-04-06 12:02 ` Luv Khemani
2017-04-06 12:11 ` Bryan Bishop
2017-04-06 17:43 ` Timo Hanke
2017-04-06 12:30 ` Luv Khemani
2017-04-06 15:15 ` Jorge Timón
2017-04-06 15:41 ` Daniel Robinson
2017-04-06 16:13 ` Andreas Schildbach
2017-04-06 21:38 ` Gregory Maxwell
2017-04-06 4:47 Oliver Petruzel
2017-04-06 4:49 Raystonn .
2017-04-06 7:47 ` praxeology_guy
2017-04-06 12:13 ` David Vorick
2017-04-07 1:34 Daniele Pinna
2017-04-07 6:46 ` Emilian Ursu
2017-04-07 7:44 ` Alex Mizrahi
2017-04-07 8:08 ` praxeology_guy
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=CAAS2fgS9dOxJDU0WU87aSJhvYbYu60kVnO6acE0G7QJFw4AQLQ@mail.gmail.com \
--to=greg@xiph$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=theymos@mm$(echo .)st \
/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