public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org, joe2015@openmailbox.org
Subject: Re: [bitcoin-dev] Increasing the blocksize as a (generalized) softfork.
Date: Mon, 4 Jan 2016 21:53:36 +0000	[thread overview]
Message-ID: <201601042153.37771.luke@dashjr.org> (raw)
In-Reply-To: <1bf64a5b514d57ca37744ae5f5238149@openmailbox.org>

On Sunday, December 20, 2015 10:56:33 AM joe2015--- via bitcoin-dev wrote:
> "generalized" softfork.

FWIW, this is something I've been planning to proposed (in a nicer form) for a 
while, tentatively called a "soft hardfork" (or less-seriously a "softserve 
hardfork"). The big piece missing that I've been holding off on publishing it 
as a BIP until complete, is a planned-out defensive reaction for a community 
which wishes to reject the hardfork. I guess I should probably prioritise this 
a bit more now...

Luke


  parent reply	other threads:[~2016-01-04 21:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20 10:56 [bitcoin-dev] Increasing the blocksize as a (generalized) softfork joe2015
2015-12-20 15:22 ` joe2015
2015-12-20 15:50 ` Tier Nolan
2015-12-20 18:17 ` Bryan Bishop
2015-12-21  3:04   ` joe2015
2015-12-21  4:23 ` jl2012
2015-12-21  4:41   ` joe2015
2015-12-30 19:00     ` Bob McElrath
2015-12-30 23:49       ` Jonathan Toomim
2015-12-30 23:56         ` Jonathan Toomim
2015-12-31  0:04         ` Bob McElrath
2015-12-31  4:39           ` joe2015
2015-12-31 10:39             ` David Chan
2015-12-31 11:32               ` joe2015
2016-01-04 21:53 ` Luke Dashjr [this message]
2015-12-20 17:21 joe2015
2015-12-21  3:39 ` Jeff Garzik
2015-12-21  3:58   ` joe2015

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=201601042153.37771.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=joe2015@openmailbox.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