+Return-Path: <mus@musalbas.com>

+Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org

+ [172.17.192.35])

+ by mail.linuxfoundation.org (Postfix) with ESMTPS id 4F2F8D04

+ for <bitcoin-dev@lists.linuxfoundation.org>;

+ Thu, 10 Mar 2016 16:28:47 +0000 (UTC)

+X-Greylist: from auto-whitelisted by SQLgrey-1.7.6

+Received: from science.musalbas.com (science.musalbas.com [195.154.112.130])

+ by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6FBEC14F

+ for <bitcoin-dev@lists.linuxfoundation.org>;

+ Thu, 10 Mar 2016 16:28:46 +0000 (UTC)

+Received: from [10.7.0.6] (unknown [10.7.0.6])

+ (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))

+ (Client did not present a certificate)

+ by science.musalbas.com (Postfix) with ESMTPSA id B977D6A09B2;

+ Thu, 10 Mar 2016 16:28:44 +0000 (UTC)

+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=musalbas.com;

+ s=mail; t=1457627324;

+ bh=YwHvO8vZFgdxInb7rRi+KQj4mXNZmKK8aidnKQyDUV4=;

+ h=Subject:To:References:Cc:From:Date:In-Reply-To;

+ b=Hpot8kMOsnlxQT4Zr748wiZueMvACoK2GbVevLr8x9uK/mhVKJIcAXAZMZIkQuh6C

+ xzQWuZdHS5MX0D6+jMCgXkwicyYwKvnh0/ZgsZtD29EwWMQ9iRxuhsyyxB4322Sw81

+ GjMPiIYbkTeqRZUqVHIFf1FYPUKfATl4vdDU6jxU=

+To: =?UTF-8?Q?Jorge_Tim=c3=b3n?= <jtimon@jtimon.cc>

+References: <201603081904.28687.luke@dashjr.org>

+ <56E0BFDC.5070604@musalbas.com> <201603100053.43822.luke@dashjr.org>

+ <56E17E67.9040508@musalbas.com>

+ <CABm2gDogqtOkgtjWNY6vD_Cu=dnoATtLHBS+-E8BtrNTOsPCSg@mail.gmail.com>

+From: Mustafa Al-Bassam <mus@musalbas.com>

+Message-ID: <56E1A0BB.5090804@musalbas.com>

+Date: Thu, 10 Mar 2016 16:28:43 +0000

+User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101

+ Thunderbird/38.6.0

+MIME-Version: 1.0

+In-Reply-To: <CABm2gDogqtOkgtjWNY6vD_Cu=dnoATtLHBS+-E8BtrNTOsPCSg@mail.gmail.com>

+Content-Type: multipart/alternative;

+ boundary="------------010002040201090205090108"

+X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,

+ DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,RP_MATCHES_RCVD autolearn=ham

+ version=3.3.1

+X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on

+ smtp1.linux-foundation.org

+X-Mailman-Approved-At: Thu, 10 Mar 2016 16:33:13 +0000

+Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>

+Subject: Re: [bitcoin-dev] BIP 2 promotion to Final

+X-BeenThere: bitcoin-dev@lists.linuxfoundation.org

+X-Mailman-Version: 2.1.12

+Precedence: list

+List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>

+List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,

+ <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>

+List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>

+List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>

+List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>

+List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,

+ <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>

+X-List-Received-Date: Thu, 10 Mar 2016 16:28:47 -0000

+

+This is a multi-part message in MIME format.

+--------------010002040201090205090108

+Content-Type: text/plain; charset=utf-8

+Content-Transfer-Encoding: quoted-printable

+

+

+

+On 10/03/16 15:59, Jorge Tim=C3=B3n wrote:

+>

+>

+> On Mar 10, 2016 16:51, "Mustafa Al-Bassam via bitcoin-dev"

+> <bitcoin-dev@lists.linuxfoundation.org

+> <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:

+>

+> > I think in general this sounds like a good definition for a hard-fork=

+

+> > becoming active. But I can envision a situation where someone will tr=

+y

+> > to be annoying about it and point to one instance of one buyer and on=

+e

+> > seller using the blockchain to buy and sell from each other, or set

+> one up.

+>

+> And all the attacker will achieve is preventing a field on a text file

+> on github from moving from "active" to "final".

+> Seems pretty stupid. Why would an attacker care so much about this? Is

+> there any way the attacker can make gains or harm bitcoin with this

+> attack?

+>

+It's extremely naive to think that just because you can't think of an

+incentive for a reason for an attack to do this, an attacker will never

+to do this. There are many people that would be willing to spend some

+time to cause some trouble for the enjoyment of it, if the attack is

+free to execute.

+

+The fact that it takes very little time and effort to prevent a BIP from

+reaching final status, means that in an base of millions of users it's

+guaranteed that some disgruntled or bored person out there will attack

+it, even if it's for the lulz.

+

+To reasonably expect that any hark fork - including an uncontroversial

+one - will be adapted by every single person in a ecosystem of millions

+of people, is wishful thinking and the BIP may as well say "hard fork

+BIPs shall never reach final status."

+

+--------------010002040201090205090108

+Content-Type: text/html; charset=utf-8

+Content-Transfer-Encoding: 8bit

+

+<html>

+ <head>

+ <meta content="text/html; charset=utf-8" http-equiv="Content-Type">

+ </head>

+ <body bgcolor="#FFFFFF" text="#000000">

+ <br>

+ <br>

+ <div class="moz-cite-prefix">On 10/03/16 15:59, Jorge Timón wrote:<br>

+ </div>

+ <blockquote

+cite="mid:CABm2gDogqtOkgtjWNY6vD_Cu=dnoATtLHBS+-E8BtrNTOsPCSg@mail.gmail.com"

+ type="cite">

+ <p dir="ltr"><br>

+ On Mar 10, 2016 16:51, "Mustafa Al-Bassam via bitcoin-dev" &lt;<a

+ moz-do-not-send="true"

+ href="mailto:bitcoin-dev@lists.linuxfoundation.org"><a class="moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a></a>&gt;

+ wrote:</p>

+ <p dir="ltr">&gt; I think in general this sounds like a good

+ definition for a hard-fork<br>

+ &gt; becoming active. But I can envision a situation where

+ someone will try<br>

+ &gt; to be annoying about it and point to one instance of one

+ buyer and one<br>

+ &gt; seller using the blockchain to buy and sell from each

+ other, or set one up.</p>

+ <p dir="ltr">And all the attacker will achieve is preventing a

+ field on a text file on github from moving from "active" to

+ "final". <br>

+ Seems pretty stupid. Why would an attacker care so much about

+ this? Is there any way the attacker can make gains or harm

+ bitcoin with this attack?</p>

+ </blockquote>

+ It's extremely naive to think that just because you can't think of

+ an incentive for a reason for an attack to do this, an attacker will

+ never to do this. There are many people that would be willing to

+ spend some time to cause some trouble for the enjoyment of it, if

+ the attack is free to execute.<br>

+ <br>

+ The fact that it takes very little time and effort to prevent a BIP

+ from reaching final status, means that in an base of millions of

+ users it's guaranteed that some disgruntled or bored person out

+ there will attack it, even if it's for the lulz.<br>

+ <br>

+ To reasonably expect that any hark fork - including an

+ uncontroversial one - will be adapted by every single person in a

+ ecosystem of millions of people, is wishful thinking and the BIP may

+ as well say "hard fork BIPs shall never reach final status."<br>

+ </body>

+</html>

+

+--------------010002040201090205090108--

+