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