MIME-Version: 1.0
In-Reply-To: <1867667.WXWC1C9quc@crushinator>
References: <55828737.6000007@riseup.net>
	<CABm2gDoa7KxsgvREo3yiNjfd6AeayqAqkjMe2rvX8yyxR_ddcA@mail.gmail.com>
	<55831CAB.2080303@jrn.me.uk> <1867667.WXWC1C9quc@crushinator>
From: Mark Friedenbach <mark@friedenbach.org>
Date: Thu, 18 Jun 2015 14:49:51 -0700
Message-ID: <CAOG=w-scXm-46sp2NgR2UUp20R5ujuaAzW-jU_Owh20C4Xc=9A@mail.gmail.com>
To: Matt Whitlock <bip@mattwhitlock.name>
Content-Type: multipart/alternative; boundary=001a1140ea02c12bde0518d1ca87
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Concerns Regarding Threats by a Developer
 to Remove Commit Access from Other Developers
Precedence: list

--001a1140ea02c12bde0518d1ca87
Content-Type: text/plain; charset=UTF-8

Matt, I for one do not think that the block size limit should be raised at
this time. Matt Corallo also started the public conversation over this
issue on the mailing list by stating that he was not in favor of acting now
to raise the block size limit. I find it a reasonable position to take that
even if you feel the block size limit should be raised at some time in the
future, there are reasons why now is not the best time to do it.

On Thu, Jun 18, 2015 at 2:42 PM, Matt Whitlock <bip@mattwhitlock.name>
wrote:

> On Thursday, 18 June 2015, at 8:31 pm, Ross Nicoll wrote:
> > I may disagree with Mike & Gavin on timescale, but I do believe there's
> > a likelihood inaction will kill Bitcoin
>
> An honest question: who is proposing inaction? I haven't seen anyone in
> this whole, agonizing debate arguing that 1MB blocks are adequate. The
> debate has been about *how* to increase the block-size limit and whether to
> take action ASAP (at the risk of fracturing Bitcoin) or to delay action for
> further debate (at the risk of overloading Bitcoin). Even those who are
> arguing for further debate are not arguing for *inaction*.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--001a1140ea02c12bde0518d1ca87
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Matt, I for one do not think that the block size limit sho=
uld be raised at this time. Matt Corallo also started the public conversati=
on over this issue on the mailing list by stating that he was not in favor =
of acting now to raise the block size limit. I find it a reasonable positio=
n to take that even if you feel the block size limit should be raised at so=
me time in the future, there are reasons why now is not the best time to do=
 it.<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On =
Thu, Jun 18, 2015 at 2:42 PM, Matt Whitlock <span dir=3D"ltr">&lt;<a href=
=3D"mailto:bip@mattwhitlock.name" target=3D"_blank">bip@mattwhitlock.name</=
a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On =
Thursday, 18 June 2015, at 8:31 pm, Ross Nicoll wrote:<br>
&gt; I may disagree with Mike &amp; Gavin on timescale, but I do believe th=
ere&#39;s<br>
&gt; a likelihood inaction will kill Bitcoin<br>
<br>
</span>An honest question: who is proposing inaction? I haven&#39;t seen an=
yone in this whole, agonizing debate arguing that 1MB blocks are adequate. =
The debate has been about *how* to increase the block-size limit and whethe=
r to take action ASAP (at the risk of fracturing Bitcoin) or to delay actio=
n for further debate (at the risk of overloading Bitcoin). Even those who a=
re arguing for further debate are not arguing for *inaction*.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/=
listinfo/bitcoin-development</a><br>
</div></div></blockquote></div><br></div>

--001a1140ea02c12bde0518d1ca87--