public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Russell O'Connor" <roconnor@blockstream•io>
To: Johnson Lau <jl2012@xbt•hk>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP draft: Extended block header hardfork
Date: Sun, 2 Apr 2017 16:39:13 -0400	[thread overview]
Message-ID: <CAMZUoKkFh-uBwzTZoJ0kzyJukEG2HeDf_VmTwgZMm1esD+TaFQ@mail.gmail.com> (raw)
In-Reply-To: <2D094CEC-3756-45B0-970F-1EB33DF352C5@xbt.hk>

[-- Attachment #1: Type: text/plain, Size: 563 bytes --]

On Sun, Apr 2, 2017 at 4:13 PM, Johnson Lau via bitcoin-dev <
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?

[-- Attachment #2: Type: text/html, Size: 903 bytes --]

  reply	other threads:[~2017-04-02 20:39 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 [this message]
2017-04-03  3:36   ` Johnson Lau
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=CAMZUoKkFh-uBwzTZoJ0kzyJukEG2HeDf_VmTwgZMm1esD+TaFQ@mail.gmail.com \
    --to=roconnor@blockstream$(echo .)io \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=jl2012@xbt$(echo .)hk \
    /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