Setting Up Two Bitcoin Core Wallets: A Guide

20 replies 316 views
alpha23Member
Posts: 116 · Reputation: 79
#1Jul 4, 2018, 05:46 AM
I need a step-by-step guide for setting up two Bitcoin Core wallets. One should be on an offline laptop with the wallet.dat file, and the other online as a watch-only wallet. The wallet is from the Bitcoin v0.8.0 era, so I guess it might need to be updated? Details please.
4 Reply Quote Share
bear100Hero Member
Posts: 123 · Reputation: 2026
#2Jul 4, 2018, 06:13 AM
Honestly, I doubt there's a tutorial that covers everything you've described. You might have to create that guide yourself after figuring it out.
1 Reply Quote Share
Posts: 181 · Reputation: 24
#3Jul 4, 2018, 09:40 AM
You can get a public key and use it to set up a watch-only wallet. If you only have a private key, import it first, grab the public address, then create the watch-only wallet. Remember, you can’t spend from that.
4 Reply Quote Share
alpha23Member
Posts: 116 · Reputation: 79
#4Jul 6, 2018, 02:43 AM
My old wallet has like 100 addresses and notes on each transaction. I’ve heard there's a newer system (PSBT) that can help with offline signing and watch-only setups, but I really need a detailed tutorial to avoid mistakes. Plus, with the wallet being so old, I guess it needs converting to a new format.
3 Reply Quote Share
gang2015Member
Posts: 682 · Reputation: 62
#5Jul 7, 2018, 11:43 PM
I think @Churchillvv is right; a specific tutorial likely doesn’t exist. Since Bitcoin-qt 0.8.0 uses BDB, it should still open in the latest version without issues but yeah, conversion may be necessary.
1 Reply Quote Share
0xChadNewbie
Posts: 513 · Reputation: 3
#6Jul 8, 2018, 03:36 AM
If you haven’t set an HD seed in versions after 0.13, your wallet stays non-HD, which can complicate things. Migrating to a descriptor wallet could work, but you'll have a ton of single key descriptors to deal with.
4 Reply Quote Share
Posts: 185 · Reputation: 37
#7Jul 8, 2018, 08:33 AM
I haven't tried this with a legacy wallet, but for the watch-only wallet, make sure to import only the public key descriptors. Don’t mess with the private keys!
0 Reply Quote Share
0xChadNewbie
Posts: 513 · Reputation: 3
#8Jul 8, 2018, 08:44 AM
Wouldn't it make more sense to use combo(pubkey) descriptors for the watch-only wallet? They match any address type except taproot. You can use getaddressinfo <address> to get the pubkey.
1 Reply Quote Share
rav3n_ninj4Senior Member
Posts: 30 · Reputation: 1643
#9Jul 8, 2018, 03:47 PM
That’s a good point. After migrating to a descriptor wallet, it should be HD. If you start with only one address, Bitcoin Core might not let you create a transaction due to no available change.
4 Reply Quote Share
Posts: 185 · Reputation: 37
#10Jul 8, 2018, 04:35 PM
Can you create unsigned transactions with the GUI? Maybe import some empty addresses along with the ones that have balances and then transfer funds to new bc1 addresses?
0 Reply Quote Share
0xChadNewbie
Posts: 513 · Reputation: 3
#11Jul 8, 2018, 08:52 PM
You can create unsigned transactions, but you might need to use the console. If the wallet is watch-only, you can copy PSBT to clipboard. But why risk higher fees?
2 Reply Quote Share
rav3n_ninj4Senior Member
Posts: 30 · Reputation: 1643
#12Jul 8, 2018, 10:06 PM
True, if it's a watch-only descriptor wallet, the 'Send' button changes to 'Create Unsigned'. Just keep in mind it should be made with 'disable_private_keys'.
2 Reply Quote Share
dave.forkMember
Posts: 375 · Reputation: 185
#13Jul 9, 2018, 01:46 AM
Great tip! I'll check the GUI client. Can I use the same data directory as Bitcoind? Can the GUI client hide behind a full node like Bitcoind?
0 Reply Quote Share
0xChadNewbie
Posts: 513 · Reputation: 3
#14Jul 9, 2018, 05:01 AM
Absolutely, the GUI can do everything bitcoind can. You can even use your existing bitcoin.conf for the GUI as long as it points to the right path.
1 Reply Quote Share
rav3n_ninj4Senior Member
Posts: 30 · Reputation: 1643
#15Jul 9, 2018, 07:49 AM
I usually stick with the standard '.bitcoin' directory in my home folder. If I accidentally run both clients simultaneously, could that cause data corruption?
1 Reply Quote Share
0xChadNewbie
Posts: 513 · Reputation: 3
#16Jul 9, 2018, 11:12 AM
I appreciate the input! Gonna study this more and test with a testnet wallet. Might build a non-HD wallet using v0.12 to safely replicate the process.
2 Reply Quote Share
rav3n_ninj4Senior Member
Posts: 30 · Reputation: 1643
#17Jul 11, 2018, 07:09 PM
Yeah, you can do that. The last one started won’t access the data directory. You could duplicate your wallet.dat and use that for testing.
1 Reply Quote Share
alpha23Member
Posts: 116 · Reputation: 79
#18Jul 11, 2018, 10:05 PM
Hey, just starting to install Debian and compile Bitcoin Core. So, there's no way to create a non-HD wallet on the latest version?
1 Reply Quote Share
0xChadNewbie
Posts: 513 · Reputation: 3
#19Jul 12, 2018, 12:08 AM
Correct, you’ll need to build v0.12 to get a non-HD wallet. After that, you can upgrade to the latest version but make sure the wallet works first.
1 Reply Quote Share
alpha23Member
Posts: 116 · Reputation: 79
#20Jul 12, 2018, 12:24 AM
I think getting testnet coins will help with migration testing. Hope everything works smoothly!
3 Reply Quote Share

Related topics