summaryrefslogtreecommitdiff
path: root/db/931e5fa908656edd489475ec562700bb2c62e0
blob: 48fa4f12bf7c64436de06abac7f39f0f15504095 (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
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
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <v@buterin.com>) id 1XWUjW-0006wU-8Y
	for bitcoin-development@lists.sourceforge.net;
	Tue, 23 Sep 2014 18:22:38 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of buterin.com
	designates 209.85.219.42 as permitted sender)
	client-ip=209.85.219.42; envelope-from=v@buterin.com;
	helo=mail-oa0-f42.google.com; 
Received: from mail-oa0-f42.google.com ([209.85.219.42])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XWUjR-0008WL-4g
	for bitcoin-development@lists.sourceforge.net;
	Tue, 23 Sep 2014 18:22:38 +0000
Received: by mail-oa0-f42.google.com with SMTP id i7so3729640oag.29
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 23 Sep 2014 11:22:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type;
	bh=sExfue5qdSxL2YrwqTRK1AGcj7azWb2lnDPhy+r/GSo=;
	b=TBbFbnfKRgQB+4+qo9MLAH1ZowMlbkIcErAdqV4kcAfAOlVHDYTM5HshByd0jq5OBq
	bl67wIeIHSHWTlioOuThTBYu5Z8gl6WhcUhDcgycJtZU9FRh76LO4EXm15wUWm2ERClg
	rXV4j4I0zWHdNSO4pBW7/FRoeHbbDDoMEMfGF1w0bZdGzUU75RnoZwXTwxCdT4JM3j3V
	fs6Tfko0MYoFQJu4FtGHFAOjdQk8mRZvQHTTfZeSRdVl16/ZwALwgYMBpnK0Rzl6BX1l
	XZN9jiUPtSEji7dJj5aXydOr+yn64ggBc2D8pb+zR/8Ei0foAb3DkOLO8Q4+I5XYQ7Cj
	HtHw==
X-Gm-Message-State: ALoCoQnNdY3DBUEJFMCIuFvHQdn75/Xb+4mb7/xEcTU+fWUjDh8o4Va+lnU+Dw+Ch9gZYBW9BcgG
MIME-Version: 1.0
X-Received: by 10.60.96.65 with SMTP id dq1mr1334442oeb.33.1411495049304; Tue,
	23 Sep 2014 10:57:29 -0700 (PDT)
Received: by 10.76.154.165 with HTTP; Tue, 23 Sep 2014 10:57:29 -0700 (PDT)
In-Reply-To: <mailman.358444.1411492141.2178.bitcoin-development@lists.sourceforge.net>
References: <mailman.358444.1411492141.2178.bitcoin-development@lists.sourceforge.net>
Date: Tue, 23 Sep 2014 13:57:29 -0400
Message-ID: <CAH8WSacmzmFs_L0NR0FunDuE+cfRyoKCq6dwG8qo8SM5K8C8vg@mail.gmail.com>
From: Vitalik Buterin <v@buterin.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=089e01227b640432990503bf4d11
X-Spam-Score: -0.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
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1XWUjR-0008WL-4g
Subject: Re: [Bitcoin-development] Bitcoin-development Digest, Vol 40,
	Issue 9
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: Tue, 23 Sep 2014 18:22:38 -0000

--089e01227b640432990503bf4d11
Content-Type: text/plain; charset=UTF-8

Have you looked at how Coinvault does it? They have a similar setup, but
sort the pubkeys at each address.

On Tue, Sep 23, 2014 at 1:09 PM, <
bitcoin-development-request@lists.sourceforge.net> wrote:

