summaryrefslogtreecommitdiff
path: root/51/eee57e4cbd0d73c270f1bf566d68041586e927
blob: b1cb2a58d900585ada3cc07dd7a74fa4a7ceb86d (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mark@monetize.io>) id 1Ukelg-0004mD-O4
	for bitcoin-development@lists.sourceforge.net;
	Thu, 06 Jun 2013 18:18:36 +0000
Received: from mail-oa0-f51.google.com ([209.85.219.51])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Ukelf-0005np-0T
	for bitcoin-development@lists.sourceforge.net;
	Thu, 06 Jun 2013 18:18:36 +0000
Received: by mail-oa0-f51.google.com with SMTP id f4so2497904oah.38
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 06 Jun 2013 11:18:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:x-enigmail-version:content-type
	:x-gm-message-state;
	bh=P2+EkCfHyUJ1bIP2KL12gb3cIRHpdXFWWv0MXRXyj58=;
	b=g9J08PIeZkh3gzabaSzrlFDjeSyli0zFrCdw2YalYi7oXOLp97MvbnxPE3ETdWv6ga
	atYf0Z6yiD2vw252ThKZy5mnh6Go0BEHH1Aaq6C/ZPmTur08IMhCl8lgHoXCpRRkTrrI
	k5ZYdmEVVXDcYPtm6J+1r7afFr/5lc9KFWsEUzLx4qtffMGJl4CtEQtwKQ9oiSzGerb/
	JfjVtM0AAWWElgybFAHHCpdNmVYUjLKO0EW6LAgMsDi7sgwYaawtYXT0Hi/lL/fJXxmB
	GrxZCZkHE7nwegQtOPCLCaQkj4qNDM3qFmnVrpCFLg0tfdTvX8d6lMUp4rdBVXoxLFHs
	GurA==
X-Received: by 10.182.24.131 with SMTP id u3mr19351337obf.29.1370542709337;
	Thu, 06 Jun 2013 11:18:29 -0700 (PDT)
Received: from [192.168.1.118] (adsl-71-131-181-199.dsl.sntc01.pacbell.net.
	[71.131.181.199])
	by mx.google.com with ESMTPSA id z5sm59263855obw.4.2013.06.06.11.18.27
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 06 Jun 2013 11:18:28 -0700 (PDT)
Message-ID: <51B0D272.5000304@monetize.io>
Date: Thu, 06 Jun 2013 11:18:26 -0700
From: Mark Friedenbach <mark@monetize.io>
Organization: Monetize.io Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
	rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Peter Vessenes <peter@coinlab.com>
References: <CAMGNxUv7wkiUYZ2nZjOP0mEW7bgR0a+CXKyDPq38joU-fMMQ9Q@mail.gmail.com>
In-Reply-To: <CAMGNxUv7wkiUYZ2nZjOP0mEW7bgR0a+CXKyDPq38joU-fMMQ9Q@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/alternative;
	boundary="------------090200020309020602030105"
X-Gm-Message-State: ALoCoQnYHPNZitOYS1jdvIUqnNVQYeGFB2VSP4RJdV29T8+e5xdcYKCKLCdcLxgY8ILyhB8LGrxZ
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1Ukelf-0005np-0T
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Revocability with known trusted escrow
 services?
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: Thu, 06 Jun 2013 18:18:36 -0000

This is a multi-part message in MIME format.
--------------090200020309020602030105
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If a technical solution could be found, I don't doubt that it will
quickly become the only legal way to do transfers in the U.S.

Peter, you are Executive Director of the Bitcoin Foundation. I would
like to know that your efforts are focused on fighting this archaic
world view, not bending over backwards to comply with it.

Mark
On 6/5/13 5:19 PM, Peter Vessenes wrote:
> 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
>
> --
>
> -------------------------
>
> CoinLab LogoPETER VESSENES
> CEO
>
> *peter@coinlab.com <mailto:peter@coinlab.com> * /  206.486.6856  /
SKYPE: vessenes
> 71 COLUMBIA ST / SUITE 300  /  SEATTLE, WA 98104
>
>
>
>
------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRsNJyAAoJEAdzVfsmodw4KBgP/A0ozXRdY0YbaFYL5tyWp+xO
OdOKbVFSQynHMws+CyA47x/DgiUbzrRwmx3fN7N67pPizYpjQLfJEwNkr6oy0Ga6
bbubYIz+TLI7sPS0B+ENg6XboChP+ZE7TPC56SyNgPUALwzsvcGZEYCHwwvIUx3F
EcUtXTw+VsBu935nRTvKj2HXruU94CaCiapS0knvgWg1/sB/PRFDQzu+fbBiLSL0
xWiuRaPs4dt+LCK2rfYtysKSv2S0FjOOwZ/Cj2J3KRtqTOnTSE2MZNAfNcMGA89u
LwWAfZohXywk2mBOk6avYxi5I0nNOndzfKQZgyHMH6zYdIP8B4gtBMxNP4CtsLaH
GWNdvYcxILcbeYqJUqlZfJamKkI0rAxgdk20YSaCAgU6rmJ8PQ4Ryl4uTS5i0xOb
xfMmHT68SOsvfL8XWobpMidVIUA+vKDZbd5AmJ9RCvJV5mj0Mrt/nJQM04NEQmtE
gb29fA1vh+nNKkPoVkyU02ghBYznurV+GMd5iFe8LObg6WxcIImadI1tdPpgINoK
glHeUl0zGXsbZDodk7imeZA3DXIf5xa9LfoVmJZrMMB/c3SQqRMwtUX04dMYQiCG
Gq4eisPXrUwepZ6hSgXqGktXYKn9dIlXR43zl4+ZBDjsAIiRiipK12WCz3pUTDow
/Xcx2iVrRWcZQefxJ3dz
=o0rL
-----END PGP SIGNATURE-----


