public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: James Hilliard <james.hilliard1@gmail.com>
To: Tom Zander <tomz@freedommail.ch>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP draft: Extended block header hardfork
Date: Tue, 4 Apr 2017 09:59:12 -0500	[thread overview]
Message-ID: <CADvTj4pOGTdopFG2NPGgEkS2y44FwKMEm2_ANQapGirqbZHP+g@mail.gmail.com> (raw)
In-Reply-To: <7465915.Qhm6HcGyAn@strawberry>

It is a consensus rule
https://github.com/bitcoin/bips/blob/master/bip-0034.mediawiki

On Tue, Apr 4, 2017 at 6:47 AM, Tom Zander via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> On Sunday, 2 April 2017 22:39:13 CEST Russell O'Connor via bitcoin-dev
> wrote:
>>  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?
>
> That change would not be a consensus change and thus free to make any day.
>
> --
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


  reply	other threads:[~2017-04-04 14:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-02 20:13 [bitcoin-dev] BIP draft: Extended block header hardfork Johnson Lau
2017-04-02 20:39 ` Russell O'Connor
2017-04-03  3:36   ` Johnson Lau
2017-04-04 11:47   ` Tom Zander
2017-04-04 14:59     ` James Hilliard [this message]
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=CADvTj4pOGTdopFG2NPGgEkS2y44FwKMEm2_ANQapGirqbZHP+g@mail.gmail.com \
    --to=james.hilliard1@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=tomz@freedommail.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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