<div dir="auto"><div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, May 26, 2019, 07:07 Aymeric Vitte via bitcoin-dev <<a href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="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'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't need this to reconciliate things<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">This is a question that belongs on <a href="https://bitcoin.stackexchange.com">https://bitcoin.stackexchange.com</a>, not this list.</div><div dir="auto"><br></div><div dir="auto">Cheers,</div><div dir="auto"><br></div><div dir="auto">-- </div><div dir="auto">Pieter</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>