[bitcoin-dev] Emergency Deployment of SegWit as a partial mitigation of CVE-2017-9230

Cameron Garnham da2ce7 at gmail.com
Fri May 26 06:30:08 UTC 2017

Hello Bitcoin-Dev,

CVE-2017-9230 (1) (2), or commonly known as ‘ASICBOOST’ is a severe (3) (4) and actively exploited (5) security vulnerability.
To learn more about this vulnerability please read Jeremy Rubin’s detailed report:
Andreas Antonopoulos has an excellent presentation on why asicboost is dangerous:

In decisions on the #bitcoin-core-dev IRC channel; It was proposed, without negative feedback, that SegWit be used as a partial-mitigation of CVE-2017-9230.

SegWit partially mitigates asicboost with the common reasonable assumption that any block that doesn’t include a witness commit in it's coinbase transaction was mined using covert asicboost.  Making the use of covert asicboost far more conspicuous.

It was also proposed that this partial mitigation should be quickly strengthened via another soft-fork that makes the inclusion of witness commits mandatory, without negative feedback.

The security trade-offs of deploying a partial-mitigation to CVE-2017-9230 quickly vs more slowly but more conservatively is under intense debate.  The author of this post has a strong preference to the swiftest viable option.


(1) CVE Entry:

(2) Announcement of CVE to Mailing List:

(3) Discussion of the perverse incentives created by 'ASICBOOST' by Ryan Grant:

(4) Discussion of ASICBOOST's non-independent PoW calculation by Tier Nolan:

(5) Evidence of Active Exploit by Gregory Maxwell:

More information about the bitcoin-dev mailing list