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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1QZNQB-000132-40
for bitcoin-development@lists.sourceforge.net;
Wed, 22 Jun 2011 13:24:43 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.47 as permitted sender)
client-ip=209.85.212.47; envelope-from=mh.in.england@gmail.com;
helo=mail-vw0-f47.google.com;
Received: from mail-vw0-f47.google.com ([209.85.212.47])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QZNQA-0005EX-0L
for bitcoin-development@lists.sourceforge.net;
Wed, 22 Jun 2011 13:24:43 +0000
Received: by vws2 with SMTP id 2so855411vws.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 22 Jun 2011 06:24:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.177.234 with SMTP id ct10mr924861vdc.2.1308749076394; Wed,
22 Jun 2011 06:24:36 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.155.38 with HTTP; Wed, 22 Jun 2011 06:24:36 -0700 (PDT)
In-Reply-To: <18440.87.106.138.84.1308200020.squirrel@lavabit.com>
References: <18440.87.106.138.84.1308200020.squirrel@lavabit.com>
Date: Wed, 22 Jun 2011 15:24:36 +0200
X-Google-Sender-Auth: mtK1qpRX_KrcG5uZW9tw4CrcEs0
Message-ID: <BANLkTi=FTLnU-riNVYssnR9FLdcEeZX7gOS6Zdv1f_XDcJoSSg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: bgroff@lavabit.com
Content-Type: multipart/alternative; boundary=bcaec5016663cc729604a64ce39b
X-Spam-Score: -0.7 (/)
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 FREEMAIL_FROM Sender email is freemail (mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.0 RFC_ABUSE_POST Both abuse and postmaster missing on sender domain
0.0 T_TO_NO_BRKTS_FREEMAIL T_TO_NO_BRKTS_FREEMAIL
-0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QZNQA-0005EX-0L
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] [PULL] Add scriptPubKey enforced
sendescrow and redeemescrow API calls
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: Wed, 22 Jun 2011 13:24:43 -0000
--bcaec5016663cc729604a64ce39b
Content-Type: text/plain; charset=UTF-8
Thanks for writing this. It's great to see somebody run with the contracts
protocol.
Your proposed protocol is simpler than the one I suggested, so I updated the
Contracts wiki page to use it. However your implementation, as pointed out
by Gavin, is too complicated. See my proposal on the wiki here:
https://en.bitcoin.it/wiki/Contracts
I think you can just use an output script of
2 <K1> <K2> <K3> 3 CHECKMULTISIGVERIFY
On Thu, Jun 16, 2011 at 6:53 AM, <bgroff@lavabit.com> wrote:
> 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 <= 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=8821.0 and
> https://forum.bitcoin.org/index.php?topic=4723.msg68804 .
>
> Feedback on the pull is very much appreciated.
>
>
>
>
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--bcaec5016663cc729604a64ce39b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Thanks for writing this. It's great to see somebody run with the contra=
cts protocol.<div><br></div><div>Your proposed protocol is simpler than the=
one I suggested, so I updated the Contracts wiki page to use it. However y=
our implementation, as pointed out by Gavin, is too complicated. See my pro=
posal on the wiki here:</div>
<div><br></div><div>=C2=A0=C2=A0<a href=3D"https://en.bitcoin.it/wiki/Contr=
acts">https://en.bitcoin.it/wiki/Contracts</a></div><div><br></div><div>I t=
hink you can just use an output script of=C2=A0</div><div><br></div><div>=
=C2=A0 2 <K1> <K2> <K3> 3 CHECKMULTISIGVERIFY</div>
<div><br></div><div><br><br></div><div><div class=3D"gmail_quote">On Thu, J=
un 16, 2011 at 6:53 AM, <span dir=3D"ltr"><<a href=3D"mailto:bgroff@lav=
abit.com">bgroff@lavabit.com</a>></span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex;">
I have a pull request here:<br>
<br>
<a href=3D"https://github.com/bitcoin/bitcoin/pull/319" target=3D"_blank">h=
ttps://github.com/bitcoin/bitcoin/pull/319</a><br>
<br>
>From the README:<br>
<br>
=C2=A0Bitcoin "escrow" are coins that are under the control of m=
ultiple<br>
=C2=A0parties. =C2=A0The initial implementation allows n parties to vote, =
with<br>
=C2=A0k good signatures needed (k <=3D n).<br>
<br>
=C2=A0This eliminates single points of failure and reduces the trust requi=
red<br>
=C2=A0in many transaction use cases.<br>
<br>
Use cases include Escrow (without trusting the escrow agent with the<br>
coins), immediate payment and funds locked with multi-party signatures.<br>
<br>
This was inspired by <a href=3D"https://forum.bitcoin.org/index.php?topic=
=3D8821.0" target=3D"_blank">https://forum.bitcoin.org/index.php?topic=3D88=
21.0</a> and<br>
<a href=3D"https://forum.bitcoin.org/index.php?topic=3D4723.msg68804" targe=
t=3D"_blank">https://forum.bitcoin.org/index.php?topic=3D4723.msg68804</a> =
.<br>
<br>
Feedback on the pull is very much appreciated.<br>
<br>
<br>
<br>
<br>
---------------------------------------------------------------------------=
---<br>
EditLive Enterprise is the world's most technically advanced content<br=
>
authoring tool. Experience the power of Track Changes, Inline Image<br>
Editing and ensure content is compliant with Accessibility Checking.<br>
<a href=3D"http://p.sf.net/sfu/ephox-dev2dev" target=3D"_blank">http://p.sf=
.net/sfu/ephox-dev2dev</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div>
--bcaec5016663cc729604a64ce39b--
|
