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 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.

 
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 ) id 1YzkLV-0008E4-Ly for bitcoin-development@lists.sourceforge.net; Tue, 02 Jun 2015 11:27:01 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.181 as permitted sender) client-ip=209.85.212.181; envelope-from=mh.in.england@gmail.com; helo=mail-wi0-f181.google.com; Received: from mail-wi0-f181.google.com ([209.85.212.181]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YzkLU-0003Sc-Ok for bitcoin-development@lists.sourceforge.net; Tue, 02 Jun 2015 11:27:01 +0000 Received: by wiwd19 with SMTP id d19so15842986wiw.0 for ; Tue, 02 Jun 2015 04:26:54 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.89.234 with SMTP id br10mr29981534wib.86.1433244414741; Tue, 02 Jun 2015 04:26:54 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.194.16.40 with HTTP; Tue, 2 Jun 2015 04:26:54 -0700 (PDT) In-Reply-To: References: Date: Tue, 2 Jun 2015 13:26:54 +0200 X-Google-Sender-Auth: _0O5T7L66XotI1yXqzV-_pBVIHM Message-ID: From: Mike Hearn To: cipher anthem Content-Type: multipart/alternative; boundary=e89a8f3ba2d537931605178738af X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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 X-Headers-End: 1YzkLU-0003Sc-Ok Cc: Bitcoin Dev 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:27:01 -0000 --e89a8f3ba2d537931605178738af Content-Type: text/plain; charset=UTF-8 > > 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. > Obviously if the majority of the mining hash rate is doing double spending attacks on exchanges then the Bitcoin experiment is resolved as a failure and it will become abandoned. This has been known since day one: it's in the white paper. The basic assumption behind Bitcoin is that only a minority of actors are dishonest - if the majority are then Satoshi's scheme does not work. So you are not stating anything new here. --e89a8f3ba2d537931605178738af Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

But the majority of the hashrate can now perfo= rm double spends on your chain! They can send bitcoins to exchanges, sell i= t, extract the money and build a new longer chain to get their bitcoins bac= k.

Obviously if th= e majority of the mining hash rate is doing double spending attacks on exch= anges then the Bitcoin experiment is resolved as a failure and it will beco= me abandoned. This has been known since day one: it's in the white pape= r. The basic assumption behind Bitcoin is that only a minority of actors ar= e dishonest - if the majority are then Satoshi's scheme does not work.<= /div>

So you are not stating anything new here.
--e89a8f3ba2d537931605178738af-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Yzkbt-000504-Hw for bitcoin-development@lists.sourceforge.net; Tue, 02 Jun 2015 11:43:57 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.177 as permitted sender) client-ip=209.85.212.177; envelope-from=nathan.cook@gmail.com; helo=mail-wi0-f177.google.com; Received: from mail-wi0-f177.google.com ([209.85.212.177]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Yzkbs-00056Z-Lm for bitcoin-development@lists.sourceforge.net; Tue, 02 Jun 2015 11:43:57 +0000 Received: by wikd7 with SMTP id d7so10680669wik.0 for ; Tue, 02 Jun 2015 04:43:50 -0700 (PDT) X-Received: by 10.180.86.198 with SMTP id r6mr30472544wiz.70.1433245430635; Tue, 02 Jun 2015 04:43:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.155.97 with HTTP; Tue, 2 Jun 2015 04:43:29 -0700 (PDT) In-Reply-To: References: From: Nathan Cook Date: Tue, 2 Jun 2015 14:43:29 +0300 Message-ID: To: Mike Hearn Content-Type: multipart/alternative; boundary=f46d04428c08c4e29705178774bb X-Spam-Score: -0.6 (/) 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 (nathan.cook[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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 X-Headers-End: 1Yzkbs-00056Z-Lm Cc: Bitcoin Dev 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:43:57 -0000 --f46d04428c08c4e29705178774bb Content-Type: text/plain; charset=UTF-8 On 2 June 2015 at 14:26, Mike Hearn wrote: > 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. >> > Obviously if the majority of the mining hash rate is doing double spending > attacks on exchanges then the Bitcoin experiment is resolved as a failure > and it will become abandoned. This has been known since day one: it's in > the white paper. The basic assumption behind Bitcoin is that only a > minority of actors are dishonest - if the majority are then Satoshi's > scheme does not work. > > So you are not stating anything new here. > It's both consistent and credible for an agent to commit to honesty on a chain that it openly supports and dishonesty on a chain that it openly opposes. (Moral? Legal? Perhaps not.) That said, majority hashpower doesn't need to be dishonest to stop a change to large blocks. It just needs to refuse to build on blocks that it doesn't like. The minority isn't going to mine blocks larger than 1MB if it knows they'll be orphaned. --f46d04428c08c4e29705178774bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On 2= June 2015 at 14:26, Mike Hearn <mike@plan99.net> wrote:

But the majority of the hashra= te can now perform double spends on your chain! They can send bitcoins to e= xchanges, sell it, extract the money and build a new longer chain to get th= eir bitcoins back.

Obviously if the majority of the mining hash rate is doing double s= pending attacks on exchanges then the Bitcoin experiment is resolved as a f= ailure and it will become abandoned. This has been known since day one: it&= #39;s in the white paper. The basic assumption behind Bitcoin is that only = a minority of actors are dishonest - if the majority are then Satoshi's= scheme does not work.

So you are not stating anyt= hing new here.
=C2=A0
I= t's both consistent and credible for an agent to commit to honesty on a= chain that it openly supports and dishonesty on a chain that it openly opp= oses. (Moral? Legal? Perhaps not.) That said, majority hashpower doesn'= t need to be dishonest to stop a change to large blocks. It just needs to r= efuse to build on blocks that it doesn't like. The minority isn't g= oing to mine blocks larger than 1MB if it knows they'll be orphaned.
--f46d04428c08c4e29705178774bb--