public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: John Sacco <johnsock@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP - Block size doubles at each reward halving with max block size of 32M
Date: Fri, 13 Nov 2015 10:52:57 +0000	[thread overview]
Message-ID: <201511131052.58623.luke@dashjr.org> (raw)
In-Reply-To: <CAEkt4XvGzkFipDwqD_m+56+vWxRaF+rRy8ydJJ7tqibcyjWJ0g@mail.gmail.com>

On Friday, November 13, 2015 9:50:47 AM John Sacco wrote:
> * 2 MB, height 420,000 < 630,000; (fork active when 75% of last 1,000 blocks
> signal support and block 420,000 reached, ~July 2016)

I'd leave out the block signalling. It isn't really useful, complicates the 
whole BIP, and mistakenly gives people the idea that miners have a choice in 
hardforks.

Luke


  reply	other threads:[~2015-11-13 10:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 23:47 [bitcoin-dev] BIP - Block size doubles at each reward halving with max block size of 32M John Sacco
2015-11-13  2:56 ` Chun Wang
2015-11-13  3:37   ` John Sacco
2015-11-13  7:49     ` Btc Drak
2015-11-13  9:50       ` John Sacco
2015-11-13 10:52         ` Luke Dashjr [this message]
     [not found]           ` <1447430469019.e0ee1956@Nodemailer>
2015-11-13 22:28             ` Luke Dashjr
2015-11-14  0:02               ` digitsu
2015-11-14  9:31                 ` Adam Back
2015-11-14 10:52                   ` Jorge Timón
2015-11-14 21:11                     ` Luke Dashjr
     [not found]                       ` <CADZB0_Z3Kf4GW0VATjb10kJF0aFgyFOcqX_=y+LFoUpsi+TRUA@mail.gmail.com>
2015-11-14 21:27                         ` Luke Dashjr
2015-11-15 12:16                           ` Jorge Timón
     [not found]                             ` <CABEog-XUNt9kDS7Mc0XYFjm5ePUT0m1YaAoG9VypTCiGLBongQ@mail.gmail.com>
2015-11-18 10:15                               ` Jorge Timón
2015-11-13  6:39   ` Luke Dashjr

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=201511131052.58623.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=johnsock@gmail.com \
    /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