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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pieter.wuille@gmail.com>) id 1Wd3X9-0007CJ-Eh
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 20:12:43 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.178 as permitted sender)
client-ip=209.85.223.178; envelope-from=pieter.wuille@gmail.com;
helo=mail-ie0-f178.google.com;
Received: from mail-ie0-f178.google.com ([209.85.223.178])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wd3X8-0004Lj-Im
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 20:12:43 +0000
Received: by mail-ie0-f178.google.com with SMTP id lx4so1405028iec.23
for <bitcoin-development@lists.sourceforge.net>;
Wed, 23 Apr 2014 13:12:37 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.42.131.197 with SMTP id a5mr45350133ict.8.1398283957287;
Wed, 23 Apr 2014 13:12:37 -0700 (PDT)
Received: by 10.50.127.243 with HTTP; Wed, 23 Apr 2014 13:12:37 -0700 (PDT)
Received: by 10.50.127.243 with HTTP; Wed, 23 Apr 2014 13:12:37 -0700 (PDT)
In-Reply-To: <53581CB3.2000109@gk2.sk>
References: <CANEZrP2hbBVGqytmXR1rAcVama4ONnR586Se-Ch=dsxOzy2O4w@mail.gmail.com>
<201404231955.09287.luke@dashjr.org>
<CAJna-Hhm-BDneR_qVzFtrGaMzs-7R-z5V49CVVv79mdOfBCD-w@mail.gmail.com>
<201404232001.06679.luke@dashjr.org> <53581CB3.2000109@gk2.sk>
Date: Wed, 23 Apr 2014 22:12:37 +0200
Message-ID: <CAPg+sBgssdOSuzGaWy2j1ed+s-oNseH9Yti8NZoHc_sBtr7fvQ@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Pavol Rusnak <stick@gk2.sk>
Content-Type: multipart/alternative; boundary=bcaec53969d891c18504f7bb5a39
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
(pieter.wuille[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: 1Wd3X8-0004Lj-Im
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New BIP32 structure
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: Wed, 23 Apr 2014 20:12:43 -0000
--bcaec53969d891c18504f7bb5a39
Content-Type: text/plain; charset=ISO-8859-1
I believe Luke means scanning chains as defined by the structure, but not
handing out addresses from other accounts than the first one.
That's certainly a possibly way to compatibly implement BIP64, but it
doesn't reduce all that much complexity. I hope people would choose that
over defining their own accountless structure though.
On 23 Apr 2014 22:06, "Pavol Rusnak" <stick@gk2.sk> wrote:
> On 04/23/2014 10:01 PM, Luke-Jr wrote:
> > Yes, it should scan all possible (under the BIP-defined structure)
> branches
> > regardless of which features it supports.
>
> So you suggest to scan for accounts, show balances but don't allow user
> to spend them? Does not seem right to me.
>
> --
> Best Regards / S pozdravom,
>
> Pavol Rusnak <stick@gk2.sk>
>
>
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--bcaec53969d891c18504f7bb5a39
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">I believe Luke means scanning chains as defined by the struc=
ture, but not handing out addresses from other accounts than the first one.=
</p>
<p dir=3D"ltr">That's certainly a possibly way to compatibly implement =
BIP64, but it doesn't reduce all that much complexity. I hope people wo=
uld choose that over defining their own accountless structure though.</p>
<div class=3D"gmail_quote">On 23 Apr 2014 22:06, "Pavol Rusnak" &=
lt;<a href=3D"mailto:stick@gk2.sk">stick@gk2.sk</a>> wrote:<br type=3D"a=
ttribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
On 04/23/2014 10:01 PM, Luke-Jr wrote:<br>
> Yes, it should scan all possible (under the BIP-defined structure) bra=
nches<br>
> regardless of which features it supports.<br>
<br>
So you suggest to scan for accounts, show balances but don't allow user=
<br>
to spend them? Does not seem right to me.<br>
<br>
--<br>
Best Regards / S pozdravom,<br>
<br>
Pavol Rusnak <<a href=3D"mailto:stick@gk2.sk">stick@gk2.sk</a>><br>
<br>
---------------------------------------------------------------------------=
---<br>
Start Your Social Network Today - Download eXo Platform<br>
Build your Enterprise Intranet with eXo Platform Software<br>
Java Based Open Source Intranet - Social, Extensible, Cloud Ready<br>
Get Started Now And Turn Your Intranet Into A Collaboration Platform<br>
<a href=3D"http://p.sf.net/sfu/ExoPlatform" target=3D"_blank">http://p.sf.n=
et/sfu/ExoPlatform</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div>
--bcaec53969d891c18504f7bb5a39--
|
