Using Qt version 5.15.5. So, in the console, when I type the importaddress command, it gives me an error even though I've got the wallet loaded up. If I close the wallet and give it another shot, it tells me something different. Anyone have a clue why it’s not working with the wallet?
importaddress command issues
3 replies 415 views
gr3g.0rbitHero Member
Posts: 1025 · Reputation: 2646
#2Apr 4, 2025, 03:00 PM
How about Bitcoin Core's version?
The latest Bitcoin Core version 26.0 uses QT v5.15.10.
I'm unable to reproduce this in v26.0 with "deprecatedrpc=create_bdb" to create a legacy wallet file.
The wallet loads and I'm able to import a watch-only address.
Try upgrading to the latest version and/or try manually loading the wallet via loadwallet "wallet_name" command.
See if it'll actually load without any error, if not, there may be something wrong with the wallet.dat file or the way it's loaded. (more info on that may help)
Running Bitcoin Knots version v25.1.knots20231115 (the latest version of Knots.)
The wallet file I tried adding it to is a brand new one.
When I try to the loadwallet command, it says "Wallet useage is restricted. (code -18)".
Using a non-Descriptor Wallet didn't make any difference.
I tried to use Sparrow wallet aswell but it looks like it won't import particular addresses.
UPDATE: When I tried using Bitcoin Core v25.?.? it came up with a Descriptor wallet error, even though it's not actually a Descriptor wallet.
I installed the latest Bitcoin Core (v26.0.0) and now it's working (with the original wallet) but when I close it and run Bitcoin Knots it still shows the error. (To be clear: I've never run Core and Knots at the same time.)
So the problem is partially solved, though I don't know why knots20231115 and Core v25.?.? wouldn't let me add a watch-only address using importaddress.
gr3g.0rbitHero Member
Posts: 1025 · Reputation: 2646
#4Apr 4, 2025, 11:43 PM
I've just finished testing Bitcoin Knots' latest version and it seems like an unreported issue,
you can report it to their repo to see if the developers can make it work.
For now, the workaround is to use the command line instead.
I used bitcoin-cli to issue the command and it worked as intended, of course set the necessary config/args to enable RPC.