Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.220.175 as permitted sender)
	client-ip=209.85.220.175; envelope-from=mh.in.england@gmail.com;
	helo=mail-vx0-f175.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <201108111824.42807.andyparkins@gmail.com>
References: <CANEZrP2hvYst92u22c_41e9=izPCP7uv-RzVM4XSt7gxC99D0A@mail.gmail.com>
	<201108111824.42807.andyparkins@gmail.com>
Date: Fri, 12 Aug 2011 00:02:09 +0200
Message-ID: <CANEZrP1Dt9pqQ7-kj=DjPDi6zU83JgWqjRQa1t4SZt+CErxm9w@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andy Parkins <andyparkins@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Protocol changes
Precedence: list

> I can't say I see what the point of all that added complexity is, contrac=
ts
> are usually more than just financial

The term "contract" is sort of misleading, but there isn't a better
word for it. Satoshi called them contracts so that's what I call them
too.

http://en.bitcoin.it/wiki/Contracts

The point is to allow for lower trust in certain types of
transactions. For instance, consider Kickstarter. They allow people to
club together to fund the creation of new things, typically indie
movies and games. The problem is you need this trusted middleman to
collect peoples pledges and aggregate them. That adds fees, etc. With
contracts it can be done entirely with software, all the artist/game
programmer would need is to run some software on their website.

> What then allows the contract out of the memory pool into a chain? =C2=A0=
The
> locktime? =C2=A0No, no, forget it... I don't want to open a new can of wo=
rms.

;)

Lock time or if every sequence number is UINT_MAX.