From: "Jérémie Dubois-Lacoste" <jeremie.dl@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Partial wallet rescan
Date: Tue, 7 Oct 2014 19:32:10 +0200 [thread overview]
Message-ID: <CAJqsvLB9JtvB=HmxYvg2HY_HFyecD=sekOO1moQg0PRs6BPa=w@mail.gmail.com> (raw)
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é Libre de Bruxelles, Post-Doctoral Researcher.
reply other threads:[~2014-10-07 17:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJqsvLB9JtvB=HmxYvg2HY_HFyecD=sekOO1moQg0PRs6BPa=w@mail.gmail.com' \
--to=jeremie.dl@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox