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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Vdln6-0006Lf-TL for bitcoin-development@lists.sourceforge.net; Tue, 05 Nov 2013 18:55:52 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.178 as permitted sender) client-ip=74.125.82.178; envelope-from=startithub@gmail.com; helo=mail-we0-f178.google.com; Received: from mail-we0-f178.google.com ([74.125.82.178]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Vdln5-00025n-Uy for bitcoin-development@lists.sourceforge.net; Tue, 05 Nov 2013 18:55:52 +0000 Received: by mail-we0-f178.google.com with SMTP id q59so3851444wes.37 for ; Tue, 05 Nov 2013 10:55:45 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.21.131 with SMTP id v3mr7987758wje.44.1383677745727; Tue, 05 Nov 2013 10:55:45 -0800 (PST) Received: by 10.216.208.67 with HTTP; Tue, 5 Nov 2013 10:55:45 -0800 (PST) In-Reply-To: References: <20131105170541.GA13660@petertodd.org> <20131105171445.GA13710@petertodd.org> Date: Tue, 5 Nov 2013 19:55:45 +0100 Message-ID: From: Alessandro Parisi To: Jeff Garzik Content-Type: multipart/alternative; boundary=047d7b5d64f2848fdc04ea729418 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 (startithub[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: bitpay.com] 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: 1Vdln5-00025n-Uy Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] BIP proposal - patch to raise selfish mining threshold. 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, 05 Nov 2013 18:55:53 -0000 --047d7b5d64f2848fdc04ea729418 Content-Type: text/plain; charset=ISO-8859-1 Thank you very much for your fair response, Sir; this means that anytime a bug is found in Bitcoin protocol, chances are that it would take a lot more time to get fixed 2013/11/5 Jeff Garzik > On Tue, Nov 5, 2013 at 1:07 PM, Alessandro Parisi > wrote: > > I agree with Ittay: when bugs are found, they must be fixed ASAP, > expecially > > when they affect a sensitive sw such as Bitcon; in IT security, every > flaw > > that is exploitable in abstract, is going to be exploited in real, > sooner or > > later, also taking into account the increasing parallel computing power; > > beware of false sense of security > > That is quite ignorant. Bitcoin is far more complex than standard IT > security "fix ASAP" mantra. Distributed consensus is a new field of > computer science, and blindly applying standard logic to bitcoin will > quickly result in large problems. > > Every fix has the chance of changing the game theory or economics of > bitcoin. A change to the core consensus protocol within bitcoin -- > mining -- is even more game-theory- and economically-critical to the > core system. Changes thus have more impact, where any change > potentially reduces bitcoin's value to zero in the worst case. > > Bitcoin is akin to medical device or avionics software. We cannot > just change at will, without significant research, analysis and > testing. "It is a bug, it must be fixed ASAP" is ignorant and > dangerous. > > Further, this is at present a THEORETICAL problem, and the solution > presented has some obvious flaws, that would make our current, WORKING > SYSTEM more fragile, and less secure. > > -- > Jeff Garzik > Senior Software Engineer and open source evangelist > BitPay, Inc. https://bitpay.com/ > --047d7b5d64f2848fdc04ea729418 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thank you very much for your fair response, Sir;
this means that anytime a bug is found in Bitcoin protocol, chances are th= at it would take a lot more time to get fixed


2013/11/5 Jeff Garzik = <jgarzik@bitpay.= com>
On Tue, Nov 5, 2013 at 1:07 PM, Alessandro Parisi <startithub@gmail.com> wrote: > I agree with Ittay: when bugs are found, they must be fixed ASAP, expe= cially
> when they affect a sensitive sw such as Bitcon; in IT security, every = flaw
> that is exploitable in abstract, is going to be exploited in real, soo= ner or
> later, also taking into account the increasing parallel computing powe= r;
> beware of false sense of security

That is quite ignorant. =A0Bitcoin is far more complex than standard = IT
security "fix ASAP" mantra. =A0Distributed consensus is a new fie= ld of
computer science, and blindly applying standard logic to bitcoin will
quickly result in large problems.

Every fix has the chance of changing the game theory or economics of
bitcoin. =A0A change to the core consensus protocol within bitcoin --
mining -- is even more game-theory- and economically-critical to the
core system. =A0Changes thus have more impact, where any change
potentially reduces bitcoin's value to zero in the worst case.

Bitcoin is akin to medical device or avionics software. =A0We cannot
just change at will, without significant research, analysis and
testing. =A0 "It is a bug, it must be fixed ASAP" is ignorant and=
dangerous.

Further, this is at present a THEORETICAL problem, and the solution
presented has some obvious flaws, that would make our current, WORKING
SYSTEM more fragile, and less secure.

--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. =A0 =A0 =A0h= ttps://bitpay.com/

--047d7b5d64f2848fdc04ea729418--