> Send Bitcoin-development mailing list submissions to
>         bitcoin-development@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> or, via email, send a message with subject or body 'help' to
>         bitcoin-development-request@lists.sourceforge.net
>
> You can reach the person managing the list at
>         bitcoin-development-owner@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Bitcoin-development digest..."
>
>
> Today's Topics:
>
>    1. Re: Proposal: "No-Collision" mode for Multisig BIP32 Wallets
>       (Justus Ranvier)
>    2. Re: Proposal: "No-Collision" mode for Multisig BIP32 Wallets
>       (Alan Reiner)
>    3. Re: Proposal: "No-Collision" mode for Multisig BIP32 Wallets
>       (Justus Ranvier)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 23 Sep 2014 16:37:20 +0000
> From: Justus Ranvier <justus@monetas.net>
> Subject: Re: [Bitcoin-development] Proposal: "No-Collision" mode for
>         Multisig BIP32 Wallets
> To: bitcoin-development@lists.sourceforge.net
> Message-ID: <5421A1C0.6080605@monetas.net>
> Content-Type: text/plain; charset="utf-8"
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 09/23/2014 04:16 PM, Alan Reiner wrote:
> > P.S. -- "No-Collision Mode" is not a great name.  Happy to take
> > suggestions for changing it.
>
> I'd call it a "voting pool wallet", since that was the original
> application for this arrangement.
>
> Would be nice if you'd at least mention our work, since we did share
> it with you back in January and have been publicly documenting it ever
> since.
>
> Or does the fact that we're implementing it in btcwallet mean what
> we're working on is unmentionable here?
>
> - --
> Justus Ranvier                   | Monetas <http://monetas.net/>
> <mailto:justus@monetas.net>      | Public key ID : C3F7BB2638450DB5
>                                  | BM-2cTepVtZ6AyJAs2Y8LpcvZB8KbdaWLwKqc
> -----BEGIN PGP SIGNATURE-----
>
> iQEcBAEBCAAGBQJUIaHAAAoJEMP3uyY4RQ21nwoH/3MYi9JibblZYmSOvCT1vJrN
> Ih+Q2WNumIAI+Y9bh4bBgLuhnG5lXyHedhYEUW+mfuwGiX+92Uc47nwaWED2/Lte
> 4Zk/KZnwLifdWCgKLdGpW6mzksRiOaVyU4vV5JchVOrGZZ2zYNIq+NcChtCph7Y5
> L202ReAG+1dfSpp4rFckuv7pTVjNcrq89UN1tJFDNQdxzIRd7bwoeCuvyFurZagB
> 88bNiOl0BI3e090WC+CWmbC6BfqJiicn/d0gp/agW01wy7CVbLypPPTKmYqt3+54
> msLUgaRHcbjuyKqu8HMHpYtgYVSNFg2q+U4SgmEepzPAkQ97khbduqA6i1B0ULM=
> =t/xp
> -----END PGP SIGNATURE-----
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: 0x38450DB5.asc
> Type: application/pgp-keys
> Size: 14046 bytes
> Desc: not available
>
> ------------------------------
>
> Message: 2
> Date: Tue, 23 Sep 2014 12:48:34 -0400
> From: Alan Reiner <etotheipi@gmail.com>
> Subject: Re: [Bitcoin-development] Proposal: "No-Collision" mode for
>         Multisig BIP32 Wallets
> To: bitcoin-development@lists.sourceforge.net
> Message-ID: <5421A462.6030205@gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 09/23/2014 12:37 PM, Justus Ranvier wrote:
> > Would be nice if you'd at least mention our work, since we did share
> > it with you back in January and have been publicly documenting it ever
> > since.
> >
> > Or does the fact that we're implementing it in btcwallet mean what
> > we're working on is unmentionable here?
> >
>
> Please don't assume poor intentions or sneaky motives.  I get a lot of
> emails from a lot of people about a lot of things.  Nine months ago was
> an eternity in this world, and it can't be ruled out that I simply forgot.
>
> I have no problem giving credit where it is due, and I mentioned in my
> first email that I wasn't sure if my stuff was original.  Please
> recap/link it here so that it can be part of this discussion.
>
> - -Alan
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQIcBAEBAgAGBQJUIaRiAAoJEBHe6b77WWmFcBgP/2IiQWda5diBIrd8MjbtYz/X
> pF+B1zOipClil151pKN5h9f4CI75qwSBSG6pUS+QH1lCz97nr5AoVYV5SAaRzv0z
> L9Bz0PiHJFHd4IRbfuFqlPZB8mw2TMD7QWJx/1U+WmpnYYOGsUeJn25psIVZSRTU
> FTCsmYrA4cGZ4bZoUKI/eiXrHao8rm/zQ7QHKOMSFWZT57sNea67vlxPXKu+AkmK
> nEYa4hD0kD7/R/TrNcmRmOlmbqCnyjICd/yp8Lj26CdHPv3PAvaxUwSX3VhWPbdc
> UOiGeo+lXqRnBVpwMd+k7oFddwrc2k9ISRdUVsU86z3JdAXKl/dLS5UoOtfC1JA9
> m90TuRtq4QuuzjLF3brI9FthuHNowA//qaVfjo/AYgsKy15td9UBtFbt4E9w263M
> NiFEmFkXfbE1JmIvmPG3AQEEdQ1/nmWiN5UcLrBfauEHMDQ1fGd89A8IBpus7bWM
> kYXboW3E9RBN4lB6OdyYU4AuH0YQhZodmry4iElMPox/tclmNiaeqDR8UYhD5BMd
> eQN9zAALyR1IY1167Ki/abVfWVf5jF7b0Eeu/wAfwcble3sCFrvWWAwzHjNi3GjY
> gNfy1eDTbwLj2M63QbtB+YqzQBZx3+SY4euGKYQ1s1CVV9ibAFI52oxeMhwzVOWF
> ofeDK5BPL8H+5L3tk+1o
> =tX2n
> -----END PGP SIGNATURE-----
>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 23 Sep 2014 17:07:58 +0000
> From: Justus Ranvier <justus@monetas.net>
> Subject: Re: [Bitcoin-development] Proposal: "No-Collision" mode for
>         Multisig BIP32 Wallets
> To: bitcoin-development@lists.sourceforge.net
> Message-ID: <5421A8EE.4060300@monetas.net>
> Content-Type: text/plain; charset="utf-8"
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 09/23/2014 04:48 PM, Alan Reiner wrote:
> > Please recap/link it here so that it can be part of this
> > discussion.
>
> http://sourceforge.net/p/bitcoin/mailman/message/32736455/
>
> http://opentransactions.org/wiki/index.php/Deposit_Address_(voting_pools)
>
> Currently being implemented here:
>
> https://github.com/monetas/btcwallet/commits/vp
>
> - --
>
> Really what's so annoying is how the BIP numbering process is handled in
> such a way that proposals can be silently pigeonholed.
>
> Especially so in the case of an *informational* BIP which requires no
> action on anyone's part (except for not using the same BIP43 purpose
> code).
>
> We resolved this by changing the naming scheme for our proposals, and
> their associated purpose codes, to not rely on centrally-allocated
> numbers.
>
> https://github.com/Open-Transactions/rfc/tree/master/bips
>
> - --
> Justus Ranvier                   | Monetas <http://monetas.net/>
> <mailto:justus@monetas.net>      | Public key ID : C3F7BB2638450DB5
>                                  | BM-2cTepVtZ6AyJAs2Y8LpcvZB8KbdaWLwKqc
> -----BEGIN PGP SIGNATURE-----
>
> iQEcBAEBCAAGBQJUIajuAAoJEMP3uyY4RQ215dQH/1GNOmZd19/e2Ys7MNFx0gqz
> rDmTFBylU3lhJrMY4CDd4Duq5+2U7HgaovqgX8UqxquHWLQUwEzZLqdEPCifLg0c
> d/u90cRlClFAaOxPh4HV2/3aZoS2R27N+ZjOfziW7RZySBP/2fMt4/ra+SPbkcAQ
> oeplYgqMRDqW52C/o2zm4y4yb0TJPS+lzSNM+JfxHSPRyY55l0KzLJfUNz1RSOze
> A8UAwdsLiJROKPKiSrQcqFOejPV7uqSPh10ukm/AI0k8TbvX8ffGQ083394M9IuE
> DB/1eyeLQVP5+lQMWNrTHk3BQ75XBEDJoSukaRENcqxtHV2m1JzTWoS2CQBXi2M=
> =TwI3
> -----END PGP SIGNATURE-----
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: 0x38450DB5.asc
> Type: application/pgp-keys
> Size: 14046 bytes
> Desc: not available
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>
> ------------------------------
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
> End of Bitcoin-development Digest, Vol 40, Issue 9
> **************************************************
>

