[bitcoin-dev] BIP draft: Extended block header hardfork

Johnson Lau jl2012 at xbt.hk
Mon Apr 3 03:36:13 UTC 2017

> On 3 Apr 2017, at 04:39, Russell O'Connor <roconnor at blockstream.io> wrote:
> On Sun, Apr 2, 2017 at 4:13 PM, Johnson Lau via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org <mailto:bitcoin-dev at lists.linuxfoundation.org>> wrote:
>         • the witness of the first input of the coinbase transaction MUST have exactly one stack item (the "extended header"), with the following data:
>                 • bytes 0 to 3: nHeight MUST be equal to the height of this block (signed little endian)
>  Someone told me a while back that it would be more natural if we move the nHeight from the coinbase script to the coinbase locktime.  Have you considered doing this?

Yes, it’d look much better. But I’m thinking of a different approach: instead of using a hash of 0000….0000, we use the hash of previous block for the coinbase input. With some new SIGHASH design, this allows people to pay to a child of a particular block. This is actually implemented in my spoonnet2 branch. I’ll describe it with a BIP soon

However, what I’m trying to do in the extended block header is independent to the design of coinbase tx. Here I’m trying to let people knowing the height just by a header and extended header (<300 bytes), without requiring all headers in the history.

Also I forgot to post the link of the BIP: https://github.com/jl2012/bips/blob/spoonnet/bip-extheader.mediawiki <https://github.com/jl2012/bips/blob/spoonnet/bip-extheader.mediawiki>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170403/7b6c9678/attachment.html>

More information about the bitcoin-dev mailing list