MIME-Version: 1.0
In-Reply-To: <CACDYSUS29qoaNML8XmRz6xDSZsiHe2kYsEFun-kBLaups-OiJg@mail.gmail.com>
References: <CAJR7vkpRhNsQsem-nFkeubX04xx1y7aHwCENfg0d1266oOsXMw@mail.gmail.com>
	<Cwhn7YzwaDUZtOygDAgrU1UXjRPG-EiH3Fyz2c95gqOpNnNbiYL1NvhS28yK5wLJCnIqDaBrM6c574dY-O6_-bRjLIFmDe2NCxIuyV1w2dw=@protonmail.com>
	<CAJR7vkoq8Y_-fbdxN=--gF5wrGByr5oODc4FkTaCEvDSuP0whQ@mail.gmail.com>
	<CACDYSUROutAMV7C8pUXz0PMvH5awkw-XUtce7BxTtZMD_yUm5A@mail.gmail.com>
	<CAJR7vkrn-oFium3wFgcOdqNPuYq+rW2DqyOnkDaCTHabO0y3Xg@mail.gmail.com>
	<CACDYSUS29qoaNML8XmRz6xDSZsiHe2kYsEFun-kBLaups-OiJg@mail.gmail.com>
From: Jimmy Song <jaejoon@gmail.com>
Date: Sat, 8 Apr 2017 17:19:11 -0500
Message-ID: <CAJR7vkp+EXakt3a9+gKU01KpK9qXkuqr3rTrZ8-q6O8rsPhYtg@mail.gmail.com>
To: Pavel Moravec <pavel.moravec@braiins.cz>
Content-Type: multipart/alternative; boundary=001a1148e60aba25b2054caf2192
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A Small Modification to Segwit
Precedence: list

--001a1148e60aba25b2054caf2192
Content-Type: text/plain; charset=UTF-8

Pavel,


> I agree. I only wanted to make clear, that the impact would be
> significant. Lot of parties would be involved with nonequivalent
> starting positions.
>
>
I agree with you. I believe nonequivalent starting positions are the norm
in mining, not the exception and hence don't believe this to be a problem.


>
> I think the ASICBoost can and should be prevented completely.
>

It certainly can be and from the responses I'm getting, I believe there
would be at least a few people that would enthusiastically support a BIP to
do that. That is, however, a separate issue than my proposal. My proposal
aims to bring ASICBoost out into the open *while it is still possible*. A
BIP to prevent ASICBoost completely is in that sense compatible.

--001a1148e60aba25b2054caf2192
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
>Pavel,</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D=
"">
</span>I agree. I only wanted to make clear, that the impact would be<br>
significant. Lot of parties would be involved with nonequivalent<br>
starting positions.<br>
<span class=3D""><br></span></blockquote><div><br></div><div>I agree with y=
ou. I believe nonequivalent starting positions are the norm in mining, not =
the exception and hence don&#39;t believe this to be a problem.</div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
</span>I think the ASICBoost can and should be prevented completely.<br></b=
lockquote><div><br></div><div>It certainly can be and from the responses I&=
#39;m getting, I believe there would be at least a few people that would en=
thusiastically support a BIP to do that. That is, however, a separate issue=
 than my proposal. My proposal aims to bring ASICBoost out into the open *w=
hile it is still possible*. A BIP to prevent ASICBoost completely is in tha=
t sense compatible.</div></div></div></div>

--001a1148e60aba25b2054caf2192--