That's just the way it is... Your file is huge. Time for a new one (or a bigger machine... although the software might not be able to handle such a large file even with big resources.)
An example on wallet.dat size impact... I don't know how you are patient to sync it
(or maybe you have it on 24/7)
An example on wallet.dat size impact... I don't know how you are patient to sync it
(or maybe you have it on 24/7)Lets see:
[1] its the ~100 leaked private keys related to the spam attack. I opened and resynced it just for this thread which took me ~7 hours. Bitcoin core acts very slow with such a big wallet file. It was ~110 MB before opening it, most of the time was resyncing.
| | | ~size | | | #TX | |
| fresh | | | 96KB | | | 0 |
| regular | | | 2MB | | | ~300 |
| spam[1] | | | 421MB | | | 195508 |
[1] its the ~100 leaked private keys related to the spam attack. I opened and resynced it just for this thread which took me ~7 hours. Bitcoin core acts very slow with such a big wallet file. It was ~110 MB before opening it, most of the time was resyncing.
Nice digging, I actually cant open the spam file anymore. Not sure why, but core just hangs itself. From the log OP posted it looks like they cranked up their keypool for some reason.
Code:
2016-02-06 17:03:37 keypool reserve 54500
What does the debug.log say directly after you start the wallet?
There should be something like this:
Code:
2016-02-05 05:50:07 init message: Loading wallet...
2016-02-05 05:50:07 nFileVersion = 110200
2016-02-05 05:50:07 Keys: 0 plaintext, xxx encrypted, xxx w/ metadata, xxx total
Alternativly, what does getwalletinfo return for keypoolsize?
my wallet.dat size : 358M