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-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tier.nolan@gmail.com>) id 1Wd2Pc-0006QW-72
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 19:00:52 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.44 as permitted sender)
client-ip=209.85.216.44; envelope-from=tier.nolan@gmail.com;
helo=mail-qa0-f44.google.com;
Received: from mail-qa0-f44.google.com ([209.85.216.44])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wd2PW-0007Kv-Vz
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 19:00:52 +0000
Received: by mail-qa0-f44.google.com with SMTP id hw13so1267518qab.31
for <bitcoin-development@lists.sourceforge.net>;
Wed, 23 Apr 2014 12:00:41 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.140.27.212 with SMTP id 78mr62428466qgx.18.1398279641515;
Wed, 23 Apr 2014 12:00:41 -0700 (PDT)
Received: by 10.140.25.86 with HTTP; Wed, 23 Apr 2014 12:00:41 -0700 (PDT)
In-Reply-To: <53580A73.9070208@gk2.sk>
References: <CANEZrP2hbBVGqytmXR1rAcVama4ONnR586Se-Ch=dsxOzy2O4w@mail.gmail.com>
<53344FF8.7030204@gk2.sk>
<CAPg+sBhbx5vy_hewAkFPaiXHzSMNH0qLhEYGjPmQMjR5StP-tw@mail.gmail.com>
<CAJna-Hi0JnrF2_rUx0rGkdnsuCoaD01e3Gobpn+QqbL=D1Uivg@mail.gmail.com>
<CAJna-HirtsGLfAhfUf9dAYEGWo6g=o=eAU187c2pdW8vDFGkPw@mail.gmail.com>
<CAPg+sBg8wDH9yTUoyhRbuzVtbD8hGxya8tOnV4pMToHy3gLrzw@mail.gmail.com>
<CAJna-HiN_1KQmpDJFFX6mGvM63RC0xwXxvfuorpihnzYf4=fsQ@mail.gmail.com>
<CAJna-HgfpyHX_0AHwt1Hkj0qhD_-xOcpxsZ9KXq=7CPgwse1hA@mail.gmail.com>
<CAPg+sBguSQ8dk1xXKinX+ez4BmdM3sz-huruuhD6NCTsp0kRBQ@mail.gmail.com>
<CAJna-Hib6umrkG0pAQzQvsyBMxOU6P675TURsVuWSU_ci9+X_A@mail.gmail.com>
<CAPg+sBiwzfXDAM0FKsBPi8d6E5y_nK5FDyfPvPhOTAA+f8654Q@mail.gmail.com>
<CAJna-HhPm0U2odPgRji7zJqCZCWuXKT_=ayC2tsajjRX5TiCXg@mail.gmail.com>
<CAJna-Hh2t-E=fm9V0EH+qOQTx+qsmcBemEJmML0G9PgsrJr5eg@mail.gmail.com>
<CAE-z3OVCL34FMECHDC3d8OiRKYhVSkzZFU0cGHV0ifu09bCbJA@mail.gmail.com>
<53580A73.9070208@gk2.sk>
Date: Wed, 23 Apr 2014 20:00:41 +0100
Message-ID: <CAE-z3OUMp_uO07+_R_x2yRLbSCzK1J5isbVUYEY3KF4Tx16K2Q@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c14d6654493904f7ba5975
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
(tier.nolan[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: 1Wd2PW-0007Kv-Vz
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 19:00:52 -0000
--001a11c14d6654493904f7ba5975
Content-Type: text/plain; charset=UTF-8
On Wed, Apr 23, 2014 at 7:46 PM, Pavol Rusnak <stick@gk2.sk> wrote:
>
> > Setting the gap limit to high is just a small extra cost in that case.
>
> Not if you have 100 accounts on 10 different devices.
>
I meant for a merchant with a server that is handing out hundreds of
addresses.
The point is to have a single system that is compatible over a large number
of systems.
--001a11c14d6654493904f7ba5975
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">On W=
ed, Apr 23, 2014 at 7:46 PM, Pavol Rusnak <span dir=3D"ltr"><<a href=3D"=
mailto:stick@gk2.sk" target=3D"_blank">stick@gk2.sk</a>></span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
<div class=3D""><br>
> Setting the gap limit to high is just a small extra cost in that case.=
<br>
<br>
</div>Not if you have 100 accounts on 10 different devices.<br></blockquote=
><div><br></div><div>I meant for a merchant with a server that is handing o=
ut hundreds of addresses.<br></div><div>=C2=A0<br></div><div>The point is t=
o have a single system that is compatible over a large number of systems.<b=
r>
</div></div></div></div>
--001a11c14d6654493904f7ba5975--
|
