matrix2021

What is the result of

Where did you put the openssl.cnf file?

What OpenSSL version?

Wait a sec, that’s kinda misleading. Descriptors aren’t just about security. If Bitcoin Core had skipped the descriptor thing and went straight to BIP 44 paths, I’d still argue that exporting private keys should be…

You might be able to use a DirectTV dish. They're all over the place and many aren’t in use.

Only receive data. But for people in countries where the internet is sketchy, this could be a good way to use your phone wallet.

There’s a free Blockstream satellite service out there, which is awesome. Check out their announcement for more info.

Looks like your shutdown messed up the database flush. It’s reapplying state changes from block data, which is super I/O intensive. If your disk is slow, it’s gonna drag. Are you using an external drive? That could…

The problem is automating scriptSig creation for random scripts isn’t feasible. Bitcoin Core needs to know how to construct those scripts to process transactions.

The node's IsStandard check isn’t as strict as what the wallet enforces. The node doesn’t rely on standard templates like the wallet does, so it’s a bit more flexible.

Importmulti can import private keys too, but it’s meant for scenarios where you have existing private keys. Plus, it is handy for using partial transactions.

Both import formats do the same thing. The different notation changes how it reads the address but it boils down to the same outcome.

Nope. Bitcoin Core has specific accepted script formats. Your redeem script isn’t one of them, so it just warns you. It adds the script and address, but can’t create valid inputs for anything outside standard formats.

Sounds like you didn't rescan the blockchain. If you imported with a timestamp of "now", it assumes no history. Just run rescanblockchain to find any transactions related to it.

Bitcoin Core v31.0 is out now! You can grab it from their official site. This version comes packed with new features, tons of bug fixes, and better performance. And don't forget, older versions like 28.x are no longer…

So, the deal is that those multipath descriptors weren’t a thing until version 29.0. If you're on 28.1, that’s why you're getting that "Key path value '<0;1>' is not a valid uint32" error. Just upgrade to 29.0 and you…

Totally agree. No real consensus limits on outputs except the overall block weight. Outputs can have any opcodes, even invalid ones, until you hit that block weight limit. And the only consensus validation happens when…

Snaps are a bit tricky because of their sandboxing. When you run a Snap app, it can't access random spots on your file system. Best bet is to grab the binary tarball from bitcoincore.org and place the binaries where you…

Yeah, bip32derivs shows the derivation path for a key. Some signers need it while others don’t. It really depends on the software or hardware you're using to sign. But here's the kicker: if you share that PSBT, the…

For sure you need to upgrade. Bitcoin Core relies on features from C++17 and C++20 that older compilers simply can't handle. Trust me, it's mandatory if you want to build without issues.