--------------090200020309020602030105
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    -----BEGIN PGP SIGNED MESSAGE-----<br>
    Hash: SHA1<br>
    <br>
    If a technical solution could be found, I don't doubt that it will
    quickly become the only legal way to do transfers in the U.S.<br>
    <br>
    Peter, you are Executive Director of the Bitcoin Foundation. I would
    like to know that your efforts are focused on fighting this archaic
    world view, not bending over backwards to comply with it.<br>
    <br>
    Mark<br>
    On 6/5/13 5:19 PM, Peter Vessenes wrote:<br>
    <span style="white-space: pre;">&gt; So, this
      <a class="moz-txt-link-freetext" href="http://www.americanbanker.com/bankthink/the-last-straw-for-bitcoin-1059608-1.html?pg=1">http://www.americanbanker.com/bankthink/the-last-straw-for-bitcoin-1059608-1.html?pg=1</a>&nbsp;
      article got posted today, noting that FinCEN thinks irrevocable
      payments are money laundering tools. <br>
      &gt;<br>
      &gt; 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.<br>
      &gt;<br>
      &gt; At any rate, it got me thinking, can we layer on revocability
      somehow without any protocol change, as an opt-in?<br>
      &gt;<br>
      &gt; 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. <br>
      &gt;<br>
      &gt; 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.<br>
      &gt;<br>
      &gt; 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.<br>
      &gt;<br>
      &gt; 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.<br>
      &gt;<br>
      &gt; Peter<br>
      &gt;<br>
      &gt; -- <br>
      &gt;<br>
      &gt; -------------------------<br>
      &gt;<br>
      &gt; CoinLab LogoPETER VESSENES <br>
      &gt; CEO<br>
      &gt;<br>
      &gt; *peter@coinlab.com <a class="moz-txt-link-rfc2396E" href="mailto:peter@coinlab.com">&lt;mailto:peter@coinlab.com&gt;</a> * /&nbsp;
      206.486.6856&nbsp; / SKYPE: vessenes <br>
      &gt; 71 COLUMBIA ST / SUITE 300&nbsp; /&nbsp; SEATTLE, WA 98104<br>
      &gt;<br>
      &gt;<br>
      &gt;<br>
      &gt;
------------------------------------------------------------------------------<br>
      &gt; How ServiceNow helps IT people transform IT departments:<br>
      &gt; 1. A cloud service to automate IT design, transition and
      operations<br>
      &gt; 2. Dashboards that offer high-level views of enterprise
      services<br>
      &gt; 3. A single system of record for all IT processes<br>
      &gt; <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/servicenow-d2d-j">http://p.sf.net/sfu/servicenow-d2d-j</a><br>
      &gt;<br>
      &gt;<br>
      &gt; _______________________________________________<br>
      &gt; Bitcoin-development mailing list<br>
      &gt; <a class="moz-txt-link-abbreviated" href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
      &gt;
      <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a></span><br>
    <br>
    -----BEGIN PGP SIGNATURE-----<br>
    Version: GnuPG/MacGPG2 v2.0.19 (Darwin)<br>
    Comment: GPGTools - <a class="moz-txt-link-freetext" href="http://gpgtools.org">http://gpgtools.org</a><br>
    Comment: Using GnuPG with Thunderbird - <a class="moz-txt-link-freetext" href="http://www.enigmail.net/">http://www.enigmail.net/</a><br>
    <br>
    iQIcBAEBAgAGBQJRsNJyAAoJEAdzVfsmodw4KBgP/A0ozXRdY0YbaFYL5tyWp+xO<br>
    OdOKbVFSQynHMws+CyA47x/DgiUbzrRwmx3fN7N67pPizYpjQLfJEwNkr6oy0Ga6<br>
    bbubYIz+TLI7sPS0B+ENg6XboChP+ZE7TPC56SyNgPUALwzsvcGZEYCHwwvIUx3F<br>
    EcUtXTw+VsBu935nRTvKj2HXruU94CaCiapS0knvgWg1/sB/PRFDQzu+fbBiLSL0<br>
    xWiuRaPs4dt+LCK2rfYtysKSv2S0FjOOwZ/Cj2J3KRtqTOnTSE2MZNAfNcMGA89u<br>
    LwWAfZohXywk2mBOk6avYxi5I0nNOndzfKQZgyHMH6zYdIP8B4gtBMxNP4CtsLaH<br>
    GWNdvYcxILcbeYqJUqlZfJamKkI0rAxgdk20YSaCAgU6rmJ8PQ4Ryl4uTS5i0xOb<br>
    xfMmHT68SOsvfL8XWobpMidVIUA+vKDZbd5AmJ9RCvJV5mj0Mrt/nJQM04NEQmtE<br>
    gb29fA1vh+nNKkPoVkyU02ghBYznurV+GMd5iFe8LObg6WxcIImadI1tdPpgINoK<br>
    glHeUl0zGXsbZDodk7imeZA3DXIf5xa9LfoVmJZrMMB/c3SQqRMwtUX04dMYQiCG<br>
    Gq4eisPXrUwepZ6hSgXqGktXYKn9dIlXR43zl4+ZBDjsAIiRiipK12WCz3pUTDow<br>
    /Xcx2iVrRWcZQefxJ3dz<br>
    =o0rL<br>
    -----END PGP SIGNATURE-----<br>
    <br>
  </body>
</html>

--------------090200020309020602030105--