public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Eric Lombrozo <elombrozo@gmail.com>
To: Ahmed Zsales <ahmedzsales18@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin is an experiment. Why don't we have an experimental hardfork?
Date: Tue, 18 Aug 2015 19:53:16 -0700	[thread overview]
Message-ID: <AE1DA2ED-86D2-48CB-BE0B-57CB0F5B8503@gmail.com> (raw)
In-Reply-To: <CADr=VrROXW0cvCYKsidxSLgtYvBxPAGvcv_FFbeTAFJ3tF6AiQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1592 bytes --]

As an aside, combining reward halving with block size limit doubling would have probably been a good idea :)

> On Aug 18, 2015, at 3:51 PM, Ahmed Zsales via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
> 
> -> You need to take into account the reward halving, likely to be in 3Q2016. Forks and reward halving at the same time would possibly be a bad combination.
> 
> -> The original proposed date for the fork was December 2015. It was pushed back to January as December is a busy period for a lot of people and businesses. Likewise, June is a busy period for people. July / August is a good period as it is quiet because people go on holiday. A window of 2 months during holiday periods is better than starting in June. January 2016 is better, mainly because of the excessive reward halving chatter likely to be going on..
> 
> ..
> Proposal (parameters in ** are my recommendations but negotiable):
> 
> 1. Today, we all agree that some kind of block size hardfork will happen on t1=*1 June 2016*
> 
> 2. If no other consensus could be reached before t2=*1 Feb 2016*, we will adopt the backup plan
> 
> 3. The backup plan is: t3=*30 days* after m=*80%* of miner approval, but not before t1=*1 June 2016*, the block size is increased to s=*1.5MB*
> 
> 4. If the backup plan is adopted, we all agree that a better solution should be found before t4=*31 Dec 2017*.
> ..
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


[-- Attachment #1.2: Type: text/html, Size: 2547 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

  reply	other threads:[~2015-08-19  2:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  9:54 [bitcoin-dev] Bitcoin is an experiment. Why don't we have an experimental hardfork? jl2012
2015-08-18 11:57 ` Micha Bailey
2015-08-18 18:52 ` Eric Lombrozo
2015-08-18 20:48 ` Danny Thorpe
2015-08-18 20:51   ` Eric Lombrozo
2015-08-18 21:06     ` Danny Thorpe
2015-08-18 21:17       ` Eric Lombrozo
2015-08-18 21:39         ` Danny Thorpe
2015-08-19  9:29       ` Jorge Timón
2015-08-19 10:14         ` odinn
2015-08-19 11:06           ` Jorge Timón
2015-08-19 11:25             ` odinn
2015-08-19 15:22               ` jl2012
2015-08-19 15:48                 ` Tier Nolan
2015-08-19 15:25               ` Jorge Timón
2015-08-19 17:30         ` Danny Thorpe
2015-08-19 18:33           ` Jorge Timón
2015-08-18 22:51 ` Ahmed Zsales
2015-08-19  2:53   ` Eric Lombrozo [this message]
2015-08-19  9:24 ` Jorge Timón
2015-08-19 10:34   ` jl2012
2015-08-19 10:53     ` Jorge Timón

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=AE1DA2ED-86D2-48CB-BE0B-57CB0F5B8503@gmail.com \
    --to=elombrozo@gmail.com \
    --cc=ahmedzsales18@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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