Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YsYmi-00082R-1C for bitcoin-development@lists.sourceforge.net; Wed, 13 May 2015 15:41:24 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.54 as permitted sender) client-ip=209.85.215.54; envelope-from=gavinandresen@gmail.com; helo=mail-la0-f54.google.com; Received: from mail-la0-f54.google.com ([209.85.215.54]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YsYmh-0007Ju-4F for bitcoin-development@lists.sourceforge.net; Wed, 13 May 2015 15:41:24 +0000 Received: by layy10 with SMTP id y10so32454876lay.0 for ; Wed, 13 May 2015 08:41:16 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.97.202 with SMTP id ec10mr6434595lbb.4.1431531676734; Wed, 13 May 2015 08:41:16 -0700 (PDT) Received: by 10.25.90.75 with HTTP; Wed, 13 May 2015 08:41:16 -0700 (PDT) In-Reply-To: References: <5550D8BE.6070207@electrum.org> <5551F376.4050008@electrum.org> <555210AF.3090705@electrum.org> Date: Wed, 13 May 2015 11:41:16 -0400 Message-ID: From: Gavin Andresen To: Adam Back Content-Type: multipart/alternative; boundary=001a1133b1c4139beb0515f871d1 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 (gavinandresen[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: 1YsYmh-0007Ju-4F Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Long-term mining incentives 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: Wed, 13 May 2015 15:41:24 -0000 --001a1133b1c4139beb0515f871d1 Content-Type: text/plain; charset=UTF-8 On Tue, May 12, 2015 at 7:48 PM, Adam Back wrote: > I think its fair to say no one knows how to make a consensus that > works in a decentralised fashion that doesnt weaken the bitcoin > security model without proof-of-work for now. > Yes. > I am presuming Gavin is just saying in the context of not pre-judging > the future that maybe in the far future another innovation might be > found (or alternatively maybe its not mathematically possible). > Yes... or an alternative might be found that weakens the Bitcoin security model by a small enough amount that it either doesn't matter or the weakening is vastly overwhelmed by some other benefit. I'm influenced by the way the Internet works; packets addressed to 74.125.226.67 reliably get to Google through a very decentralized system that I'll freely admit I don't understand. Yes, a determined attacker can re-route packets, but layers of security on top means re-routing packets isn't enough to pull off profitable attacks. I think Bitcoin's proof-of-work might evolve in a similar way. Yes, you might be able to 51% attack the POW, but layers of security on top of POW will mean that won't be enough to pull off profitable attacks. -- -- Gavin Andresen --001a1133b1c4139beb0515f871d1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, May 12, 2015 at 7:48 PM, Adam Back <adam@cypherspace.org> wrote:
I think its fair to say no one knows how to= make a consensus that
works in a decentralised fashion that doesnt weaken the bitcoin
security model without proof-of-work for now.

Yes.
=C2=A0
I am presuming Gavin i= s just saying in the context of not pre-judging
the future that maybe in the far future another innovation might be
found (or alternatively maybe its not mathematically possible).

Yes... or an alternative might be found that weake= ns the Bitcoin security model by a small enough amount that it either doesn= 't matter or the weakening is vastly overwhelmed by some other benefit.=

I'm influenced by the way the Internet works;= packets addressed to 74.125.226.67 reliably get to Google through a very d= ecentralized system that I'll freely admit I don't understand. Yes,= a determined attacker can re-route packets, but layers of security on top = means re-routing packets isn't enough to pull off profitable attacks.

I think Bitcoin's proof-of-work might evolve in= a similar way. Yes, you might be able to 51% attack the POW, but layers of= security on top of POW will mean that won't be enough to pull off prof= itable attacks.


--
--
Gavin Andresen

--001a1133b1c4139beb0515f871d1--