blob: aa58a81e3c15acefc9aa370840827412c35a2b34 (
plain)
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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <grarpamp@gmail.com>) id 1SiDwO-0004iJ-Ie
for bitcoin-development@lists.sourceforge.net;
Sat, 23 Jun 2012 00:11:04 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.210.47 as permitted sender)
client-ip=209.85.210.47; envelope-from=grarpamp@gmail.com;
helo=mail-pz0-f47.google.com;
Received: from mail-pz0-f47.google.com ([209.85.210.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1SiDwN-0007Ot-U1
for bitcoin-development@lists.sourceforge.net;
Sat, 23 Jun 2012 00:11:04 +0000
Received: by dalh21 with SMTP id h21so2771533dal.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 22 Jun 2012 17:10:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.202.99 with SMTP id kh3mr14427472pbc.157.1340410257974;
Fri, 22 Jun 2012 17:10:57 -0700 (PDT)
Received: by 10.143.156.17 with HTTP; Fri, 22 Jun 2012 17:10:57 -0700 (PDT)
Date: Fri, 22 Jun 2012 20:10:57 -0400
Message-ID: <CAD2Ti29zRc38K1DGfe=NC2PMZwCQs55LV1pkN4wuLntrgdchiw@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.0 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(grarpamp[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.6 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1SiDwN-0007Ot-U1
Subject: [Bitcoin-development] Wallet related bug?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 23 Jun 2012 00:11:04 -0000
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.
|
