MIME-Version: 1.0
Sender: slashene@gmail.com
From: Nicolas Dorier <nicolas.dorier@gmail.com>
Date: Tue, 9 Feb 2016 21:32:06 +0900
Message-ID: <CA+1nnrnghvJFfcg0Az0di1EGJYrSh-9h+5Y9P1pfQbbL-AuX=w@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a1139641e8e79ef052b558296
Subject: Re: [bitcoin-dev] On Hardforks in the Context of SegWit
Precedence: list

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

> 2) In order to prevent significant blowups in the cost to validate
> [...] and transactions are only allowed to contain
> up to 20 non-segwit inputs. [...]

There is two kind of hard fork, the one who breaks things, and the one who
does not.
Restricting the non-segwit inputs would disrupt lots of services, and
potentially invalidating
hash time locked transactions, which is a very bad precedent.
So I'm strongly against this particular point.

> scriptPubKeys are now limited to 100 bytes in
> size and may not contain OP_CODESEPARATOR, scriptSigs must be push-only
> (ie no non-push opcodes)

Same problem for native multisig, however potentially less important than
the previous point.

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

<div dir=3D"ltr"><div>&gt; 2) In order to prevent significant blowups in th=
e cost to validate</div><div>&gt; [...] and transactions are only allowed t=
o contain</div><div>&gt; up to 20 non-segwit inputs. [...]</div><div><br></=
div><div>There is two kind of hard fork, the one who breaks things, and the=
 one who does not.</div><div>Restricting the non-segwit inputs would disrup=
t lots of services, and potentially invalidating=C2=A0</div><div>hash time =
locked transactions, which is a very bad precedent.</div><div>So I&#39;m st=
rongly against this particular point.<br></div><div><br></div><div>&gt;=C2=
=A0<span style=3D"font-size:12.8px">scriptPubKeys are now limited to 100 by=
tes in</span></div><span style=3D"font-size:12.8px">&gt; size and may not c=
ontain OP_CODESEPARATOR, scriptSigs must be push-only</span><br style=3D"fo=
nt-size:12.8px"><span style=3D"font-size:12.8px">&gt; (ie no non-push opcod=
es)</span><div><span style=3D"font-size:12.8px"><br></span></div><div><span=
 style=3D"font-size:12.8px">Same problem for native multisig, however poten=
tially less important than the previous point.</span></div></div>

--001a1139641e8e79ef052b558296--