<oembed><type>rich</type><version>1.0</version><author_name>npub1dw88wd5gqsqn6ufxhf9h03uk8087l7gfzdtez5csjlt6pupu4pwsj8plrw</author_name><author_url>https://nostr.ae/npub1dw88wd5gqsqn6ufxhf9h03uk8087l7gfzdtez5csjlt6pupu4pwsj8plrw</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-04-02&#xA;📝 Original message:On Sun, Apr 2, 2017 at 4:13 PM, Johnson Lau via bitcoin-dev &lt;&#xA;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&#xA;&gt;         • the witness of the first input of the coinbase transaction MUST&#xA;&gt; have exactly one stack item (the &#34;extended header&#34;), with the following&#xA;&gt; data:&#xA;&gt;                 • bytes 0 to 3: nHeight MUST be equal to the height of&#xA;&gt; this block (signed little endian)&#xA;&gt;&#xA;&#xA; Someone told me a while back that it would be more natural if we move the&#xA;nHeight from the coinbase script to the coinbase locktime.  Have you&#xA;considered doing this?&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170402/98da6ac9/attachment.html&gt;</html></oembed>