From: grarpamp <grarpamp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] Wallet related bug?
Date: Fri, 22 Jun 2012 20:10:57 -0400 [thread overview]
Message-ID: <CAD2Ti29zRc38K1DGfe=NC2PMZwCQs55LV1pkN4wuLntrgdchiw@mail.gmail.com> (raw)
I had previously commented on this.
My references to wallet ver were really to nFileVersion.
And I've since been able to make that, and the
real walletversion become current.
However it is still doing this every invocation...
Rescanning last 14xxx blocks (from block 170xxx)...
Which seems unneeded more than 1x. I cannot yet explain.
So I expect to avoid all by send the balance from old
wallets to new wallet soon instead.
The old wallets were ver 10500.
next reply other threads:[~2012-06-23 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 0:10 grarpamp [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-22 11:01 [Bitcoin-development] Wallet related bug? grarpamp
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='CAD2Ti29zRc38K1DGfe=NC2PMZwCQs55LV1pkN4wuLntrgdchiw@mail.gmail.com' \
--to=grarpamp@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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