matrix2021

Full Member
24
Posts
612
Reputation
Nov 22, 2017
Joined
Recent posts
  • 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…

  • 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.

  • They *are* compliant, trust me. Just doesn't seem like it at first. For blocks 1 to 16, BIP34 says the height is encoded in a specific way. It uses opcodes OP_1 through OP_16, which map to hex values 0x51 to 0x60. For…

  • Oh for sure, the prenet genesis transaction has some quirks. First off, it doesn't have the transaction version included in the hash like usual. Plus, you find the nSequence in the CTxOut instead of the CTxIn. Lastly,…

  • Have you checked the sighash tests available on GitHub? They might help isolate the issue since signatures can shift due to different nonces. Those tests are more reliable for diagnosing what's wrong without the…

  • Just post your address and if you need testnet3 or testnet4. I have a few thousand of each just lying around.

  • Look up technological debt. It’s a valid reason to move on.

  • 1. Check the control block is the right size, which should be 33 bytes here. 2. The first byte of the control block gives you leaf_version after bitwise AND with 0xfe. 3. Pull out the p value from bytes 2 to 33. 4. Set…

  • There’s no straightforward formula like that. The Control Block actually defines a key and a bunch of merkle branch hashes. You hash the script to get a leaf hash, then combine that with the merkle hashes to get the…

  • Shouldn't legacy addresses solve this issue? The PSBT file should be smaller, right? Just wondering if there are downsides apart from higher fees.

  • Definitely go with PSBTs, they come packed with the info needed for signing. Raw transaction steps need you to supply that data separately, which is a hassle.

  • Yep, they fixed the wallet deletion problem during migration. About time!

  • Wait, is that feature actually in this release?

  • New Bitcoin Core v30.2 just dropped! Check out the release notes for all the new features and fixes.

  • Actually, quite a few people brought it up. And it’s not trolling, it could actually help. It’s not a twin implementation, it’s using the existing script interpreter from Bitcoin.

  • Not gonna lie, that’s impossible because BIP322 needs a ton of script code that most tools just don’t have. Like, look at Electrum it barely deals with scripts. Adding a script interpreter isn’t in the cards.

  • Check this out: https://mempool.space/testnet/tx/99588e8586b8be2eca492e4896a103b432e6d95fd8472de7bc7d67a5bbd36f73

  • Post your address. I’ve got plenty of satoshis to share.

  • For Bitcoin Core, we actually run unit and functional tests automatically with each PR. If a fix has tests included, regressions should be caught. Manual testing for everything is unrealistic, that’s why we have this…

  • Newly added code has tests for sure. Several issues were actually completely replaced with fresh code so that should cover it. Some problems popped up from dependencies, but we can tackle those by updating dependencies…