From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <pete@petertodd.org>) id 1We8Qa-00013b-Q7
	for bitcoin-development@lists.sourceforge.net;
	Sat, 26 Apr 2014 19:38:24 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.82 as permitted sender)
	client-ip=62.13.149.82; envelope-from=pete@petertodd.org;
	helo=outmail149082.authsmtp.co.uk; 
Received: from outmail149082.authsmtp.co.uk ([62.13.149.82])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1We8QY-0002uY-QV for bitcoin-development@lists.sourceforge.net;
	Sat, 26 Apr 2014 19:38:24 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
	by punt14.authsmtp.com (8.14.2/8.14.2) with ESMTP id s3QJcFfp016739; 
	Sat, 26 Apr 2014 20:38:15 +0100 (BST)
Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109])
	(authenticated bits=128)
	by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s3QJc95w094189
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Sat, 26 Apr 2014 20:38:12 +0100 (BST)
Date: Sat, 26 Apr 2014 15:37:59 -0400
From: Peter Todd <pete@petertodd.org>
To: Mike Hearn <mike@plan99.net>
Message-ID: <20140426193759.GC16440@savin>
References: <20140426112312.GA17949@savin>
	<CANEZrP3VpsW_RNWUpw-gsQhXqLF4deOJJPHxGJUc8Gx_y0B9wA@mail.gmail.com>
	<20140426183119.GB16440@savin>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="jy6Sn24JjFx/iggw"
Content-Disposition: inline
In-Reply-To: <20140426183119.GB16440@savin>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 4dd3914c-cd7a-11e3-b802-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
	http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
	aQdMdAQUGUUGAgsB AmIbWVReU1V7WGE7 bAxPbAVDY01GQQRq
	WVdMSlVNFUsrAn17 VRcbFRl7cwROcTBx Z05mWj5fCBB5fEd5
	EVMHQWpXeGZhPWMC AkhYdR5UcAFPdx8U a1UrBXRDAzANdhES
	HhM4ODE3eDlSNilR RRkIIFQOdA4mGj85 RhYLATQpEgUJQDg5
	KxFjMUYRGkoKeloz LVtpRU0fdgcbEBFP fQlWDStXYlQaTDAs
	EktUWlRWEDxSQW9C Cxk1L1dUGDVUQSNT GEpCTQpn
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 76.10.178.109/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
	anti-virus system.
X-Spam-Score: -1.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 SPF_PASS               SPF: sender matches SPF record
X-Headers-End: 1We8QY-0002uY-QV
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
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: Sat, 26 Apr 2014 19:38:24 -0000


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

On Sat, Apr 26, 2014 at 02:31:19PM -0400, Peter Todd wrote:
> 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?
>=20
> 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)
>=20
> 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.
>=20
> 1) http://www.mail-archive.com/bitcoin-development%40lists.sourceforge.ne=
t/msg02028.html

I swear, I'm getting alzheimers or something. This and stealth addresses
is now the second time I've totally forgotten I had just read an idea a
week prior:

Reddit user RubenSomsen, ten days ago:

"I would really like it if Mycelium allowed me to temporarily lock my
bitcoins in a 2-of-2 transaction with a potential buyer (of course with
nlocktime back to myself) so the network can start confirming the
transaction before we even meet."
-http://www.reddit.com/r/Bitcoin/comments/236k5d/mycelium_local_trader_is_n=
ow_available/cgtxede

Better explanation than mine too for someone wanting a quick intro.

--=20
'peter'[:-1]@petertodd.org
000000000000000038a12e1b8bc9562cddc5cfa24ba7c418f4b945f6b1677e41

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

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

iQGrBAEBCACVBQJTXAsRXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAzOGExMmUxYjhiYzk1NjJjZGRjNWNmYTI0YmE3YzQxOGY0
Yjk0NWY2YjE2NzdlNDEvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfvoVgf+MqAXu7OrhXh3xNtWFAGmGq6R
VEQyeJN9QY4k8FRAvkafAOaoF5CDRgyHrO8QBiVa699UTFYlruRleyTS5Gf94OUp
oYkI6OK4Y5jg4KSAvrBJUkaxaMwuFltxx0sXlYj1AJAB1ayy10zJj7W1RYQuYOzz
wvnHPtDiFmDlxijJpkKMd4e9PndVZM5lmVU1g3ayGl+8HwKMND3jmlv6Td/o0Nsh
euMVmhlp2C2y/prfeizXkAK6sApdj39lnHziJQ6guJGjhKecIUvVR6vzqhiD7uRL
Qs3QXmu93bBAjLfX6swALRW+yJrD/9HiJSERqRFIwX2IbUbHBL9jYu7BEpmKLw==
=KWod
-----END PGP SIGNATURE-----

--jy6Sn24JjFx/iggw--