hebasto: in any case I think the criterion for translation should be "does this message make sense to a user/translator", you can assume knowledge of bitcoin terminology such as blocks, transactions, wallets, etc, but not internals of the software
2. we officially announced the residency today. We're still looking for great engineers who want to spend summer working on Bitcoin or Lightning with us. If you know anyone who might be appropriate, please send them our way at https://residency.chaincode.com/#apply
[bitcoin] achow101 opened pull request #15301: tests: When testing with --usecli, unify RPC arg to cli arg conversion and handle dicts and lists (master...fix-tests-cli-args) https://github.com/bitcoin/bitcoin/pull/15301
[bitcoin] practicalswift opened pull request #15296: tests: Add script checking for deterministic line coverage in unit tests (master...test_deterministic_coverage) https://github.com/bitcoin/bitcoin/pull/15296
in any case you can't expect that people will change version bytes at all, or that bitcoin won't, so using them as identifiers would be a poor decision.
Bullit: #bitcoin please.
stevenroose: if it's a BIP, no need to refer to anything but bitcoin and testnet
I've modified transaction transmission and sometimes (very rarely though) I'm getting "non-mandatory-script-verify-flag (Witness program hash mismatch)". Any idea how it might happen or where should I look for? Transactions are generated by "bitcoin-cli sendtoaddress"
promag: or perhaps void the bitcoin.conf wallets, and load wallet w1?
Hey all, I've been working on making bitcoin builds with Guix, which I think can replace gitian for our release process one day. It is a very exciting package manger which will bring much better supply chain security to Bitcoin. Let me know your thoughts! https://github.com/bitcoin/bitcoin/pull/15277
losing my mind with bitcoin-qt shutdown
What are some "network identifiers" that can be used to generally refer to a "bitcoin network"? I.e. Mainnet, Testnet, Liquidv1, ...
Is there anything we can do to head off funds loss from typos/copypaste errors with decriptor importing? The use of descriptors as user/api handled key material seems like a step backward for Bitcoin, as we're now introducing ways for simple typos (or clbuttic errors) to cause funds to go off to space.