Quote from: nc50lc on April 17, 2025, 04:10:35 AM

Quote from: takuma sato

Anyway, how do you do this without screwing up the wallet.dat file? There has been so much stuff added to Bitcoin Core.

Load it using "File->Restore" and it'll be copied to the correct folder then it will be loaded automatically.
Migrating a legacy to descriptor wallet isn't mandatory as of now.

After that, export the wallet's addresses or public keys (for p2pkh) or redeem scripts if you have any (for P2SH, rarely used in 2013).
One way to do that is to use dumpwallet command but addresstype=legacy has to be added to your bitcoin.conf file (requires restart) for it to output legacy addresses.

bitcoincore.org/en/doc/29.0.0/rpc/wallet/dumpwallet

Quote from: takuma sato on April 17, 2025, 01:00:46 AM

I want to use the new psbt method, but I don't know how to select specific utxos in Coin Control and put it into a psbt file.

You'll need a watch-only wallet in your online Bitcoin Core for that.
Create one by ticking "Disable Private Keys" during Create Wallet process.

You can then import the addresses, public keys or redeem scripts contained in your offline Bitcoin Core wallet via importdescriptors command.
References for you to check how to use it:

bitcoincore.org/en/doc/29.0.0/rpc/wallet/importdescriptors (use timestamp "now" to skip rescan)
github.com/bitcoin/bitcoin/blob/master/doc/descriptors.md

(this part is tedious since your wallet isn't HD, you wont be able to utilize extended public keys)

Rescan the wallet/sync the node, then tick "Enable coin-control features" in the 'Settings->Options' and you'll be able to select specific UTXO in the 'Send' tab.
Using the 'Send' tab of you watch-only wallet will let you create a PSBT that you can send to your offline wallet.

Quote from: nc50lc on April 17, 2025, 04:10:35 AM

Quote from: takuma sato

Anyway, how do you do this without screwing up the wallet.dat file? There has been so much stuff added to Bitcoin Core.

Load it using "File->Restore" and it'll be copied to the correct folder then it will be loaded automatically.

What does this do specifically? Because you mentioned it will be "loaded". What is loaded? I would imagine, this just loads the wallet normally, but there is an additional step here:

Quote from: nc50lc on April 17, 2025, 04:10:35 AM

After that, export the wallet's addresses or public keys (for p2pkh) or redeem scripts if you have any (for P2SH, rarely used in 2013).
One way to do that is to use dumpwallet command but addresstype=legacy has to be added to your bitcoin.conf file (requires restart) for it to output legacy addresses.

bitcoincore.org/en/doc/29.0.0/rpc/wallet/dumpwallet

So I don't get it. What is loaded if the wallet requires that you export the keys? Why is this step necessary? The addresses are legacy addresses (p2pkh). I just don't understand what im doing there. I think im being confused. This is just to export the public keys to create a watch-only wallet on the online wallet im assuming? So this means that "File->Restore" is all I need to do to have the private keys ready.

I may have been confused with the descriptor thing, which required some more convoluted migration process. Why are they going to force this? Why not just keep it backwards compatible? That just introduces extra steps to guarantee you eventually screw up. Also I don't need anything but legacy addresses, everything else for me is just clutter.