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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jeanpaulkogelman@me.com>) id 1V1NnJ-0001NP-76
for bitcoin-development@lists.sourceforge.net;
Mon, 22 Jul 2013 21:37:25 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of me.com
designates 17.172.220.237 as permitted sender)
client-ip=17.172.220.237; envelope-from=jeanpaulkogelman@me.com;
helo=st11p02mm-asmtp002.mac.com;
Received: from st11p02mm-asmtpout002.mac.com ([17.172.220.237]
helo=st11p02mm-asmtp002.mac.com)
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1V1NnH-0003vM-3r for bitcoin-development@lists.sourceforge.net;
Mon, 22 Jul 2013 21:37:25 +0000
Received: from st11p02mm-spool001.mac.com ([17.172.220.246])
by st11p02mm-asmtp002.mac.com
(Oracle Communications Messaging Server 7u4-27.05(7.0.4.27.4) 64bit
(built Apr
23 2013)) with ESMTP id <0MQC007VTXDYFB30@st11p02mm-asmtp002.mac.com>
for bitcoin-development@lists.sourceforge.net; Mon,
22 Jul 2013 21:37:16 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure
engine=2.50.10432:5.10.8794,1.0.431,0.0.0000
definitions=2013-07-22_05:2013-07-22, 2013-07-22,
1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0
ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0
classifier=spam
adjust=0 reason=mlx scancount=1 engine=6.0.2-1305010000
definitions=main-1307220169
MIME-version: 1.0
Content-type: multipart/alternative;
boundary="Boundary_(ID_Vdf0BLCHqDc/Vwl8ceBu5w)"
Received: from localhost ([17.172.220.223]) by st11p02mm-spool001.mac.com
(Oracle Communications Messaging Server 7u4-23.01(7.0.4.23.0) 64bit
(built Aug
10 2011)) with ESMTP id <0MQC004KFXDZVPA0@st11p02mm-spool001.mac.com>;
Mon, 22 Jul 2013 21:37:11 +0000 (GMT)
To: Mike Hearn <mike@plan99.net>
From: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
Date: Mon, 22 Jul 2013 21:37:12 +0000 (GMT)
X-Mailer: iCloud Mail (1R)
X-Originating-IP: [159.153.138.53]
Message-id: <81f77484-3ca9-40a7-a999-884260b26be5@me.com>
In-reply-to: <CANEZrP37a=EH+1P47opH0E-1TG9ozgw_1NzecJpRRJsMaZRLOw@mail.gmail.com>
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: 1V1NnH-0003vM-3r
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet
master seed with optional encryption
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: Mon, 22 Jul 2013 21:37:25 -0000
--Boundary_(ID_Vdf0BLCHqDc/Vwl8ceBu5w)
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
I added a 2 byte 'weeks since 2013-01-01' field and updated the prefixes, ranges and test vectors.
The updated proposal lives here:
https://bitcointalk.org/index.php?topic=258678
Cheers,
jp
On Jul 22, 2013, at 06:14 AM, Mike Hearn <mike@plan99.net> wrote:
This isn't usable for SPV wallets unless it has a birthday in it. Otherwise you either need to scan the entire chain (slow) or find a fully indexed copy of the block chain (expensive, more centralised). Just add a UNIX time as an extra 4 bytes, or if you want to save a few characters then use a uint16 that represents "days since birth of this specification".
--Boundary_(ID_Vdf0BLCHqDc/Vwl8ceBu5w)
Content-type: multipart/related;
boundary="Boundary_(ID_QavY4mEarusBdqOyItVRkw)"; type="text/html"
--Boundary_(ID_QavY4mEarusBdqOyItVRkw)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
<html><body><div><br></div><div>I added a 2 byte 'weeks since 2013-01-01' field and updated the prefixes, ranges and test vectors.</div><div><br></div><div>The updated proposal lives here:</div><div><a href="https://bitcointalk.org/index.php?topic=258678">https://bitcointalk.org/index.php?topic=258678</a></div><div><br></div><div>Cheers,</div><div><br></div><div>jp<br><br>On Jul 22, 2013, at 06:14 AM, Mike Hearn <mike@plan99.net> wrote:<br><br></div><div><blockquote type="cite"><div class="msg-quote"><div dir="ltr">This isn't usable for SPV wallets unless it has a birthday in it. Otherwise you either need to scan the entire chain (slow) or find a fully indexed copy of the block chain (expensive, more centralised). Just add a UNIX time as an extra 4 bytes, or if you want to save a few characters then use a uint16 that represents "days since birth of this specification".</div></div></blockquote></div></body></html>
--Boundary_(ID_QavY4mEarusBdqOyItVRkw)--
--Boundary_(ID_Vdf0BLCHqDc/Vwl8ceBu5w)--
|
