<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #23054: Use C++11 member initializer in CTxMemPoolEntry (master...2109-cpp11MemberInitMempool) https://github.com/bitcoin/bitcoin/pull/23054
<bitcoin-git>
[bitcoin] jnewbery opened pull request #23053: [fuzz] Use public methods in addrman fuzz tests (master...2021-09-addrman-fuzzer-public-methods2) https://github.com/bitcoin/bitcoin/pull/23053
<bitcoin-git>
[bitcoin] Shubhankar-Gambhir opened pull request #23052: test: use miniwallet in test_rpc function in feature_rbf.py (master...master) https://github.com/bitcoin/bitcoin/pull/23052
<Kiminuo>
jonatack: https://github.com/bitcoin/bitcoin/pull/12677#pullrequestreview-759043318 - I don't really want to try to beat somebody in addressing these but I should have some time over the coming days to address that so I'll do it, ok? Saying that just because I don't want to compete with somebody
<bitcoin-git>
[bitcoin] jonatack opened pull request #23050: log: change an incorrect fee to fee rate, and vice-versa (master...fee-vs-feerate) https://github.com/bitcoin/bitcoin/pull/23050
<bitcoin-git>
[bitcoin] jb55 closed pull request #18985: bloom: use Span instead of std::vector for `insert` and `contains` [ZAP3] (master...2020-05-bloom-span) https://github.com/bitcoin/bitcoin/pull/18985
<laanwj>
it indeed looks like "dpkg --add-architecture armhf && apt update && apt install libc6:armhf" is enough to run armhf release bitcoin-cli on aarch64 host
<laanwj>
name connections (where the network isn't known) are a special case that's outside of the normal per-network proxy handling, names never come from the P2P network but only in special cases (as mentioned in https://github.com/bitcoin/bitcoin/pull/22959#issuecomment-922915197)
<gribble>
https://github.com/bitcoin/bitcoin/issues/22949 | fee: Round up fee calculation to avoid a lower than expected feerate by achow101 · Pull Request #22949 · bitcoin/bitcoin · GitHub
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #23043: ci: Set --nocleanup for Windows functional tests (master...2109-ciWinCleanup) https://github.com/bitcoin/bitcoin/pull/23043
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #23042: net: Avoid logging AlreadyHaveTx when disconneting misbehaving peer (master...2109-netLogDisconnect) https://github.com/bitcoin/bitcoin/pull/23042
<bitcoin-git>
[bitcoin] theStack opened pull request #23037: test: fix confusing off-by-one nValue in feature_coinstatsindex.py (master...202109-test-fix_namount_offbyone_in_coinstatsindex) https://github.com/bitcoin/bitcoin/pull/23037
<bitcoin-git>
[bitcoin] jonatack opened pull request #23036: test: use test_framework.p2p `P2P_SERVICES` constant in functional tests (master...use-test_framework-P2P_SERVICES-in-functional-tests) https://github.com/bitcoin/bitcoin/pull/23036
<bitcoin-git>
[bitcoin] jonatack opened pull request #23035: p2p, rpc, test: expose tried and refcount in getnodeaddresses, update/improve tests (master...getnodeaddresses-tried-and-reference_count) https://github.com/bitcoin/bitcoin/pull/23035
<kallewoof>
The signet faucet bitcoin core node is so slow that the faucet is experiencing time-outs now. It has quite a lot of keys. If someone wants to do some analysis to see where to speed tihngs up before I do some utxo consolidation, let mek now.
<bitcoin-git>
[bitcoin] luke-jr opened pull request #23027: Bugfix: Skip tests for tools not being built (master...bugfix_util_test_config) https://github.com/bitcoin/bitcoin/pull/23027
<shiza>
That's a lot easier way to understanding it than bitcoin.it/regression_test_mode!
<bitcoin-git>
[bitcoin] martinus opened pull request #23025: bench: update nanobench add `-min_duration_ms` (master...2021-09-update-nanobench) https://github.com/bitcoin/bitcoin/pull/23025
<shiza>
It's showing that on bitcoin-cli's output (and error code -8) upong requesting it getnewaddress of 'bech32m' type (in what seems an API feature unpromised by `help getnewaddress`, but somehow treated because the error message doesn't just tell 'Unknown address type'.)
<bitcoin-git>
[bitcoin] fanquake closed pull request #22987: qa: Fix "RuntimeError: Event loop is closed" on Windows (master...210915-loop) https://github.com/bitcoin/bitcoin/pull/22987
<shiza>
Can anything in Bitcoin Core transform a legacy wallet into a descriptors wallet in a single step?
<bitcoin-git>
bitcoin/master 357f0c7 Hennadii Stepanov: ci: Enable more functional tests on Windows MSVC task
<bitcoin-git>
bitcoin/master f559326 Hennadii Stepanov: qa: Fix "RuntimeError: Event loop is closed" on Windows
<bitcoin-git>
[bitcoin] fanquake closed pull request #23023: Update and rename contrib/seeds/suspicious_hosts.txt to contrib/semil… (master...patch-1) https://github.com/bitcoin/bitcoin/pull/23023
<bitcoin-git>
[bitcoin] Peterblanco021091 opened pull request #23023: Update and rename contrib/seeds/suspicious_hosts.txt to contrib/semil… (master...patch-1) https://github.com/bitcoin/bitcoin/pull/23023
<harding>
shasum on linux has an option to ignore invalid input, which was used on the BitcoinCore.org instructions. For OSX, there's no such option, and I wonder if you could just insert a line in the SHASUMS file that said "bitcoin-22.0.blah.tar.gz SUCCESS" and make it look like it passed or something. For the Windows instructions, I think you had to do by-eye verification anyway.
<roconnor>
IIUC at least some of these signers are not using dedicated bitcoin signing keys, and thus may use the same key for signing emails or whatnot.
<gribble>
https://github.com/bitcoin/bitcoin/issues/22949 | fee: Round up fee calculation to avoid a lower than expected feerate by achow101 · Pull Request #22949 · bitcoin/bitcoin · GitHub
<prayank>
I had added some topic for meeting today according to bitcoin core wiki. It's 12 AM here and I want to sleep early today. Shared my thoughts here which most probably would not matter, but better than suggesting a topic and saying nothing: https://gist.github.com/prayank23/e385e31427989c47e715d61556772d02
<bitcoin-git>
bitcoin/master 350e034 Jon Atack: consensus: don't call GetBlockPos in ReadBlockFromDisk without lock
<bitcoin-git>
bitcoin/master cdf12c7 W. J. van der Laan: Merge bitcoin/bitcoin#22895: consensus: don't call GetBlockPos in ReadBloc...
<bitcoin-git>
[bitcoin] theStack opened pull request #22998: test: use MiniWallet for make_utxo helper in feature_rbf.py (master...202109-test-use_miniwallet_for_make_utxo) https://github.com/bitcoin/bitcoin/pull/22998
<bitcoin-git>
[bitcoin] hebasto opened pull request #22987: qa: Fix "RuntimeError: Event loop is closed" on Windows (master...210915-loop) https://github.com/bitcoin/bitcoin/pull/22987
<bitcoin-git>
[bitcoin] hebasto closed pull request #22980: qa: Ignore `--failfast` option of `test_runner.py` on Windows (master...210915-failfast) https://github.com/bitcoin/bitcoin/pull/22980
<bitcoin-git>
[bitcoin] naumenkogs closed pull request #18925: Add extra thread for scheduler, move TorControl and OpenAddedConnections to scheduler (master...2020_05_extra_scheduler_thread) https://github.com/bitcoin/bitcoin/pull/18925
<bitcoin-git>
[bitcoin] hebasto opened pull request #22980: qa: Ignore `--failfast` option of `test_runner.py` on Windows (master...210915-failfast) https://github.com/bitcoin/bitcoin/pull/22980
<laanwj>
MarcoFalke: fanquake: do we still need travis enabled on bitcoin/bitcoin?
<_aj_>
laanwj: i assume there's some secret to authenticate "this is the bitcoin project from github" (which might let you corrupt the ccache and blah), but maybe that wasn't one of the ones that got leaked
<bitcoin-git>
[bitcoin] MarcoFalke closed pull request #22940: fuzz: Move all addrman fuzz targets to one file (master...2109-fuzzMergeAddrman) https://github.com/bitcoin/bitcoin/pull/22940
<bitcoin-git>
[gui] jarolrod opened pull request #423: qt: make initTranslations a member function of BitcoinApplication class (master...move-init-translations) https://github.com/bitcoin-core/gui/pull/423
<bitcoin-git>
[bitcoin] ryanofsky opened pull request #22976: scripted-diff: Rename overloaded int GetArg to GetIntArg (master...pr/intarg) https://github.com/bitcoin/bitcoin/pull/22976
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #22970: doc: Update snap release process for new versioning scheme (master...2109-docSnapRel) https://github.com/bitcoin/bitcoin/pull/22970
<_aj_>
lucaferr: you need neighbouring nodes that have upgraded to support taproot; "bitcoin-cli getpeerinfo | grep subver" -> look for 0.21.1 or 0.21.99 or 22.0.0 or 22.99.0
<laanwj>
of course, updating the documentation and verification instructions is still important, but it should be a one-time thing. I did have a note on verifying the binaries in the testing instructions here: https://github.com/bitcoin/bitcoin/issues/22634
<bitcoin-git>
[bitcoin] jarolrod opened pull request #22966: doc: Improve documentation around the ACK statement (master...ack-documentation) https://github.com/bitcoin/bitcoin/pull/22966
<harding>
Re: verification instructions, I just opened a PR to temporarily hide them until they can be updated. If I can get a couple approach ACKs from established contributors in the next hour or two, I'll merge tonight. https://github.com/bitcoin-core/bitcoincore.org/pull/796
<bitcoin-git>
[gui] hebasto closed pull request #261: Display node address in peer table with monospace font for clean alignment (master...node-address-monospace) https://github.com/bitcoin-core/gui/pull/261
<bitcoin-git>
[bitcoin] klementtan opened pull request #22959: cli: Display all proxies in -getinfo (master...getinfo-multiple-proxies) https://github.com/bitcoin/bitcoin/pull/22959