Skip to main content
11 events
when toggle format what by license comment
Apr 27, 2021 at 7:08 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Mar 28, 2021 at 3:24 answer added memtha timeline score: 1
Feb 19, 2021 at 0:04 history edited memtha CC BY-SA 4.0
added 336 characters in body; edited tags
Feb 15, 2021 at 23:46 comment added memtha Supplemental: I just did the dump | load thing and restarted the node. Looks like the node is reindexing starting from block 1. So that might be a good sign.
Feb 15, 2021 at 23:34 comment added memtha @PieterWuille that's is what I thought, though I was hoping that that was what was going wrong with my import attempt. bitcoind says the -upgradewallet option is not valid and I see nothing similar in the man file that shipped with the source. I am having a heck of a time finding binaries of db4.8-utils for debian. Though I'm not quite sure if the wallet version is the problem, since the old and new are theoretically both 4.8.
Feb 15, 2021 at 22:07 comment added Pieter Wuille You only need the passphrase to sign transactions (i.e, sending coins). You'll have to provide it using the walletpassphrase RPC (or if you use the GUI, it'll just ask you when needed).
Feb 15, 2021 at 22:01 comment added memtha @PieterWuille the old setup was the release build (80% sure). I will try upgradewallet next once my current attempt to importwallet via bitcoin-cli finishes, if it does not work. Does it matter that the old wallet.dat file is passphrase protected? At what point should I enter the passphrase (and how)?
Feb 15, 2021 at 21:21 comment added Pieter Wuille It doesn't look like this is related to BDB at all, actually, looking at the stacktrace. Can you try starting with -upgradewallet cmdline argument? (make a backup of wallet.dat first, of course).
Feb 15, 2021 at 21:10 comment added Pieter Wuille Was the old Bitcoin-Qt binary self compiled or a release binary? Release binaries always use BDB 4.8.
Feb 15, 2021 at 21:10 comment added Pieter Wuille What often works (but make sure you have a wallet.dat backup) in these cases is running "db<ver>_dump old_wallet.dat | db<ver>_load new_wallet.dat", where you replace the <ver> with the respective version number (e.g. db5.3_dump, db4.8_load). This'll create a new_wallet.dat file that's compatible with whatever version you select.
Feb 15, 2021 at 20:09 history asked memtha CC BY-SA 4.0