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 1YzkEd-0006TI-L4 for bitcoin-development@lists.sourceforge.net; Tue, 02 Jun 2015 11:19:55 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmx.com designates 212.227.17.22 as permitted sender) client-ip=212.227.17.22; envelope-from=cipher.anthem@gmx.com; helo=mout.gmx.net; Received: from mout.gmx.net ([212.227.17.22]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1YzkEc-0003EZ-CI for bitcoin-development@lists.sourceforge.net; Tue, 02 Jun 2015 11:19:55 +0000 Received: from [188.138.9.49] by 3capp-mailcom-bs06.server.lan (via HTTP); Tue, 2 Jun 2015 13:19:48 +0200 MIME-Version: 1.0 Message-ID: From: "cipher anthem" To: bitcoin-development@lists.sourceforge.net Content-Type: text/html; charset=UTF-8 Date: Tue, 2 Jun 2015 13:19:48 +0200 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K0:N0LYg/yiFuLgh6xisWOhRmwlXR7qwzJaGn7z90fqRMP iybkLaPdIJYwSimPspsZjymaQ0hmtR2x1B3kJKMVOgxXvpYmEq Rv4Gb3sImsaBFpEV+BXgHW/zQ4blTdjOKOv+bf8QOUoq8JjyTZ d5sdBbRc6m7P9y/iqNUntftIXGp9/snHeUY/W+RwlE6lyH0pq+ 8QiAEk6XwcyJFKh2K1137e1/M9ChZ8iZcxveHQBQ3PXXAszMLc pTs8L0SEi70iqrjL9kpWw2P/v7t5tcy1EWInLIX0XW1T8Fo4c6 QsLuijvg1aUvtO/ZjSlAg8TX/GR X-UI-Out-Filterresults: notjunk:1;V01:K0:lJFuFGZJVSo=:ts2PcaiCnW/eIuZEndcfAf CnYKaQbU7TJlAy+RSWNS9YTUQLUZKKErlDw/L4reA/m1PtCwyO+vK8yWqDupP9TavgsF+YtOH +T10h9NHpvA2g7nY6iN6nAlHhpOszWek/ZubzcI8jcAEosP9fZbfixXn5HfAIb6dK5eiHRfWE 7ce7R/gIfaZCqBD35yzZjyu9yivKdXg9xsdwxBB0iH2KenUrTtDdQA0EPLnkxci40gkGtUF9I IeNUlUp7caXDdtVdFYX+5MAhujNkHPTleMRc75V3B9CI6ZjHRgZF0BIbiIy0RmUTSEhWzgFTx QNTL5++Y81NQI+1V9WqFGbMiK7Y0xaePWMFyL/mTKaB2+kP2RwOEvX4pxXzpXVMJmM+dIhV17 wn56pzOu/1RTpmvFK02406gb+r8gY0Zi88ALNmsOGB2swqj5TKaXlH8xnZAPHMLWG1I2Zcbfp pHDr2Yv2pw== X-Spam-Score: 1.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 (cipher.anthem[at]gmx.com) -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [212.227.17.22 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 2.3 MIME_HTML_ONLY BODY: Message only has text/html MIME parts X-Headers-End: 1YzkEc-0003EZ-CI Subject: Re: [Bitcoin-development] =?utf-8?q?Fwd=3A_Block_Size_Increase_Requir?= =?utf-8?b?ZW1lbnRz4oCP?= 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, 02 Jun 2015 11:19:55 -0000
>Then please enlighten me. You're unable to download block templates from a trusted node outside of the country because the bandwidth requirements are too high? Or due to some other problem? 
 
>With respect to "now it's your turn". Let's imagine the hard fork goes ahead. Let us assume that almost all exchanges, payment processors and other businesses go with larger blocks, but Chinese miners do not.
 
>Then you will mine coins that will not be recognised on trading platforms and cannot be sold. Your losses will be much larger than from orphans.
 
>This can happen even if Chinese miners who can't/won't scale up are >50% hashrate. SPV clients would need a forced checkpoint, which would be messy and undesirable, but it's technically feasible. The smaller side of the chain would cease to exist from the perspective of people actually trading coins.
 
>If your internet connectivity situation is really so poor that you cannot handle one or two megabits out of the country then you're hanging on by your fingernails anyway: your connection to the main internet could become completely unusable at any time. If that's really the case, it seems to me that Chinese Bitcoin is unsustainable and what you really need is a China-specific alt coin that can run entirely within the Chinese internet.

 

You claim that if all merchants, exchanges and users are moving to your chain then it will be the main chain even if it has less computational power.

But the majority of the hashrate can now perform double spends on your chain! They can send bitcoins to exchanges, sell it, extract the money and build a new longer chain to get their bitcoins back. Are companies like Xapo and Coinbase really so stupid that they would go along with this without complete consensus? I dont think so.

If the miners think that Bitcoin is doomed because of this change, then this is what they will do to maximize their profits.

But you could always roll back the blockchain to revert the double spend and have you and Gavin do a checkpoint on every block. Better yet just sign the blocks yourselves and you wont have to worry about that pesky mining!

Or you could change the hashing algortihm... Oh, but wait... so much capital has gone into the mining industry so this aint gonna happen.

The sheep of reddit who worships Gavin and Hearn really need to understand the importance of consensus...

Nothing of this is obviously going to happen, but just the fact that Mike suggests it is painful to watch.