Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of lavabit.com
	designates 72.249.41.33 as permitted sender)
	client-ip=72.249.41.33; envelope-from=bgroff@lavabit.com;
	helo=karen.lavabit.com; 
Message-ID: <18440.87.106.138.84.1308200020.squirrel@lavabit.com>
Date: Thu, 16 Jun 2011 00:53:40 -0400 (EDT)
From: bgroff@lavabit.com
To: bitcoin-development@lists.sourceforge.net
User-Agent: SquirrelMail/1.4.13
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [Bitcoin-development] [PULL] Add scriptPubKey enforced sendescrow
 and redeemescrow API calls
Precedence: list

I have a pull request here:

https://github.com/bitcoin/bitcoin/pull/319

From the README:

  Bitcoin "escrow" are coins that are under the control of multiple
  parties.  The initial implementation allows n parties to vote, with
  k good signatures needed (k <=3D n).

  This eliminates single points of failure and reduces the trust required
  in many transaction use cases.

Use cases include Escrow (without trusting the escrow agent with the
coins), immediate payment and funds locked with multi-party signatures.

This was inspired by https://forum.bitcoin.org/index.php?topic=3D8821.0 a=
nd
https://forum.bitcoin.org/index.php?topic=3D4723.msg68804 .

Feedback on the pull is very much appreciated.