From: Tom Zander <tomz@freedommail.ch>
To: bitcoin-dev@lists.linuxfoundation.org
Date: Fri, 26 May 2017 11:21:55 +0200
Message-ID: <2575282.hbjRTIzDqY@strawberry>
In-Reply-To: <2E6BB6FA-65FF-497F-8AEA-4CC8655BAE69@gmail.com>
References: <D0299438-E848-4696-B323-8D0E810AE491@gmail.com>
	<CAFmyj8zNkPj3my3CLzkXdpJ1xkD0GQk8ODg09qYnnj_ONGUtsQ@mail.gmail.com>
	<2E6BB6FA-65FF-497F-8AEA-4CC8655BAE69@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [bitcoin-dev] Emergency Deployment of SegWit as a partial
	mitigation of CVE-2017-9230
Precedence: list

On Friday, 26 May 2017 10:02:27 CEST Cameron Garnham via bitcoin-dev wrote:
> So, I started searching for the motivations of such a large amount of the
> mining hash-rate holding a position that isn=E2=80=99t at-all represented=
 in the
> wider Bitcoin Community. My study of ASICBOOST lead to a =E2=80=98bingo=
=E2=80=99 moment:=20
> If one assumes that the 67% of the hash rate that refuse to signal for
> SegWit are using ASICBOOST. The entire picture of this political
> stalemate became much more understandable.

I=E2=80=99m uncomfortable with your =E2=80=9Cbingo=E2=80=9D moment, and you=
r huge assumption to get=20
to make it fit.
The reality is that we have seen repeatedly that the miners are stating the=
y=20
are Ok with an ASICBOOST disabling change.
The larger mining industry has just this week come to consensus about a=20
better way to activate SegWit! Referring to the New York consensus meeting!!
https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-13352=
1fe9a77

I question your conclusions of miners not supporting SegWit because of=20
ASICBOOST, the evidence shows this accusation to be false.

You openly admitting here that you use ASICBOOST as a tool to push SegWit i=
s=20
further making me uncomfortable. Your intention may be pure, but the method=
s=20
are not.
And on that I agree with Andreas, that taints this proposal.

=2D-=20
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel