0xChad

Seriously, if you read through the original posts, it’s a mess! There are so many contradictions. It’s like the user doesn’t really own the wallet or something.

You’re asking why it can’t do that? Well, it hasn’t been implemented yet. But it’s not impossible. A feature for "prune by timestamp" could be added if there’s demand for it. Currently, you can manually prune by using…

That’s true, but remember testnets aren’t permanent. Like, they can get abandoned anytime. The current testnet3 might go soon just because it’s getting bloated.

That only works if OP_RETURN’s limit is above 80 bytes. Even a small message could turn into a bigger hex value when encrypted. So you totally didn’t test it before launching.

If the imported address matches the old one and starts with 1, there’s a chance that Blockchain messed up the encoding. You might need to revert it to an uncompressed format.

Have you actually put your app to the test? It looks like it’s misusing createrawtransaction and adding OP_Return in a weird way. And that’s not even broadcasting the transaction.

You can also use "timestamp": 0 for a full scan after import. Ideally, you set "now" for the first descriptors and use "0" for the last one, so it only scans once when everything's imported.

Your multisig descriptors might be using public keys or WIF, which won't work with ranges. 'Active' means the wallet should derive child keys from it, so you need a master/extended key with a path and a range.

Can you tweak your transaction fee after consolidating? Like, before sending out?

And just to clarify, Taproot is a form of SegWit. Bech32 (bc1q) is SegWit version 0, while Taproot (bc1p) is version 1.

Check the local sections below the homepage here. If your language is listed, post there for better support without the translation issues. If you stick with English, make sure to share details from the pinned help…

You're talking about the entropy, not the binary seed derived from it. Those words represent a pretty short binary value. You can check the entropy details in the BIP39 tool by toggling the right option.

Check your 'debug.log' for more details. Look in your bitcoin datadir. You should see lines that start with "Verifying last <N> blocks at level <N>" and end with "Verification: <message>". The nBlocks and level should…

From what I understand, just put the two numbers right after the command, separated by a space. You could also try named to specify the parameter names. Like this: $bitcoin-cli named verifychain checklevel=1 nblocks=0.

You can actually set it to start automatically. Go to Settings -> Options, and check "Start Bitcoin Core on system login" under the 'Main' tab. Then, in the 'Window' tab, you can minimize it to the tray instead of the…

Are you looking for the datadir option? You can start Bitcoin Knots with the choosedatadir command line argument. That should bring up the setup screen, which is handy. But just a heads-up, this only works for the GUI…

Coinb.in? If your mobile wallet can sign unsigned raw transactions, then you’re good. Otherwise, you’ll have to export your private keys to sign. Just be careful, it’s a manual process and you’ll need to be spot on with…

It definitely looks like an online wallet or an exchange situation unless you really had 22 BTC. Normally, non-custodial wallets manage change addresses automatically, or send the change back. Maybe fees ate up your…

Just to clarify, mBTC isn’t an altcoin. It’s a smaller denomination of Bitcoin. So if you sent 0.0093776 BTC, you should get pretty much the same back. The mBTC you see isn’t related to any altcoin like MBTC.

Tough to say for sure. Could be that zombie process holding the port. But usually, if that happens, you'd see a different error related to the data directory.