--089e01227b640432990503bf4d11
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Have you looked at how Coinvault does it? They have a simi=
lar setup, but sort the pubkeys at each address.</div><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote">On Tue, Sep 23, 2014 at 1:09 PM,  <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-development-request@lists.sourc=
eforge.net" target=3D"_blank">bitcoin-development-request@lists.sourceforge=
.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Bitcoin-d=
evelopment mailing list submissions to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:bitcoin-development@lists.sou=
rceforge.net">bitcoin-development@lists.sourceforge.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://lists.sourceforge.net/lists/=
listinfo/bitcoin-development" target=3D"_blank">https://lists.sourceforge.n=
et/lists/listinfo/bitcoin-development</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:bitcoin-development-request@l=
ists.sourceforge.net">bitcoin-development-request@lists.sourceforge.net</a>=
<br>
<br>
You can reach the person managing the list at<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:bitcoin-development-owner@lis=
ts.sourceforge.net">bitcoin-development-owner@lists.sourceforge.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of Bitcoin-development digest...&quot;<br>
<br>
<br>
Today&#39;s Topics:<br>
<br>
=C2=A0 =C2=A01. Re: Proposal: &quot;No-Collision&quot; mode for Multisig BI=
P32 Wallets<br>
=C2=A0 =C2=A0 =C2=A0 (Justus Ranvier)<br>
=C2=A0 =C2=A02. Re: Proposal: &quot;No-Collision&quot; mode for Multisig BI=
P32 Wallets<br>
=C2=A0 =C2=A0 =C2=A0 (Alan Reiner)<br>
=C2=A0 =C2=A03. Re: Proposal: &quot;No-Collision&quot; mode for Multisig BI=
P32 Wallets<br>
=C2=A0 =C2=A0 =C2=A0 (Justus Ranvier)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 23 Sep 2014 16:37:20 +0000<br>
From: Justus Ranvier &lt;<a href=3D"mailto:justus@monetas.net">justus@monet=
as.net</a>&gt;<br>
Subject: Re: [Bitcoin-development] Proposal: &quot;No-Collision&quot; mode =
for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Multisig BIP32 Wallets<br>
To: <a href=3D"mailto:bitcoin-development@lists.sourceforge.net">bitcoin-de=
velopment@lists.sourceforge.net</a><br>
Message-ID: &lt;<a href=3D"mailto:5421A1C0.6080605@monetas.net">5421A1C0.60=
80605@monetas.net</a>&gt;<br>
Content-Type: text/plain; charset=3D&quot;utf-8&quot;<br>
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA256<br>
<br>
On 09/23/2014 04:16 PM, Alan Reiner wrote:<br>
&gt; P.S. -- &quot;No-Collision Mode&quot; is not a great name.=C2=A0 Happy=
 to take<br>
