From: Mustafa Al-Bassam <mus@musalbas•com>
To: "Jorge Timón" <jtimon@jtimon•cc>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 2 promotion to Final
Date: Thu, 10 Mar 2016 16:33:40 +0000 [thread overview]
Message-ID: <56E1A1E4.60908@musalbas.com> (raw)
In-Reply-To: <56E1A0BB.5090804@musalbas.com>
[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]
By the way, on that basis it might be a good idea to introduce an extra
status called "deployed" to indicate when a hard fork has reached a
super-majority and is being used by the economy in practice, but not the
whole economy.
On 10/03/16 16:28, Mustafa Al-Bassam wrote:
>
>
> On 10/03/16 15:59, Jorge Timón wrote:
>>
>>
>> On Mar 10, 2016 16:51, "Mustafa Al-Bassam via bitcoin-dev"
>> <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 try
>> > to be annoying about it and point to one instance of one buyer and one
>> > 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."
[-- Attachment #2: Type: text/html, Size: 2902 bytes --]
next prev parent reply other threads:[~2016-03-10 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 19:04 Luke Dashjr
2016-03-10 0:36 ` Mustafa Al-Bassam
2016-03-10 15:46 ` Jorge Timón
[not found] ` <56E0BFDC.5070604@musalbas.com>
[not found] ` <201603100053.43822.luke@dashjr.org>
2016-03-10 14:02 ` Mustafa Al-Bassam
2016-03-10 15:59 ` Jorge Timón
2016-03-10 16:28 ` Mustafa Al-Bassam
2016-03-10 16:33 ` Mustafa Al-Bassam [this message]
2016-03-10 18:30 ` Jorge Timón
2016-03-10 16:43 ` Luke Dashjr
2016-03-16 20:43 ` Btc Drak
2016-03-16 22:24 ` Luke Dashjr
2016-03-18 9:42 ` Btc Drak
2016-03-18 19:34 ` Luke Dashjr
2016-03-18 22:52 ` David A. Harding
2016-03-18 11:59 ` Tom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56E1A1E4.60908@musalbas.com \
--to=mus@musalbas$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jtimon@jtimon$(echo .)cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox