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
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.



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

Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
Bitcoin-development mailing list

Reply via email to