&gt; suggestions for changing it.<br>
<br>
I&#39;d call it a &quot;voting pool wallet&quot;, since that was the origin=
al<br>
application for this arrangement.<br>
<br>
Would be nice if you&#39;d at least mention our work, since we did share<br=
>
it with you back in January and have been publicly documenting it ever<br>
since.<br>
<br>
Or does the fact that we&#39;re implementing it in btcwallet mean what<br>
we&#39;re working on is unmentionable here?<br>
<br>
- --<br>
Justus Ranvier=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0| Monetas &lt;<a href=3D"http://monetas.net/" target=3D"_blank">h=
ttp://monetas.net/</a>&gt;<br>
&lt;mailto:<a href=3D"mailto:justus@monetas.net">justus@monetas.net</a>&gt;=
=C2=A0 =C2=A0 =C2=A0 | Public key ID : C3F7BB2638450DB5<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| BM-2cTepVtZ6AyJAs2Y8LpcvZB8K=
bdaWLwKqc<br>
-----BEGIN PGP SIGNATURE-----<br>
<br>
iQEcBAEBCAAGBQJUIaHAAAoJEMP3uyY4RQ21nwoH/3MYi9JibblZYmSOvCT1vJrN<br>
Ih+Q2WNumIAI+Y9bh4bBgLuhnG5lXyHedhYEUW+mfuwGiX+92Uc47nwaWED2/Lte<br>
4Zk/KZnwLifdWCgKLdGpW6mzksRiOaVyU4vV5JchVOrGZZ2zYNIq+NcChtCph7Y5<br>
L202ReAG+1dfSpp4rFckuv7pTVjNcrq89UN1tJFDNQdxzIRd7bwoeCuvyFurZagB<br>
88bNiOl0BI3e090WC+CWmbC6BfqJiicn/d0gp/agW01wy7CVbLypPPTKmYqt3+54<br>
msLUgaRHcbjuyKqu8HMHpYtgYVSNFg2q+U4SgmEepzPAkQ97khbduqA6i1B0ULM=3D<br>
=3Dt/xp<br>
-----END PGP SIGNATURE-----<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: 0x38450DB5.asc<br>
Type: application/pgp-keys<br>
Size: 14046 bytes<br>
Desc: not available<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 23 Sep 2014 12:48:34 -0400<br>
From: Alan Reiner &lt;<a href=3D"mailto:etotheipi@gmail.com">etotheipi@gmai=
l.com</a>&gt;<br>
Subject: Re: [Bitcoin-development] Proposal: &quot;No-Collision&quot; mode =
for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Multisig BIP32 Wallets<br>
To: <a href=3D"mailto:bitcoin-development@lists.sourceforge.net">bitcoin-de=
velopment@lists.sourceforge.net</a><br>
Message-ID: &lt;<a href=3D"mailto:5421A462.6030205@gmail.com">5421A462.6030=
205@gmail.com</a>&gt;<br>
Content-Type: text/plain; charset=3DISO-8859-1<br>
<br>
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
On 09/23/2014 12:37 PM, Justus Ranvier wrote:<br>
&gt; Would be nice if you&#39;d at least mention our work, since we did sha=
re<br>
&gt; it with you back in January and have been publicly documenting it ever=
<br>
&gt; since.<br>
&gt;<br>
&gt; Or does the fact that we&#39;re implementing it in btcwallet mean what=
<br>
&gt; we&#39;re working on is unmentionable here?<br>
&gt;<br>
<br>
Please don&#39;t assume poor intentions or sneaky motives.=C2=A0 I get a lo=
t of<br>
emails from a lot of people about a lot of things.=C2=A0 Nine months ago wa=
s<br>
an eternity in this world, and it can&#39;t be ruled out that I simply forg=
ot.<br>
<br>
I have no problem giving credit where it is due, and I mentioned in my<br>
first email that I wasn&#39;t sure if my stuff was original.=C2=A0 Please<b=
r>
recap/link it here so that it can be part of this discussion.<br>
<br>
- -Alan<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1<br>
<br>
iQIcBAEBAgAGBQJUIaRiAAoJEBHe6b77WWmFcBgP/2IiQWda5diBIrd8MjbtYz/X<br>
pF+B1zOipClil151pKN5h9f4CI75qwSBSG6pUS+QH1lCz97nr5AoVYV5SAaRzv0z<br>
L9Bz0PiHJFHd4IRbfuFqlPZB8mw2TMD7QWJx/1U+WmpnYYOGsUeJn25psIVZSRTU<br>
FTCsmYrA4cGZ4bZoUKI/eiXrHao8rm/zQ7QHKOMSFWZT57sNea67vlxPXKu+AkmK<br>
nEYa4hD0kD7/R/TrNcmRmOlmbqCnyjICd/yp8Lj26CdHPv3PAvaxUwSX3VhWPbdc<br>
UOiGeo+lXqRnBVpwMd+k7oFddwrc2k9ISRdUVsU86z3JdAXKl/dLS5UoOtfC1JA9<br>
m90TuRtq4QuuzjLF3brI9FthuHNowA//qaVfjo/AYgsKy15td9UBtFbt4E9w263M<br>
NiFEmFkXfbE1JmIvmPG3AQEEdQ1/nmWiN5UcLrBfauEHMDQ1fGd89A8IBpus7bWM<br>
kYXboW3E9RBN4lB6OdyYU4AuH0YQhZodmry4iElMPox/tclmNiaeqDR8UYhD5BMd<br>
eQN9zAALyR1IY1167Ki/abVfWVf5jF7b0Eeu/wAfwcble3sCFrvWWAwzHjNi3GjY<br>
gNfy1eDTbwLj2M63QbtB+YqzQBZx3+SY4euGKYQ1s1CVV9ibAFI52oxeMhwzVOWF<br>
ofeDK5BPL8H+5L3tk+1o<br>
=3DtX2n<br>
-----END PGP SIGNATURE-----<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 23 Sep 2014 17:07:58 +0000<br>
From: Justus Ranvier &lt;<a href=3D"mailto:justus@monetas.net">justus@monet=
as.net</a>&gt;<br>
Subject: Re: [Bitcoin-development] Proposal: &quot;No-Collision&quot; mode =
for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Multisig BIP32 Wallets<br>
To: <a href=3D"mailto:bitcoin-development@lists.sourceforge.net">bitcoin-de=
velopment@lists.sourceforge.net</a><br>
Message-ID: &lt;<a href=3D"mailto:5421A8EE.4060300@monetas.net">5421A8EE.40=
60300@monetas.net</a>&gt;<br>
Content-Type: text/plain; charset=3D&quot;utf-8&quot;<br>
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA256<br>
<br>
On 09/23/2014 04:48 PM, Alan Reiner wrote:<br>
&gt; Please recap/link it here so that it can be part of this<br>
&gt; discussion.<br>
<br>
<a href=3D"http://sourceforge.net/p/bitcoin/mailman/message/32736455/" targ=
et=3D"_blank">http://sourceforge.net/p/bitcoin/mailman/message/32736455/</a=
><br>
<br>
<a href=3D"http://opentransactions.org/wiki/index.php/Deposit_Address_(voti=
ng_pools)" target=3D"_blank">http://opentransactions.org/wiki/index.php/Dep=
osit_Address_(voting_pools)</a><br>
<br>
Currently being implemented here:<br>
<br>
<a href=3D"https://github.com/monetas/btcwallet/commits/vp" target=3D"_blan=
k">https://github.com/monetas/btcwallet/commits/vp</a><br>
<br>
- --<br>
<br>
Really what&#39;s so annoying is how the BIP numbering process is handled i=
n<br>
such a way that proposals can be silently pigeonholed.<br>
<br>
Especially so in the case of an *informational* BIP which requires no<br>
action on anyone&#39;s part (except for not using the same BIP43 purpose<br=
>
code).<br>
<br>
We resolved this by changing the naming scheme for our proposals, and<br>
their associated purpose codes, to not rely on centrally-allocated<br>
numbers.<br>
<br>
<a href=3D"https://github.com/Open-Transactions/rfc/tree/master/bips" targe=
t=3D"_blank">https://github.com/Open-Transactions/rfc/tree/master/bips</a><=
br>
<br>
- --<br>
Justus Ranvier=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0| Monetas &lt;<a href=3D"http://monetas.net/" target=3D"_blank">h=
ttp://monetas.net/</a>&gt;<br>
&lt;mailto:<a href=3D"mailto:justus@monetas.net">justus@monetas.net</a>&gt;=
=C2=A0 =C2=A0 =C2=A0 | Public key ID : C3F7BB2638450DB5<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| BM-2cTepVtZ6AyJAs2Y8LpcvZB8K=
bdaWLwKqc<br>
-----BEGIN PGP SIGNATURE-----<br>
<br>
iQEcBAEBCAAGBQJUIajuAAoJEMP3uyY4RQ215dQH/1GNOmZd19/e2Ys7MNFx0gqz<br>
rDmTFBylU3lhJrMY4CDd4Duq5+2U7HgaovqgX8UqxquHWLQUwEzZLqdEPCifLg0c<br>
d/u90cRlClFAaOxPh4HV2/3aZoS2R27N+ZjOfziW7RZySBP/2fMt4/ra+SPbkcAQ<br>
oeplYgqMRDqW52C/o2zm4y4yb0TJPS+lzSNM+JfxHSPRyY55l0KzLJfUNz1RSOze<br>
A8UAwdsLiJROKPKiSrQcqFOejPV7uqSPh10ukm/AI0k8TbvX8ffGQ083394M9IuE<br>
DB/1eyeLQVP5+lQMWNrTHk3BQ75XBEDJoSukaRENcqxtHV2m1JzTWoS2CQBXi2M=3D<br>
=3DTwI3<br>
-----END PGP SIGNATURE-----<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: 0x38450DB5.asc<br>
Type: application/pgp-keys<br>
Size: 14046 bytes<br>
Desc: not available<br>
<br>
------------------------------<br>
<br>
---------------------------------------------------------------------------=
---<br>
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer<br>
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports<br=
>
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper<br>
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D154622311&amp;iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D154622311&amp;iu=3D/4140/ostg.clktrk</a><br>
<br>
------------------------------<br>
<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>
<br>
<br>
End of Bitcoin-development Digest, Vol 40, Issue 9<br>
**************************************************<br>
</blockquote></div><br></div>

--089e01227b640432990503bf4d11--