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
|
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 <mh.in.england@gmail.com>) id 1YW6HL-00087k-De
for bitcoin-development@lists.sourceforge.net;
Thu, 12 Mar 2015 16:48:11 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.175 as permitted sender)
client-ip=209.85.223.175; envelope-from=mh.in.england@gmail.com;
helo=mail-ie0-f175.google.com;
Received: from mail-ie0-f175.google.com ([209.85.223.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YW6HJ-0002vm-LV
for bitcoin-development@lists.sourceforge.net;
Thu, 12 Mar 2015 16:48:11 +0000
Received: by iecsl2 with SMTP id sl2so48641304iec.1
for <bitcoin-development@lists.sourceforge.net>;
Thu, 12 Mar 2015 09:48:04 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.8.215 with SMTP id h84mr50843273ioi.89.1426178876634;
Thu, 12 Mar 2015 09:47:56 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.36.54.147 with HTTP; Thu, 12 Mar 2015 09:47:56 -0700 (PDT)
In-Reply-To: <CAJna-HhHkmOTqNW2R6=Cih+tM_Eeu5o1LBxA4ZNzp-6vm1p6fg@mail.gmail.com>
References: <54F32EED.6040103@electrum.org>
<CANEZrP23buJF0ENfrKGRuzpQ3Uod09s-kRcb3CBw1-OmUxEyZg@mail.gmail.com>
<550057FD.6030402@electrum.org>
<CANEZrP2UrRYG2wh3DHHj9B3Sp1X=n+gPCRcoj1Fouu4Lg157UA@mail.gmail.com>
<CAJna-HhHkmOTqNW2R6=Cih+tM_Eeu5o1LBxA4ZNzp-6vm1p6fg@mail.gmail.com>
Date: Thu, 12 Mar 2015 09:47:56 -0700
X-Google-Sender-Auth: XNnmBfNrB33Boo9R3Pap8zmn8es
Message-ID: <CANEZrP2AhCfks7Q+16PHGB0ZEeWwbdbbQM_xj3ebrkgDBgbosg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: slush <slush@centrum.cz>
Content-Type: multipart/alternative; boundary=001a113f89bc540b8b05111a2585
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1YW6HJ-0002vm-LV
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Electrum 2.0 has been tagged
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: Thu, 12 Mar 2015 16:48:11 -0000
--001a113f89bc540b8b05111a2585
Content-Type: text/plain; charset=UTF-8
>
> b) "Creation date" is just a short-term hack.
>
I agree, but we need things to be easy in the short term as well as the
long term :)
The long term solution is clearly to have the 12 word seed be an encryption
key for a wallet backup with all associated metadata. We're heading in that
direction one step at a time. Unfortunately it will take time for wallets
to start working this way, and all the pieces to fall into place. Restoring
from the block chain will be a semi regular operation for users until then.
WRT version number I have no real strong feelings about this. But
representing short pieces of binary data as words is so convenient, it
seems likely that it could be similar to addresses: people find other uses
for this mechanism beyond just storing a raw private key. Bitcoin addresses
have versions and that's proven to be useful several times, even though in
theory an address is "just" a hash of a pubkey.
--001a113f89bc540b8b05111a2585
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div=
class=3D"gmail_quote"><div>b) "Creation date" is just a short-te=
rm hack. <br></div></div></div></div></blockquote><div><br></div><div>I agr=
ee, but we need things to be easy in the short term as well as the long ter=
m :)=C2=A0</div><div><br></div><div>The long term solution is clearly to ha=
ve the 12 word seed be an encryption key for a wallet backup with all assoc=
iated metadata. We're heading in that direction one step at a time. Unf=
ortunately it will take time for wallets to start working this way, and all=
the pieces to fall into place. Restoring from the block chain will be a se=
mi regular operation for users until then.</div><div><br></div><div>WRT ver=
sion number I have no real strong feelings about this. But representing sho=
rt pieces of binary data as words is so convenient, it seems likely that it=
could be similar to addresses: people find other uses for this mechanism b=
eyond just storing a raw private key. Bitcoin addresses have versions and t=
hat's proven to be useful several times, even though in theory an addre=
ss is "just" a hash of a pubkey.</div></div></div></div>
--001a113f89bc540b8b05111a2585--
|
