Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.98 as permitted sender)
	client-ip=62.13.148.98; envelope-from=pete@petertodd.org;
	helo=outmail148098.authsmtp.com; 
Date: Sat, 26 Apr 2014 14:31:19 -0400
From: Peter Todd <pete@petertodd.org>
To: Mike Hearn <mike@plan99.net>
Message-ID: <20140426183119.GB16440@savin>
References: <20140426112312.GA17949@savin>
	<CANEZrP3VpsW_RNWUpw-gsQhXqLF4deOJJPHxGJUc8Gx_y0B9wA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="LyciRD1jyfeSSjG0"
Content-Disposition: inline
In-Reply-To: <CANEZrP3VpsW_RNWUpw-gsQhXqLF4deOJJPHxGJUc8Gx_y0B9wA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>,
	Jeremy Spilman <jeremy.spilman@gmail.com>
Subject: Re: [Bitcoin-development] Eliminating double-spends with two-party
 self-escrow for high value transactions
Precedence: list


--LyciRD1jyfeSSjG0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 26, 2014 at 08:07:58PM +0200, Mike Hearn wrote:
> What stops the buyer just always waiting to get their money back?

The seller won't hand over the goods of course until they have a valid
transaction signed by the buyer sending them the escrowed funds. (and
the nLockTime deadline is sufficiently far away that the probability of
not being able to get the transaction mined in time is low)

Note how the mechanism I'm proposing is basically just a Jeremy
Spilman-style micropayment channel(1) used for a single payment; I
should have made that clear in my original post.

1) http://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/=
msg02028.html

--=20
'peter'[:-1]@petertodd.org
000000000000000069ea3b64f8b627bc81c8981ce80e95edf81cd356ad04e1a0

--LyciRD1jyfeSSjG0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQGrBAEBCACVBQJTW/tzXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDA1Y2I2MGVjY2QxNmI2MDdiZTE1N2JjYzhhZDc1MjA4MzM3
OTU1NjM2YzUxNzM2NDgvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkftcqwf+KdDBjtiPuUZGPMlVUoPtfDSi
emgO0+zhW79wOBWPIa2cG5kcDxz8EpY6C1CLu7Jyj2xjK3disHQHN6y5QmcPFIet
uWRcejLcVrylAlVLJ0NFEt4dKfK0Fr7L0zUKKaaUnfu9s8WiZxnEi/uYK1Et07hJ
UVeImQQiF3KC8oKavk5gBD5ng8iadqeS1KXWxbVe6a/v644Fl/N5FgOrcvnxhXUo
yXoyODJEHKW3YM3TgjdeBh0YD7iVAE+8h/E2JeZ44O8E8llV7A5KWZgOqDrZ0oAM
/wGx6jK2lxQ0ZoWesdZ23SMCowo9gj2crjZzXNgWaE3N1Qxl6KD0ApZgsOaa/w==
=NRaj
-----END PGP SIGNATURE-----

--LyciRD1jyfeSSjG0--