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 1RBTE1-00014B-7Z
	for Bitcoin-development@lists.sourceforge.net;
	Wed, 05 Oct 2011 15:17:37 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.53 as permitted sender)
	client-ip=74.125.82.53; envelope-from=mh.in.england@gmail.com;
	helo=mail-ww0-f53.google.com; 
Received: from mail-ww0-f53.google.com ([74.125.82.53])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1RBTE0-00061X-GE
	for Bitcoin-development@lists.sourceforge.net;
	Wed, 05 Oct 2011 15:17:37 +0000
Received: by wwg14 with SMTP id 14so2359245wwg.10
	for <Bitcoin-development@lists.sourceforge.net>;
	Wed, 05 Oct 2011 08:17:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.47.11 with SMTP id s11mr3028260web.24.1317827850327; Wed,
	05 Oct 2011 08:17:30 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.216.137.17 with HTTP; Wed, 5 Oct 2011 08:17:30 -0700 (PDT)
In-Reply-To: <CAPfzCrS87dJwHC=HQAVcfm8Fm9r5LdENg5s9JUnLuZr+sgh+jg@mail.gmail.com>
References: <CAPfzCrS87dJwHC=HQAVcfm8Fm9r5LdENg5s9JUnLuZr+sgh+jg@mail.gmail.com>
Date: Wed, 5 Oct 2011 17:17:30 +0200
X-Google-Sender-Auth: B3RVZQsquAL-lNy4BfvnphxJL2s
Message-ID: <CANEZrP02QiScfqWWBR7jNjZ9nDT7KkWuzK4Ua9NtVEwyiDAWKA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Brian McQueen <mcqueenorama@gmail.com>
Content-Type: multipart/alternative; boundary=001485f1bdc4e4d5ac04ae8eb4e0
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: 1RBTE0-00061X-GE
Cc: Bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Transaction Delivery and Storage
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, 05 Oct 2011 15:17:37 -0000

--001485f1bdc4e4d5ac04ae8eb4e0
Content-Type: text/plain; charset=UTF-8

I imagine a lot of the things on the contracts page will be implemented by
specialized software that interacts with the Bitcoin network directly.
Transactions would then be moved around, for example, by having clients do
HTTP POSTs of protocol buffers to servers that are listening and know how to
interpret the received messages.

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

<div class=3D"gmail_quote">I imagine a lot of the things on the contracts p=
age will be implemented by specialized software that interacts with the Bit=
coin network directly. Transactions would then be moved around, for example=
, by having clients do HTTP POSTs of protocol buffers to servers that are l=
istening and know how to interpret the received messages.</div>

--001485f1bdc4e4d5ac04ae8eb4e0--