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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1VZndA-0005iX-5y
for bitcoin-development@lists.sourceforge.net;
Fri, 25 Oct 2013 20:05:12 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.50 as permitted sender)
client-ip=209.85.215.50; envelope-from=gmaxwell@gmail.com;
helo=mail-la0-f50.google.com;
Received: from mail-la0-f50.google.com ([209.85.215.50])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VZnd8-0008As-Vo
for bitcoin-development@lists.sourceforge.net;
Fri, 25 Oct 2013 20:05:12 +0000
Received: by mail-la0-f50.google.com with SMTP id ec20so3483014lab.37
for <bitcoin-development@lists.sourceforge.net>;
Fri, 25 Oct 2013 13:05:04 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.125.33 with SMTP id mn1mr3312224lbb.8.1382731504187;
Fri, 25 Oct 2013 13:05:04 -0700 (PDT)
Received: by 10.112.89.72 with HTTP; Fri, 25 Oct 2013 13:05:04 -0700 (PDT)
In-Reply-To: <B09A5DE3EF411243BB3328232CD25A5D998989775B@MAILR023.mail.lan>
References: <B09A5DE3EF411243BB3328232CD25A5D998989775B@MAILR023.mail.lan>
Date: Fri, 25 Oct 2013 13:05:04 -0700
Message-ID: <CAAS2fgR0zH6JZWm-qLR3HcTC_m5o4N7V4wnGMM01q4yiS4CDwQ@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Mike Caldwell <mcaldwell@swipeclock.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.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
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: swipeclock.com]
X-Headers-End: 1VZnd8-0008As-Vo
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 38
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: Fri, 25 Oct 2013 20:05:12 -0000
On Fri, Oct 25, 2013 at 11:50 AM, Mike Caldwell
<mcaldwell@swipeclock.com> wrote:
> I have noticed that there was a recent change to BIP 0038
> (Password-Protected Private Key) on the Wiki, which is a proposal I wrote=
in
> late 2012. Gregory, it looks to me as though you have made this change, =
and
> I=E2=80=99m hoping for your help here. The change suggests that the numb=
er was
> never assigned, and that there has been no discussion regarding the propo=
sal
> on this list.
Greetings, (repeating from our discussion on IRC)
No prior messages about your proposal have made it to the list, and no
mention of the assignment had been made in the wiki.
The first I ever heard of this scheme was long after you'd written the
document when I attempted to assign the number to something else then
noticed something existed at that name.
Since you had previously created BIP documents without public
discussion (e.g. "BIP 22"
https://en.bitcoin.it/wiki/OP_CHECKSIGEX_DRAFT_BIP [...] Or, I wonder
did your emails just get eaten that time too?), I'd just assumed
something similar had happened here.
I didn't take any action at the time I first noticed it, but after
someone complained about bitcoin-qt "not confirming with BIP38" to me
today it was clear to me that people were confusing this with
something that was "officially" (as much as anything is) supported, so
I moved the document out. (I've since moved it back, having heard
from you that you thought that it had actually been
assigned/announced).
With respect to moving it forward: Having a wallet which can only a
single address is poor form. Jean-Paul Kogelman has a draft proposal
which is based on your BIP38 work though the encoding scheme is
different, having been revised in response to public discussion.
Perhaps efforts here can be combined?
|
