summaryrefslogtreecommitdiff
path: root/92/aa6b52e9fbb5d87949e734b42d0cbe9e82ce54
blob: 405dc8aca21f2cb9d10569efd300a038c50cbe92 (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
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 <jeanpaulkogelman@me.com>) id 1V1HBN-0004Qv-B4
	for bitcoin-development@lists.sourceforge.net;
	Mon, 22 Jul 2013 14:33:49 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of me.com
	designates 17.172.220.240 as permitted sender)
	client-ip=17.172.220.240; envelope-from=jeanpaulkogelman@me.com;
	helo=st11p02mm-asmtp005.mac.com; 
Received: from st11p02mm-asmtpout005.mac.com ([17.172.220.240]
	helo=st11p02mm-asmtp005.mac.com)
	by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1V1HBK-0003re-48 for bitcoin-development@lists.sourceforge.net;
	Mon, 22 Jul 2013 14:33:49 +0000
Received: from [10.0.1.7] (216-19-182-8.dyn.novuscom.net [216.19.182.8])
	by st11p02mm-asmtp005.mac.com
	(Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit
	(built Jan
	3 2012)) with ESMTPSA id <0MQC00J3WDRXC1C0@st11p02mm-asmtp005.mac.com>
	for bitcoin-development@lists.sourceforge.net; Mon,
	22 Jul 2013 14:33:35 +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_03:2013-07-19, 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-1307220092
References: <op.w0hd2nthyldrnw@laptop-air>
	<acc0f014-7ae3-4e45-87ad-2b0e5358dca9@me.com>
	<CANEZrP37a=EH+1P47opH0E-1TG9ozgw_1NzecJpRRJsMaZRLOw@mail.gmail.com>
MIME-version: 1.0 (1.0)
In-reply-to: <CANEZrP37a=EH+1P47opH0E-1TG9ozgw_1NzecJpRRJsMaZRLOw@mail.gmail.com>
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Message-id: <058CED37-646C-4978-8026-8EF3868F17A7@me.com>
X-Mailer: iPhone Mail (10B329)
From: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
Date: Mon, 22 Jul 2013 07:33:34 -0700
To: Mike Hearn <mike@plan99.net>
X-Spam-Score: -1.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
X-Headers-End: 1V1HBK-0003re-48
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 14:33:49 -0000

Hi Mike,

I had a similar request on the forums. I suggested adding either a 2 byte 'w=
eeks since genesis' or 'months since genesis', but starting from spec birth w=
orks too. Would either of those work for you?


jp

On Jul 22, 2013, at 6:14 AM, Mike Hearn <mike@plan99.net> wrote:

> This isn't usable for SPV wallets unless it has a birthday in it. Otherwis=
e you either need to scan the entire chain (slow) or find a fully indexed co=
py 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".