Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1Wd233-0005om-D1
	for bitcoin-development@lists.sourceforge.net;
	Wed, 23 Apr 2014 18:37:33 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.173 as permitted sender)
	client-ip=209.85.214.173; envelope-from=mh.in.england@gmail.com;
	helo=mail-ob0-f173.google.com; 
Received: from mail-ob0-f173.google.com ([209.85.214.173])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Wd232-0003lE-HM
	for bitcoin-development@lists.sourceforge.net;
	Wed, 23 Apr 2014 18:37:33 +0000
Received: by mail-ob0-f173.google.com with SMTP id wn1so1489345obc.32
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 23 Apr 2014 11:37:27 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.85.193 with SMTP id j1mr13805445obz.52.1398278247137;
	Wed, 23 Apr 2014 11:37:27 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Wed, 23 Apr 2014 11:37:27 -0700 (PDT)
In-Reply-To: <53580452.3030705@gmail.com>
References: <CANEZrP0szimdFSk23aMfO8p2Xtgfbm6kZ=x3rmdPDFUD73xHMg@mail.gmail.com>
	<5357D394.7010908@gmail.com>
	<CANEZrP0dxAOWxg8Nu9LqV1SGE1C1WD2m+EPhg3sFCnFQQVv4kQ@mail.gmail.com>
	<5357F634.2070300@gmail.com>
	<CABsx9T12e7rbbza9XFi1EY20+0xciWXMiXrOHjTMdj=7Pzsrxw@mail.gmail.com>
	<5357FD32.40200@gmail.com>
	<CANEZrP3JV2sCK7-4P40wh9EXQfn2GCc3D=095wCo75Wh0LvMBQ@mail.gmail.com>
	<535800C1.9060604@gmail.com> <20140423181545.GA5434@savin>
	<53580452.3030705@gmail.com>
Date: Wed, 23 Apr 2014 20:37:27 +0200
X-Google-Sender-Auth: kpnCSytSR_ZxG4DPOwmbzYz6PAE
Message-ID: <CANEZrP1dP3m79bUfgWqi3XZVgnKEW7KoKjBvYSwcQD785QZxGg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Justus Ranvier <justusranvier@gmail.com>
Content-Type: multipart/alternative; boundary=089e01229a1237c6e304f7ba0682
X-Spam-Score: -0.5 (/)
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
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	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: 1Wd232-0003lE-HM
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Coinbase reallocation to discourage
	Finney attacks
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 18:37:33 -0000

--089e01229a1237c6e304f7ba0682
Content-Type: text/plain; charset=UTF-8

If you want to try and argue that the development list is the wrong place
to discuss development, please do so on another thread (or your blog).
Let's keep this thread for discussion of the original proposal - ideally,
discussed with the dryness that a topic as nerdy as distributed consensus
algorithms deserves ;)

--089e01229a1237c6e304f7ba0682
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">If you want to try and argue that the development list is =
the wrong place to discuss development, please do so on another thread (or =
your blog). Let&#39;s keep this thread for discussion of the original propo=
sal - ideally, discussed with the dryness that a topic as nerdy as distribu=
ted consensus algorithms deserves ;)</div>

--089e01229a1237c6e304f7ba0682--