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 1YLu5S-0001XT-1D for bitcoin-development@lists.sourceforge.net; Thu, 12 Feb 2015 13:45:46 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.178 as permitted sender) client-ip=209.85.212.178; envelope-from=alex.mizrahi@gmail.com; helo=mail-wi0-f178.google.com; Received: from mail-wi0-f178.google.com ([209.85.212.178]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YLu5Q-0002yQ-3p for bitcoin-development@lists.sourceforge.net; Thu, 12 Feb 2015 13:45:46 +0000 Received: by mail-wi0-f178.google.com with SMTP id em10so4394267wid.5 for ; Thu, 12 Feb 2015 05:45:38 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.187.236 with SMTP id fv12mr3579204wjc.131.1423748738066; Thu, 12 Feb 2015 05:45:38 -0800 (PST) Received: by 10.27.148.13 with HTTP; Thu, 12 Feb 2015 05:45:37 -0800 (PST) In-Reply-To: References: <20150212064719.GA6563@savin.petertodd.org> Date: Thu, 12 Feb 2015 15:45:37 +0200 Message-ID: From: Alex Mizrahi To: Bitcoin Dev Content-Type: multipart/alternative; boundary=047d7bea40ccc83036050ee455fc 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 (alex.mizrahi[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: 1YLu5Q-0002yQ-3p Subject: Re: [Bitcoin-development] replace-by-fee v0.10.0rc4 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: Thu, 12 Feb 2015 13:45:46 -0000 --047d7bea40ccc83036050ee455fc Content-Type: text/plain; charset=UTF-8 > Yes, like any P2P network Bitcoin cannot work if a sufficiently large > number of miners decide to attack it. > 1. They won't be attacking Bitcoin, they will attack merchants who accept payments with 0 confirmations. This attack has nothing to do with Bitcoin consensus mechanism (as Bitcoin protocol doesn't provide a consensus over mempool contents), thus it is not an attack on Bitcoin. 2. In the example I used, having 10% of hashpower is enough to offer 10% success rate. Would you mind having 1 out of 10 hamburgers for free? If a system can be attacked by a tiny fraction, it is a shitty system. --047d7bea40ccc83036050ee455fc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
=C2=A0
Yes, like any P2P network Bitc= oin cannot work if a sufficiently large number of miners decide to attack i= t.

1. They won'= t be attacking Bitcoin, they will attack merchants who accept payments with= 0 confirmations. This attack has nothing to do with Bitcoin consensus mech= anism (as Bitcoin protocol doesn't provide a consensus over mempool con= tents), thus it is not an attack on Bitcoin.
2. In the example I = used, having 10% of hashpower is enough to offer 10% success rate. Would yo= u mind having 1 out of 10 hamburgers for free? If a system can be attacked = by a tiny fraction, it is a shitty system.
--047d7bea40ccc83036050ee455fc--