From: Johnson Lau <jl2012@xbt•hk>
To: Russell O'Connor <roconnor@blockstream•io>
Cc: bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP draft: Extended block header hardfork
Date: Mon, 3 Apr 2017 11:36:13 +0800 [thread overview]
Message-ID: <9820147A-F1E8-4BF6-BBE0-005D20D49653@xbt.hk> (raw)
In-Reply-To: <CAMZUoKkFh-uBwzTZoJ0kzyJukEG2HeDf_VmTwgZMm1esD+TaFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
> On 3 Apr 2017, at 04:39, Russell O'Connor <roconnor@blockstream•io> wrote:
>
> On Sun, Apr 2, 2017 at 4:13 PM, Johnson Lau via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org <mailto:bitcoin-dev@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>
[-- Attachment #2: Type: text/html, Size: 2505 bytes --]
next prev parent reply other threads:[~2017-04-03 3:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 20:13 Johnson Lau
2017-04-02 20:39 ` Russell O'Connor
2017-04-03 3:36 ` Johnson Lau [this message]
2017-04-04 11:47 ` Tom Zander
2017-04-04 14:59 ` James Hilliard
2017-04-04 15:32 ` Tom Zander
2017-04-04 15:44 ` Greg Sanders
2017-04-04 16:03 ` Jean-Paul Kogelman
2017-04-04 16:17 ` Tom Zander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9820147A-F1E8-4BF6-BBE0-005D20D49653@xbt.hk \
--to=jl2012@xbt$(echo .)hk \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=roconnor@blockstream$(echo .)io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox