Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of coinlab.com
	designates 209.85.216.169 as permitted sender)
	client-ip=209.85.216.169; envelope-from=peter@coinlab.com;
	helo=mail-qc0-f169.google.com; 
MIME-Version: 1.0
From: Peter Vessenes <peter@coinlab.com>
Date: Wed, 5 Jun 2013 17:19:16 -0700
Message-ID: <CAMGNxUv7wkiUYZ2nZjOP0mEW7bgR0a+CXKyDPq38joU-fMMQ9Q@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e01537ba4f4195e04de714436
Subject: [Bitcoin-development] Revocability with known trusted escrow
	services?
Precedence: list

--089e01537ba4f4195e04de714436
Content-Type: text/plain; charset=ISO-8859-1

So, this
http://www.americanbanker.com/bankthink/the-last-straw-for-bitcoin-1059608-1.html?pg=1
article got posted today, noting that FinCEN thinks irrevocable
payments
are money laundering tools.

I will hold my thoughts about the net social good of rent-seeking large
corporations taking money from consumers over fraudulent reversals.
Actually, I won't, I just said it.

At any rate, it got me thinking, can we layer on revocability somehow
without any protocol change, as an opt-in?

My initial scheme is a trusted (hah) escrow service that issues time
promises for signing. If it doesn't receive a cancel message, it will sign
at the end of the time.

The addresses would be listed by the escrow service, or in an open
registry, so you could see if you were going to have a delay period when
you saw a transaction go out.

This seems sort of poor to me, it imagines that mythical thing, a trusted
escrow service, and is vulnerable to griefing, but I thought I'd see if
some of the brighter minds than me can come up with a layer-on approach
here.

When I think about it, I can imagine that I would put a good number of my
coins in a one day reversible system, because I would have warning if
someone wanted to try and spend them, and could do something about it. I'm
not sure if it gets me anything over a standard escrow arrangement, though.

Peter

-- 

------------------------------

[image: CoinLab Logo]PETER VESSENES
CEO

*peter@coinlab.com * /  206.486.6856  / SKYPE: vessenes
71 COLUMBIA ST / SUITE 300  /  SEATTLE, WA 98104

--089e01537ba4f4195e04de714436
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">So, this <a href=3D"http://www.americanbanker.com/bankthin=
k/the-last-straw-for-bitcoin-1059608-1.html?pg=3D1">http://www.americanbank=
er.com/bankthink/the-last-straw-for-bitcoin-1059608-1.html?pg=3D1</a> =A0ar=
ticle got posted today, noting that FinCEN thinks irrevocable payments are =
money laundering tools.=A0<div>

<br></div><div>I will hold my thoughts about the net social good of rent-se=
eking large corporations taking money from consumers over fraudulent revers=
als. Actually, I won&#39;t, I just said it.<br><div><br></div><div>At any r=
ate, it got me thinking, can we layer on revocability somehow without any p=
rotocol change, as an opt-in?</div>

<div><br></div><div>My initial scheme is a trusted (hah) escrow service tha=
t issues time promises for signing. If it doesn&#39;t receive a cancel mess=
age, it will sign at the end of the time.=A0</div><div><br></div><div>The a=
ddresses would be listed by the escrow service, or in an open registry, so =
you could see if you were going to have a delay period when you saw a trans=
action go out.</div>

<div><br></div><div>This seems sort of poor to me, it imagines that mythica=
l thing, a trusted escrow service, and is vulnerable to griefing, but I tho=
ught I&#39;d see if some of the brighter minds than me can come up with a l=
ayer-on approach here.</div>

<div><br></div><div style>When I think about it, I can imagine that I would=
 put a good number of my coins in a one day reversible system, because I wo=
uld have warning if someone wanted to try and spend them, and could do some=
thing about it. I&#39;m not sure if it gets me anything over a standard esc=
row arrangement, though.</div>

<div style><br></div><div>Peter<br clear=3D"all"><div><br></div>-- <br><div=
 dir=3D"ltr"><br><hr style=3D"font-family:Times;font-size:medium;border-rig=
ht-width:0px;border-bottom-width:0px;border-left-width:0px;border-top-style=
:solid;border-top-color:rgb(204,204,204);margin:10px 0px">

<p style=3D"font-size:medium;font-family:Helvetica,sans-serif;line-height:1=
em"><span style=3D"color:rgb(50,90,135);text-transform:uppercase"><img src=
=3D"http://coinlab.com/static/images/email_logo.jpg" align=3D"right" alt=3D=
"CoinLab Logo" width=3D"130">PETER=A0<span style=3D"font-weight:bold">VESSE=
NES=A0</span><br>

<span style=3D"color:rgb(96,58,23);font-size:0.8em">CEO</span></span></p><p=
 style=3D"font-size:medium;font-family:Helvetica,sans-serif;line-height:1em=
"><span style=3D"color:rgb(96,58,23);font-size:0.9em"><strong><a href=3D"ma=
ilto:peter@coinlab.com" style=3D"text-decoration:none;color:rgb(96,58,23)" =
target=3D"_blank">peter@coinlab.com</a>=A0</strong>=A0/=A0=A0206.486.6856 =
=A0/=A0<span style=3D"font-size:0.7em;text-transform:uppercase">SKYPE:</spa=
n>=A0vessenes=A0</span><br>

<span style=3D"color:rgb(96,58,23);font-size:0.7em;text-transform:uppercase=
">71 COLUMBIA ST / SUITE 300 =A0/=A0 SEATTLE, WA 98104</span></p></div>
</div></div></div>

--089e01537ba4f4195e04de714436--