Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.175 as permitted sender)
	client-ip=209.85.214.175; envelope-from=jeremie.dl@gmail.com;
	helo=mail-ob0-f175.google.com; 
MIME-Version: 1.0
Date: Tue, 7 Oct 2014 19:32:10 +0200
Message-ID: <CAJqsvLB9JtvB=HmxYvg2HY_HFyecD=sekOO1moQg0PRs6BPa=w@mail.gmail.com>
From: =?UTF-8?B?SsOpcsOpbWllIER1Ym9pcy1MYWNvc3Rl?= <jeremie.dl@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: [Bitcoin-development] Partial wallet rescan
Precedence: list

Hi all,

Before starting to implement a patch for a specific need, I would like
to be sure that it was not written already and available somewhere.
This list is probably my best chance.

I would like to add an optional parameter <block_heigh> to "-rescan",
from which the rescan would then start. When performing the wallet
rescan, everything before the block number <block_heigh> would be
ignored.
Thus, it would do pretty much the same thing as the wallet birthday
mechanism (which relies on nTimeFirstKey), the difference being that
the point in time where to start would be *explicitly* given by the
user, at launch time, on the command line. Another possiblity is to
provide as parameter a time stamp instead of a block height; the
interesting part for me is that anyway that information is explicitly
provided by the user.

Regards,

Jeremie

--
Jeremie Dubois-Lacoste, PhD.
Belgian Bitcoin Association, Director.
Universit=C3=A9 Libre de Bruxelles, Post-Doctoral Researcher.