From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <wtogami@gmail.com>) id 1YzOqM-0002Ej-FK
	for bitcoin-development@lists.sourceforge.net;
	Mon, 01 Jun 2015 12:29:26 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.192.169 as permitted sender)
	client-ip=209.85.192.169; envelope-from=wtogami@gmail.com;
	helo=mail-pd0-f169.google.com; 
Received: from mail-pd0-f169.google.com ([209.85.192.169])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YzOqL-00018Z-Em
	for bitcoin-development@lists.sourceforge.net;
	Mon, 01 Jun 2015 12:29:26 +0000
Received: by pdbnf5 with SMTP id nf5so45570604pdb.2
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 01 Jun 2015 05:29:19 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.70.38.10 with SMTP id c10mr39904208pdk.72.1433161759779;
	Mon, 01 Jun 2015 05:29:19 -0700 (PDT)
Received: by 10.70.93.72 with HTTP; Mon, 1 Jun 2015 05:29:19 -0700 (PDT)
In-Reply-To: <CANEZrP12WAcUOJp5UYg4pfWL7_4WiAHWWZAoaxAb5xB+qAP4Xg@mail.gmail.com>
References: <554BE0E1.5030001@bluematt.me>
	<CAFzgq-xByQ1E_33_m3UpXQFUkGc78HKnA=7XXMshANDuTkNsvA@mail.gmail.com>
	<CABsx9T0kbRe31LMwk499MQUw225f5GGd67GfhXBezHmDqxkioA@mail.gmail.com>
	<CAFzgq-z5WCznGhbOexS0XESNGAVauw45ewEV-1eMij7yDT61=Q@mail.gmail.com>
	<CAFzgq-zTybEQyGz0nq90u5n5JZcJzxQS_XKaTpr5POJi-tHM6A@mail.gmail.com>
	<CABsx9T2L5bi-c63-KqSifOMeNayUWSPo0_Hx8VjMR_4=kC3ixg@mail.gmail.com>
	<CAE28kUT61qYxqV0mOqw5Dan=eMiCvnG2SnsAeWzOWTxwLydyeQ@mail.gmail.com>
	<CABsx9T2hfpts5y_M6PdDcxmq9Q2smesJ0Nmp9a9iyPD_MoPC9g@mail.gmail.com>
	<CAE28kUTZV3YsaSCX2d5YwLetnf=f+bOWGrwxLXdZFywTZ=+Pjg@mail.gmail.com>
	<CALC81CNq-GK5q6R4bmgHL5_Ej2+cZrtQMMLVmuhvMxkZokM3hQ@mail.gmail.com>
	<CAE28kUQr+kUPak67tcNQGGscUXtJiD1LiXfjdD8_LMUWyVdR5w@mail.gmail.com>
	<CANEZrP12WAcUOJp5UYg4pfWL7_4WiAHWWZAoaxAb5xB+qAP4Xg@mail.gmail.com>
Date: Mon, 1 Jun 2015 02:29:19 -1000
Message-ID: <CAEz79Pr22g=2ZZWE_HrH5-foPqejp6Cb_Qr9n2=vRjmzGhHhZQ@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7bfe9b6e98f0c4051773f9d2
X-Spam-Score: 2.8 (++)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(wtogami[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.2 MISSING_HEADERS        Missing To: header
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
	2.7 MALFORMED_FREEMAIL Bad headers on message from free email service
	-0.5 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YzOqL-00018Z-Em
Subject: Re: [Bitcoin-development] Fwd: Block Size Increase Requirements
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2015 12:29:26 -0000

--047d7bfe9b6e98f0c4051773f9d2
Content-Type: text/plain; charset=UTF-8

Whilst it would be nice if miners in *outside* China can carry on forever
regardless of their internet situation, nobody has any inherent "right" to
mine if they can't do the job - if miners in *outside* China can't get the
trivial amounts of bandwidth required through their firewall *TO THE
MAJORITY OF THE HASHRATE* and end up being outcompeted then OK, too bad,
we'll have to carry on without them.


On Mon, Jun 1, 2015 at 12:13 AM, Mike Hearn <mike@plan99.net> wrote:

> Whilst it would be nice if miners in China can carry on forever regardless
> of their internet situation, nobody has any inherent "right" to mine if
> they can't do the job - if miners in China can't get the trivial amounts of
> bandwidth required through their firewall and end up being outcompeted then
> OK, too bad, we'll have to carry on without them.
>
> But I'm not sure why it should be a big deal. They can always run a node
> on a server in Taiwan and connect the hardware to it via a VPN or so.
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

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

<div dir=3D"ltr"><blockquote style=3D"margin:0 0 0 40px;border:none;padding=
:0px">Whilst it would be nice if miners <strike>in</strike> <b>outside</b> =
China can carry on forever regardless of their internet situation, nobody h=
as any inherent &quot;right&quot; to mine if they can&#39;t do the job - if=
 miners <strike>in</strike>=C2=A0<b>outside</b> China can&#39;t get the tri=
vial amounts of bandwidth required <strike>through their firewall</strike> =
<b>TO THE MAJORITY OF THE HASHRATE</b> and end up being outcompeted then OK=
, too bad, we&#39;ll have to carry on without them.<br></blockquote></div><=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jun 1, 201=
5 at 12:13 AM, Mike Hearn <span dir=3D"ltr">&lt;<a href=3D"mailto:mike@plan=
99.net" target=3D"_blank">mike@plan99.net</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">Whilst i=
t would be nice if miners in China can carry on forever regardless of their=
 internet situation, nobody has any inherent &quot;right&quot; to mine if t=
hey can&#39;t do the job - if miners in China can&#39;t get the trivial amo=
unts of bandwidth required through their firewall and end up being outcompe=
ted then OK, too bad, we&#39;ll have to carry on without them.</div><div cl=
ass=3D"gmail_extra"><br></div><div class=3D"gmail_extra">But I&#39;m not su=
re why it should be a big deal. They can always run a node on a server in T=
aiwan and connect the hardware to it via a VPN or so.</div></div>
<br>-----------------------------------------------------------------------=
-------<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=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>

--047d7bfe9b6e98f0c4051773f9d2--