MIME-Version: 1.0
References: <e537e781-e10f-7299-fddb-67fab74124c0@gmail.com>
In-Reply-To: <e537e781-e10f-7299-fddb-67fab74124c0@gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
Date: Sun, 26 May 2019 10:54:08 -0700
Message-ID: <CAPg+sBg6ws3LZXeppDfjznHbdBSoeQ4-5FHwDutQ1frRFZNc9w@mail.gmail.com>
To: Aymeric Vitte <vitteaymeric@gmail.com>, 
	Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000000851400589ce1f5d"
Subject: Re: [bitcoin-dev] Two questions about segwit implementation
Precedence: list

--0000000000000851400589ce1f5d
Content-Type: text/plain; charset="UTF-8"

On Sun, May 26, 2019, 07:07 Aymeric Vitte via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> I realized recently that my segwit implementation was not correct,
> basically some time ago, wrongly reading the specs (and misleaded by
> what follows), I thought that scriptsig would go into witness data as it
> was, but that's not the case, op_pushdata is replaced by varlen
>
> Now reading correctly the specs, they seem to be not totally correct,
> then the first question is: why OP_0 is 00 in witness data and not 0100?
> Does this apply to other op_codes? This does not look logical at all
>
> The second question is: why for non segwit inputs there is a 00 length
> in segwit data, what is the rational for that? It should just be nothing
> since you don't need this to reconciliate things
>

This is a question that belongs on https://bitcoin.stackexchange.com, not
this list.

Cheers,

-- 
Pieter

--0000000000000851400589ce1f5d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D=
"gmail_attr">On Sun, May 26, 2019, 07:07 Aymeric Vitte via bitcoin-dev &lt;=
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
I realized recently that my segwit implementation was not correct,<br>
basically some time ago, wrongly reading the specs (and misleaded by<br>
what follows), I thought that scriptsig would go into witness data as it<br=
>
was, but that&#39;s not the case, op_pushdata is replaced by varlen<br>
<br>
Now reading correctly the specs, they seem to be not totally correct,<br>
then the first question is: why OP_0 is 00 in witness data and not 0100?<br=
>
Does this apply to other op_codes? This does not look logical at all<br>
<br>
The second question is: why for non segwit inputs there is a 00 length<br>
in segwit data, what is the rational for that? It should just be nothing<br=
>
since you don&#39;t need this to reconciliate things<br></blockquote></div>=
</div><div dir=3D"auto"><br></div><div dir=3D"auto">This is a question that=
 belongs on <a href=3D"https://bitcoin.stackexchange.com">https://bitcoin.s=
tackexchange.com</a>, not this list.</div><div dir=3D"auto"><br></div><div =
dir=3D"auto">Cheers,</div><div dir=3D"auto"><br></div><div dir=3D"auto">--=
=C2=A0</div><div dir=3D"auto">Pieter</div><div dir=3D"auto"><br></div><div =
dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>

--0000000000000851400589ce1f5d--