public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mark Friedenbach <mark@friedenbach.org>
To: Aaron Voisine <voisine@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] questions about bitcoin-XT code fork & non-consensus hard-fork
Date: Mon, 15 Jun 2015 17:41:00 -0700	[thread overview]
Message-ID: <CAOG=w-vFMczkSx+Dv06sX6tLp1vn3a-4g1B8JaGDFs_BDgbc8g@mail.gmail.com> (raw)
In-Reply-To: <CACq0ZD5TTJ=dvz+o-ex6vUWAnOtMfD=VE7JaZWXYM1Lo2L_9wA@mail.gmail.com>

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

On Mon, Jun 15, 2015 at 5:08 PM, Aaron Voisine <voisine@gmail.com> wrote:

> Wasn't the XT hard fork proposed as a last resort, should the bitcoin-core
> maintainers simply refuse to lift the 1Mb limit? No one wants to go that
> route. An alternate hard-fork proposal like BIP100 that gets consensus, or
> a modified version of gavin's that ups the limit to 8Mb instead of 20Mb, or
> hell even some major changes to the non-consunsus code to make it
> adequately handle the situation when blocks fill up, and allow wallet
> software to continue working with a send-and-forget use pattern, any of
> these would be enough to avoid the need for an XT only hard-fork.
>
> So far BIP100 is the only one that seems to actually be getting any sort
> of momentum toward consensus, and it was proposed... 2 days ago? When the
> XT fork was proposed as a last resort, it was when the opponents were (to
> my understanding) suggesting we just let blocks fill up, and hopefully
> things would just work out on their own.
>

We are not reaching consensus about any proposal, Garzik's or otherwise.

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

  reply	other threads:[~2015-06-16  0:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15  0:04 [Bitcoin-development] questions about bitcoin-XT code fork & non-consensus hard-fork Adam Back
2015-06-15  9:56 ` Mike Hearn
2015-06-15 18:03   ` Adam Back
2015-06-15 20:55     ` Mike Hearn
2015-06-15 21:56       ` Bryan Bishop
2015-06-15 22:17         ` Faiz Khan
2015-06-15 22:56           ` Brian Hoffman
2015-06-15 23:05             ` [Bitcoin-development] questions about bitcoin-XT code fork &non-consensus hard-fork Raystonn .
2015-06-16  0:08             ` [Bitcoin-development] questions about bitcoin-XT code fork & non-consensus hard-fork Aaron Voisine
2015-06-16  0:41               ` Mark Friedenbach [this message]
2015-06-16  1:17               ` Alex Morcos
2015-06-16  4:00                 ` Aaron Voisine
2015-06-17  3:54                   ` Peter Todd
2015-06-18 15:23               ` Jorge Timón
2015-06-16 11:29           ` Mike Hearn
2015-06-16 11:20         ` Mike Hearn
2015-06-16 12:33     ` Pindar Wong
2015-06-16 13:33       ` Peter Todd
2015-06-16 13:55         ` Pindar Wong
2015-06-17  3:59           ` Peter Todd
2015-06-25  6:43             ` [bitcoin-dev] " Pindar Wong
2015-06-26 19:30               ` Peter Todd
2015-06-15 22:54   ` odinn
2015-06-16  1:20     ` Eric Lombrozo
2015-06-16  5:18   ` Venzen
2015-06-16  6:09     ` Marcel Jamin
2015-06-16  9:21       ` Benjamin
2015-06-16 11:01     ` Tier Nolan
2015-06-17  3:52 ` Troy Benjegerdes

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='CAOG=w-vFMczkSx+Dv06sX6tLp1vn3a-4g1B8JaGDFs_BDgbc8g@mail.gmail.com' \
    --to=mark@friedenbach.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=voisine@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