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
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
|
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 <elombrozo@gmail.com>) id 1WNZDW-0000eH-Fm
for bitcoin-development@lists.sourceforge.net;
Wed, 12 Mar 2014 02:48:26 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.173 as permitted sender)
client-ip=209.85.192.173; envelope-from=elombrozo@gmail.com;
helo=mail-pd0-f173.google.com;
Received: from mail-pd0-f173.google.com ([209.85.192.173])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WNZDU-0005B6-Uk
for bitcoin-development@lists.sourceforge.net;
Wed, 12 Mar 2014 02:48:26 +0000
Received: by mail-pd0-f173.google.com with SMTP id z10so426748pdj.4
for <bitcoin-development@lists.sourceforge.net>;
Tue, 11 Mar 2014 19:48:19 -0700 (PDT)
X-Received: by 10.68.218.3 with SMTP id pc3mr1824235pbc.71.1394592499110;
Tue, 11 Mar 2014 19:48:19 -0700 (PDT)
Received: from [192.168.1.107] (cpe-76-88-33-166.san.res.rr.com.
[76.88.33.166])
by mx.google.com with ESMTPSA id vb7sm2019263pbc.13.2014.03.11.19.48.15
for <multiple recipients>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Tue, 11 Mar 2014 19:48:16 -0700 (PDT)
Content-Type: multipart/signed;
boundary="Apple-Mail=_55900BF5-A5DF-4933-87CA-D9C41B1FED3B";
protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Eric Lombrozo <elombrozo@gmail.com>
In-Reply-To: <531FC808.7060709@gmail.com>
Date: Tue, 11 Mar 2014 19:48:13 -0700
Message-Id: <9A6499BC-E546-45CC-A7EF-5182FC86052D@gmail.com>
References: <CANAnSg3Bt0e7CfUcJXe96xhU6nqif9ey_vurZMZkSa9OHjHStw@mail.gmail.com> <CABsx9T0SMi6Gp4JY=CpHxLEu5pVkvDmnug7PsY7m_dvtT7khzg@mail.gmail.com> <531DFDF8.80008@gmail.com> <531E52FE.5090107@jerviss.org> <531E5454.1030601@gmail.com> <CAJHLa0NZkzQQvMxgCJAJGT=Yn6vrVNK8Bg7RAfAjctpnrfg5zA@mail.gmail.com> <CABsx9T3eViYDsEmLm7ceimJNwci3mCOxWoVnVZHrqp7pDmm0+g@mail.gmail.com> <CANAnSg2kzPF0886PsQW8chzsWi6Urp+=-x+9bbv8Mv6hmpvBPw@mail.gmail.com> <CAJHLa0Mu2kiv3CCme7BPwzWtT++PNLQ2aAKdLyA8LFTtXEg9fg@mail.gmail.com> <CABsx9T0Lvg84qFVRbc7Ef4vZEQj9eO7Jhup5PTRLLeuJFvXi-w@mail.gmail.com> <4fca6b510dd57d2f92affeb988d2ee5d.squirrel@fulvetta.riseup.net>
<531FAA55.2020108@xeno-genesis.com> <531FC808.7060709@gmail.com>
To: Alan Reiner <etotheipi@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [209.85.192.173 listed in list.dnswl.org]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(elombrozo[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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
X-Headers-End: 1WNZDU-0005B6-Uk
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Multisign payment protocol?
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, 12 Mar 2014 02:48:26 -0000
--Apple-Mail=_55900BF5-A5DF-4933-87CA-D9C41B1FED3B
Content-Type: multipart/alternative;
boundary="Apple-Mail=_1511D332-608E-42BF-8F01-B6B2450979F9"
--Apple-Mail=_1511D332-608E-42BF-8F01-B6B2450979F9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
Ciphrex CoinVault (https://ciphrex.com) is currently using parallel =
trees with lexicographic sorting of keys.
CoinVault is also using a partially signed transaction format whereby =
0-length placeholders are used for missing signatures in the transaction =
scripts. Once all the required signatures to satisfy the policy are =
present, the remaining zero-length placeholders are removed so the =
transaction can be broadcast to the network. These partially signed =
transactions can be shared with other parties to an account or other =
signing devices for the purpose of requesting additional signatures.
-Eric
On Mar 11, 2014, at 7:35 PM, Alan Reiner <etotheipi@gmail.com> wrote:
> I might as well throw in a word about Armory. After our next release =
in a couple weeks, we will be going full-speed at new wallets and BIP32 =
integration. Just like Jean-Pierre mentioned, we'll be using parallel =
trees to generate P2SH addresses after sorting the keys =
lexicographically. We plan to introduce the concept of a wallet =
"bundle" (that name is far from concrete... I'd love a better word). =
All wallets in a bundle are protected by the same backup, and stored in =
the same file. The default behavior will be use new branches in the =
same BIP32 tree when a user creates a new "wallet", though we will allow =
multiple bundles in advanced and expert usermode (which is needed to =
have watching-only wallets from a different seed created from an offline =
computer).
>=20
> However, we do plan to allow separate parties to create =
multisig-intended wallets with public parts that can be exported and =
combined with other users. We feel this is critical, as it allows for =
linked wallets in which there was never a single-point of failure from =
key-generation to signing. This is especially important for contexts =
where employees may be handling a company's Bitcoins wallets.
>=20
> On this topic, I have gotten a lot of inquiries into BIP 38 and 39. I =
was not clear whether those BIPs were worth prioritizing ... i.e. is =
there a general consensus from a variety of wallet developers that they =
should be supported? Rather, I'm happy to start prioritizing them if =
others do too, but I haven't spent much time trying to understand them =
to even know if they're mature, yet.
>=20
> -Alan
>=20
>=20
> On 03/11/2014 08:29 PM, Jean-Pierre Rupp wrote:
>> Hello people,
>>=20
>> We are working on some of this stuff. We had some very early draft on
>> how we envisioned multisig happening. It is all implemented in =
Haskoin
>> available as multiple repositories in Github. I am happy to see this
>> gathering momentum.
>>=20
>> Our multisig system uses BIP-0032 HD wallets, and there will soon be
>> BIP-0039 support for keys compatibility.
>>=20
>> Our wallet uses synced trees rooted at the extended pubkeys of the
>> participants. Currently we are sorting public keys in the scripts to
>> avoid ambiguity.
>>=20
>> Download haskoin-wallet:
>>=20
>> cabal install haskoin-wallet
>>=20
>> Check out the hw command (installed in ~/.cabal/bin/hw). Use importtx =
to
>> bring transactions into the wallet. You must initialize first with a
>> seed and create an account. It supports both regular and multisig =
accounts.
>>=20
>> Perhaps this can lead to interesting discussions on key exchange, and
>> the appropriate handling of wallet metadata. I=92d love to work on a
>> proper standard that could lead us to compatible implementations.
>>=20
>> This document explains how we do it now:
>>=20
>> http://haskoin.com/~xeno/hd-multisig-wallet.html
>>=20
>> Cheers!
>>=20
>>=20
>>=20
>> =
--------------------------------------------------------------------------=
----
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and =
their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/13534_NeoTech
>>=20
>>=20
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>=20
> =
--------------------------------------------------------------------------=
----
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and =
their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> =
http://p.sf.net/sfu/13534_NeoTech_________________________________________=
______
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--Apple-Mail=_1511D332-608E-42BF-8F01-B6B2450979F9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=windows-1252
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Ciphrex CoinVault (<a =
href=3D"https://ciphrex.com">https://ciphrex.com</a>) is currently using =
parallel trees with lexicographic sorting of =
keys.<div><br></div><div>CoinVault is also using a partially signed =
transaction format whereby 0-length placeholders are used for missing =
signatures in the transaction scripts. Once all the required signatures =
to satisfy the policy are present, the remaining zero-length =
placeholders are removed so the transaction can be broadcast to the =
network. These partially signed transactions can be shared with other =
parties to an account or other signing devices for the purpose of =
requesting additional =
signatures.</div><div><br></div><div>-Eric<br><div><br></div><div><br><div=
><div>On Mar 11, 2014, at 7:35 PM, Alan Reiner <<a =
href=3D"mailto:etotheipi@gmail.com">etotheipi@gmail.com</a>> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">
=20
<meta content=3D"text/html; charset=3DISO-8859-1" =
http-equiv=3D"Content-Type">
=20
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
I might as well throw in a word about Armory. After our next
release in a couple weeks, we will be going full-speed at new
wallets and BIP32 integration. Just like Jean-Pierre =
mentioned,
we'll be using parallel trees to generate P2SH addresses after
sorting the keys lexicographically. We plan to introduce the
concept of a wallet "bundle" (that name is far from concrete... I'd
love a better word). All wallets in a bundle are protected by =
the
same backup, and stored in the same file. The default behavior =
will
be use new branches in the same BIP32 tree when a user creates a new
"wallet", though we will allow multiple bundles in advanced and
expert usermode (which is needed to have watching-only wallets from
a different seed created from an offline computer).<br>
<br>
However, we do plan to allow separate parties to create
multisig-intended wallets with public parts that can be exported and
combined with other users. We feel this is critical, as it =
allows
for linked wallets in which there was never a single-point of
failure from key-generation to signing. This is especially
important for contexts where employees may be handling a company's
Bitcoins wallets.<br>
<br>
On this topic, I have gotten a lot of inquiries into BIP 38 and =
39.
I was not clear whether those BIPs were worth prioritizing ... i.e.
is there a general consensus from a variety of wallet developers
that they should be supported? Rather, I'm happy to start
prioritizing them if others do too, but I haven't spent much time
trying to understand them to even know if they're mature, yet.<br>
<br>
-Alan<br>
<br>
<br>
<div class=3D"moz-cite-prefix">On 03/11/2014 08:29 PM, Jean-Pierre
Rupp wrote:<br>
</div>
<blockquote cite=3D"mid:531FAA55.2020108@xeno-genesis.com" =
type=3D"cite">
<pre wrap=3D"">Hello people,
We are working on some of this stuff. We had some very early draft on
how we envisioned multisig happening. It is all implemented in Haskoin
available as multiple repositories in Github. I am happy to see this
gathering momentum.
Our multisig system uses BIP-0032 HD wallets, and there will soon be
BIP-0039 support for keys compatibility.
Our wallet uses synced trees rooted at the extended pubkeys of the
participants. Currently we are sorting public keys in the scripts to
avoid ambiguity.
Download haskoin-wallet:
cabal install haskoin-wallet
Check out the hw command (installed in ~/.cabal/bin/hw). Use importtx to
bring transactions into the wallet. You must initialize first with a
seed and create an account. It supports both regular and multisig =
accounts.
Perhaps this can lead to interesting discussions on key exchange, and
the appropriate handling of wallet metadata. I=92d love to work on a
proper standard that could lead us to compatible implementations.
This document explains how we do it now:
<a class=3D"moz-txt-link-freetext" =
href=3D"http://haskoin.com/~xeno/hd-multisig-wallet.html">http://haskoin.c=
om/~xeno/hd-multisig-wallet.html</a>
Cheers!
</pre>
<br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset>
<br>
<pre =
wrap=3D"">----------------------------------------------------------------=
--------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and =
their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
<a class=3D"moz-txt-link-freetext" =
href=3D"http://p.sf.net/sfu/13534_NeoTech">http://p.sf.net/sfu/13534_NeoTe=
ch</a></pre>
<br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset>
<br>
<pre wrap=3D"">_______________________________________________
Bitcoin-development mailing list
<a class=3D"moz-txt-link-abbreviated" =
href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-developm=
ent@lists.sourceforge.net</a>
<a class=3D"moz-txt-link-freetext" =
href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development">=
https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a>
</pre>
</blockquote>
<br>
</div>
=
--------------------------------------------------------------------------=
----<br>Learn Graph Databases - Download FREE O'Reilly Book<br>"Graph =
Databases" is the definitive new guide to graph databases and =
their<br>applications. Written by three acclaimed leaders in the =
field,<br>this first edition is now available. Download your free book =
today!<br><a =
href=3D"http://p.sf.net/sfu/13534_NeoTech_________________________________=
______________">http://p.sf.net/sfu/13534_NeoTech_________________________=
______________________</a><br>Bitcoin-development mailing =
list<br>Bitcoin-development@lists.sourceforge.net<br>https://lists.sourcef=
orge.net/lists/listinfo/bitcoin-development<br></blockquote></div><br></di=
v></div></body></html>=
--Apple-Mail=_1511D332-608E-42BF-8F01-B6B2450979F9--
--Apple-Mail=_55900BF5-A5DF-4933-87CA-D9C41B1FED3B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
iQIcBAEBAgAGBQJTH8rtAAoJEAA1EyJsW9n+S9IP/25ZWAx+Iz3/5tu4Sngfh7fK
c5q3b/PXAlmFcQ54dN31+E/j58LwHt1KYx6a4QHoNJll7T5Z4Jj62z1HxR3YRCEn
GijHzvY1zP11qIfg7LdIFVqtJegRGx/s+xLd6upfIeRMnB+6UJe1aGKQava23Em7
v8KyE0NQTtNEaActdoP1bTycVjY7pFVSg+03WghXENoK+cQvh9jIrIyMNEPjYmEN
Y/mNKPqT6v2SnmAXpZTDWCBsZVhuRkm4Zcifol7qBSies41gMRNtHzAcFXJMVU6H
CDxLroT9jB/IO4Fc7nBR3l8PhmPk4wf6F3+XPSl6phTdq8g9joLmOG+T/xe8s0rd
2/LIX4IO06lnc4yQ/tiEbAIqq2jfAvKvLy42UY44KM67xVvr349Or2BptzFIoG42
bsjnL00Yk0LDP1TUQEPomoQ5iXfNtISisHPUHtn6Qkol19EEHWCgEeKOUIzGJqmF
YwyYBxbXrjHqR4SiR98nzUa3CWEYh1z5Q5aL5Jq9OnVHxw73+543jbDHgXCXxdRN
rwfCX1SAMMumMOZ4ziewvX0dt2hEU1kIbTagz3T+VPXvBozUqF05nsz/ul1cBv2T
ZWQUyQ/03W4sDNGt4IWNbOvmTXrXIWaxOgxQepWLC21GPTnRP2shhYKPQICSwFj+
hx2prlqHaQgZtlc/Ti6v
=8BO/
-----END PGP SIGNATURE-----
--Apple-Mail=_55900BF5-A5DF-4933-87CA-D9C41B1FED3B--
|
