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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <winkelspecht@gmail.com>) id 1VLsFS-0001sN-N7
for bitcoin-development@lists.sourceforge.net;
Tue, 17 Sep 2013 10:11:10 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.53 as permitted sender)
client-ip=209.85.212.53; envelope-from=winkelspecht@gmail.com;
helo=mail-vb0-f53.google.com;
Received: from mail-vb0-f53.google.com ([209.85.212.53])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VLsFR-0001l4-Rd
for bitcoin-development@lists.sourceforge.net;
Tue, 17 Sep 2013 10:11:10 +0000
Received: by mail-vb0-f53.google.com with SMTP id i3so3734446vbh.40
for <bitcoin-development@lists.sourceforge.net>;
Tue, 17 Sep 2013 03:11:04 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.220.249.67 with SMTP id mj3mr637479vcb.23.1379412664033;
Tue, 17 Sep 2013 03:11:04 -0700 (PDT)
Received: by 10.58.68.196 with HTTP; Tue, 17 Sep 2013 03:11:03 -0700 (PDT)
Date: Tue, 17 Sep 2013 03:11:03 -0700
Message-ID: <CAH97s+nU_aOt-CdJLcdeUucviOZ89ENZNpLvKY3AiH=orrZYkQ@mail.gmail.com>
From: Micah Winkelspecht <winkelspecht@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=089e013a15e6d6a84604e6918977
X-Spam-Score: -0.6 (/)
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 commonly abused enduser mail provider
(winkelspecht[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: 1VLsFR-0001l4-Rd
Subject: [Bitcoin-development] BIP32 (HD Wallets) implementation in Ruby
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, 17 Sep 2013 10:11:10 -0000
--089e013a15e6d6a84604e6918977
Content-Type: text/plain; charset=ISO-8859-1
I've been hard at work completing an open source Ruby gem library (called
MoneyTree) that implements Hierarchical Deterministic Bitcoin wallets
(BIP32), and it's about ready for release. It passes all of the test
vectors and has 100% code coverage. I've also written an extensive README
which goes into depth about HD Wallets, which I'll probably be turning into
a blog post.
However, I'm pretty new to crypto, so I wanted to run it by this group
first before releasing it. If anybody has knowledge of BIP32 and can give
at a review, I would greatly appreciate it, and would be glad to add you as
a contributor.
If you have knowledge of the BIP32 spec, but not Ruby, you can still help
by reading over my README for conceptual accuracy.
Check out the repo here: https://github.com/wink/money-tree
Thanks in advance,
Micah Winkelspecht
--089e013a15e6d6a84604e6918977
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I've been hard at work completing an open source Ruby =
gem library (called MoneyTree) that implements Hierarchical Deterministic B=
itcoin wallets (BIP32), and it's about ready for release. It passes all=
of the test vectors and has 100% code coverage. I've also written an e=
xtensive README which goes into depth about HD Wallets, which I'll prob=
ably be turning into a blog post.<div>
<br></div><div>However, I'm pretty new to crypto, so I wanted to run it=
by this group first before releasing it. If anybody has knowledge of BIP32=
and can give at a review, I would greatly appreciate it, and would be glad=
to add you as a contributor.</div>
<div><br></div><div>If you have knowledge of the BIP32 spec, but not Ruby, =
you can still help by reading over my README for conceptual accuracy.</div>=
<div><br></div><div>Check out the repo here:=A0<a href=3D"https://github.co=
m/wink/money-tree">https://github.com/wink/money-tree</a></div>
<div><br></div><div>Thanks in advance,</div><div><br></div><div>Micah Winke=
lspecht</div></div>
--089e013a15e6d6a84604e6918977--
|
