Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1YxjLy-00080x-44
	for bitcoin-development@lists.sourceforge.net;
	Wed, 27 May 2015 21:59:10 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.46 as permitted sender)
	client-ip=74.125.82.46; envelope-from=mh.in.england@gmail.com;
	helo=mail-wg0-f46.google.com; 
Received: from mail-wg0-f46.google.com ([74.125.82.46])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YxjLw-0004bS-G6
	for bitcoin-development@lists.sourceforge.net;
	Wed, 27 May 2015 21:59:10 +0000
Received: by wgez8 with SMTP id z8so21084852wge.0
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 27 May 2015 14:59:02 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.157.168 with SMTP id wn8mr47543653wjb.79.1432763942425; 
	Wed, 27 May 2015 14:59:02 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.194.143.9 with HTTP; Wed, 27 May 2015 14:59:02 -0700 (PDT)
In-Reply-To: <CANEZrP2x+fBitgcvoaC2qBbJS-Ek_hgS3ZGM55UtURKc-oDZMQ@mail.gmail.com>
References: <5550D8BE.6070207@electrum.org>
	<CANEZrP2x+fBitgcvoaC2qBbJS-Ek_hgS3ZGM55UtURKc-oDZMQ@mail.gmail.com>
Date: Wed, 27 May 2015 23:59:02 +0200
X-Google-Sender-Auth: yIuN_RnBaX7ottbN_gwjDTMyLXc
Message-ID: <CANEZrP0ZdGp6Punh34mNMgaukHDQvMwDM_KEEsnuHn8Fj3Pt2Q@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Thomas Voegtlin <thomasv@electrum.org>
Content-Type: multipart/alternative; boundary=089e0122e968d5daf70517175908
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: 1YxjLw-0004bS-G6
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
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: <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, 27 May 2015 21:59:10 -0000

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

I wrote an article that explains the hashing assurance contract concept:

https://medium.com/@octskyward/hashing-7d04a887acc8

(it doesn't contain an in depth protocol description)

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

<div dir=3D"ltr">I wrote an article that explains the hashing assurance con=
tract concept:<div><br></div><div><a href=3D"https://medium.com/@octskyward=
/hashing-7d04a887acc8">https://medium.com/@octskyward/hashing-7d04a887acc8<=
/a><br></div><div><br></div><div>(it doesn&#39;t contain an in depth protoc=
ol description)</div></div>

--089e0122e968d5daf70517175908--