rav3n_ninj4

Thanks for all the input! Set it up successfully. The VPN was lifesaver since I accidentally connected straight to the Bitcoin network at one point. But I think the simple setup doesn’t really need a VPN.

Started testing it out this way now. Might switch things up later. Appreciate the advice!

Nice, I set my full node to work with the Tor network. My bitcoin.conf is all set up for it. Now it listens only locally. I’ll use SSH port forwarding on my laptop. Like forwarding 28333 to 8333 on my full node. Hope…

Been running a full node on Bitcoin Core as a Tor hidden service for a bit now. It's set up on a virtual linux server. Looking to create watch-only wallets on my laptop using this full node to generate unsigned…

Yep, you got it! Your HD wallet's math is solid. Even if you lose wallet.dat, you can restore it using the xprv key. Running `listdescriptors` helps you get the keys for a watch-only setup online. I had similar…

Quick question, kind of off-topic but still relevant: I thought all wallets were HD wallets. So, new ones from Bitcoin Core are HD, but those old ones from a decade ago... not so much, right?

Nah, it’s a security measure. Signing needs the output script of what you’re spending. That info isn’t part of the input, so it’s extra data in PSBT. Also, you wanna know the amount to verify things. With non-segwit,…

Used decodepsbt to check the files in JSON. Major differences! From my user view, I did the same for both transactions. First, moved all from address 1 to 2. Then from 2 to 3. In the second transaction, I see an input…

Here's the analyzepsbt for the first transaction (3071 bytes): And for the second one (272 bytes). Looks like both had one input? But the first one is way bigger. Each adds around 50 bytes when signed, I assume that's…

You still got copies of the PSBTs you used? You could run analyzepsbt to check the input counts.

I switched to the qt-client after realizing it’s got a full PSBT workflow. Did two native SegWit transactions as a test. Signed them on my HW wallet, no issues, network accepted them. Surprisingly, the first PSBT was 3K…

I did some digging online and found this series of articles. The section on creating a PSBT the easy way seems perfect for me. Gonna give it a try. Saw HWI in the last article. Didn't know about it before. Seems useful,…

I'm on Core Client 27.1, just using the daemon for now. Thought about switching to the GUI, but first let me explain my setup. I've got a cold wallet on a Raspberry Pi and a watch wallet on a regular PC. They…

Is it okay to use the same Bitcoin address multiple times, ignoring privacy concerns? I read somewhere that if the nonce k used for the ECDSA signature isn’t random, it could expose your private key. Is that a…

Still confused. That BIP39 tool calls it a BIP39 seed, but isn’t that the same as my binary seed?

Yeah, normally you'd go through legacy wallets for that. You’ll have to convert it to WIF yourself.

Yes, but you need to encode the 'seed' into WIF first. You mean the seed, not the phrase, right? Only legacy wallets can use that command.

Running a daemon on a connected device isn't really cold storage even with -noconnect. A cold wallet should never touch the internet.

Cobra runs bitcoin.org, but yeah, bitcoincore.org is the real deal. But why care about Bitcoin Core if you're not planning to use it directly? Lightweight clients like Electrum could be better.

Wait, what limitations for a cold wallet? I thought it didn't need the network. I’d run it with the -noconnect option. RAM is okay, but RNG might be a concern.