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
|
Return-Path: <dev@jonasschnelli.ch>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 2226771
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 25 Aug 2016 07:39:35 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from server3 (server3.include7.ch [144.76.194.38])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 6603B162
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 25 Aug 2016 07:39:34 +0000 (UTC)
Received: by server3 (Postfix, from userid 115)
id 19E8C2E606A0; Thu, 25 Aug 2016 09:39:33 +0200 (CEST)
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Spam-Level:
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, FSL_HELO_NON_FQDN_1
autolearn=ham version=3.3.1
Received: from Jonass-MacBook-Pro-2.local (84-73-208-41.dclient.hispeed.ch
[84.73.208.41]) by server3 (Postfix) with ESMTPSA id E07F02D0002E;
Thu, 25 Aug 2016 09:39:31 +0200 (CEST)
To: Jochen Hoenicke <hoenicke@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
References: <201608232012.12588.luke@dashjr.org>
<90bf12f2-e109-28b4-e93e-54bbc8002cb4@electrum.org>
<57BDACB2.9040307@jonasschnelli.ch>
<278c940d-4b3b-2b8a-1aa5-f0991f1e6c8e@gmail.com>
From: Jonas Schnelli <dev@jonasschnelli.ch>
Message-ID: <57BEA0B0.3090308@jonasschnelli.ch>
Date: Thu, 25 Aug 2016 09:39:28 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <278c940d-4b3b-2b8a-1aa5-f0991f1e6c8e@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature";
boundary="qkR6uwsjEH2GsXqLt8xMjeOKn3NFSxf7G"
Subject: Re: [bitcoin-dev] BIP Status updates (including to Active/Final
Status) - BIP 39, BIP 43, BIP 44, BIP 67, BIP 111, BIP 125, BIP 130
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 07:39:35 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--qkR6uwsjEH2GsXqLt8xMjeOKn3NFSxf7G
Content-Type: multipart/mixed; boundary="rpS2ev08Ob824mD5a0vhJe2eOLR4gMJlm"
From: Jonas Schnelli <dev@jonasschnelli.ch>
To: Jochen Hoenicke <hoenicke@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <57BEA0B0.3090308@jonasschnelli.ch>
Subject: Re: [bitcoin-dev] BIP Status updates (including to Active/Final
Status) - BIP 39, BIP 43, BIP 44, BIP 67, BIP 111, BIP 125, BIP 130
References: <201608232012.12588.luke@dashjr.org>
<90bf12f2-e109-28b4-e93e-54bbc8002cb4@electrum.org>
<57BDACB2.9040307@jonasschnelli.ch>
<278c940d-4b3b-2b8a-1aa5-f0991f1e6c8e@gmail.com>
In-Reply-To: <278c940d-4b3b-2b8a-1aa5-f0991f1e6c8e@gmail.com>
--rpS2ev08Ob824mD5a0vhJe2eOLR4gMJlm
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Sorry for hijacking the thread again
> As I understand it, you can scan sequentially starting with the genesis=
> block (or with a block at around the time when BIP44 was written). The=
n
> if you find a new transaction, which requires to generate new addresses=
,
> you generate them and scan further from that point on. This way you ca=
n
> scan in a single pass if the scanning process calls you back when it
> finds a transaction and allows you to change the set of addresses on th=
e
> fly.
(I think this case if not completely unrealistic):
What would happen, if a user gave out 21 addresses, then address0 had
receive funds in +180 days after generation where address21 had receive
funds immediately (all other addresses never received a tx).
In a scan, address0 would be detected at <address-birthday>+180 days
which would trigger the resize+20 of the address-lookup-window, but, we
would require to go back 180day in order to detect received transaction
of address21 (new lookup-window) in that case.
Or do I misunderstand something?
</jonas>
--rpS2ev08Ob824mD5a0vhJe2eOLR4gMJlm--
--qkR6uwsjEH2GsXqLt8xMjeOKn3NFSxf7G
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJXvqCwAAoJECnUvLZBb1PsMS8QAJkNxhUwRvuBzuB8gGPHZaWZ
x9sJ8EPUWi9Am0NE01vifmE813onSd8whdbBPLSXj67mWYUcdkOavMnHtlCK1wAJ
zT7ziNYLBzeR6rTN6I1rDXt5ZJwGX4kXYezefspCvnYFKQfAlujmxX56mfUiwAQN
DEonlupV8ri98u0k7Wp0+aNR4zzj2LUZsuVCAeGjBMUX0xXmWIJUvCh0L+KikbUZ
SQ6Tiu3lqr4kQASeqR5veUVkE9NtyfInAivbOE557kopaAugwhwIGLfGDWBipp6J
XJQC8r0dYP783icrKTeS4stp3JXgYieVtfd+vTN0r3OqktmKoDIFfu83t9Yo9qv3
pp5x9s67xc4ccsJFJKp3khFRYAP/nmP21yN+31e9V79DO+4rA3Qyc6s7sYqwmPuI
0qW53Sv8k+/HiLt4cabOGyhnLH9x1rTrBbWQ7ma0smDvst4POObyXy03J6hcuFB6
5Vecpuedocx1hEeWdDKu0ho/Y8rGg0jzFYDcDd0gPlyqXmntUUTbAwN/2YXkaWcy
sAOPxx8J9Ah/x8G+qRZR2/UweLRqH7gEAsFGcxNU+ZdUdpxM9MM3V029tLuBHTOZ
ZrmIPrg34BRR6iDcjeIBl+gWrbqQX4UliulB0WWRF92w3vvswQYIpf2tIX+SY2HJ
Sc67EYyFQRHCXzbQHOHC
=072s
-----END PGP SIGNATURE-----
--qkR6uwsjEH2GsXqLt8xMjeOKn3NFSxf7G--
|
