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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WmlAQ-0000vq-Rc for bitcoin-development@lists.sourceforge.net; Tue, 20 May 2014 14:37:22 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of leitl.org designates 164.177.174.8 as permitted sender) client-ip=164.177.174.8; envelope-from=eugen@leitl.org; helo=leitl.org; Received: from v8.ativel.com ([164.177.174.8] helo=leitl.org) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WmlAO-0004MW-2u for bitcoin-development@lists.sourceforge.net; Tue, 20 May 2014 14:37:22 +0000 Received: by leitl.org (Postfix, from userid 1000) id DB19F540022; Tue, 20 May 2014 16:37:10 +0200 (CEST) Date: Tue, 20 May 2014 16:37:10 +0200 From: Eugen Leitl To: bitcoin-development@lists.sourceforge.net Message-ID: <20140520143710.GT26986@leitl.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.5 (-) 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 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1WmlAO-0004MW-2u Subject: Re: [Bitcoin-development] Why are we bleeding nodes? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 14:37:23 -0000 On Tue, May 20, 2014 at 10:15:44AM +0200, bitcoingrant@gmx.com wrote: > Recently China has updated its firewall blocking bitcoin sites and p= ools. > Whether this is simple blacklist or more=C2=A0sophisticated=C2=A0pac= ket targeting is > uncertain, however this update did spefically target VPN handshakes. Could a blockchain fork due to network split happen? =C2=A0