bitcoin/master fab8cd5 MarcoFalke: Revert "ci: Run fuzzer task for the master branch only"
bitcoin/master fa27745 MarcoFalke: ci: Bump fuzz tasks to jammy
bitcoin/master 2ab4fbe fanquake: Merge bitcoin/bitcoin#24292: Revert "ci: Run fuzzer task for the master br...
provoostenator: nice to see https://github.com/bitcoin-core/gui/pull/555 -- it's very similar to my approach I'm currently working on. The only concern is we are past "string freeze" point -- hope no new and changed strings, although, did not check yet
[gui] jonatack opened pull request #554: Add and improve peers tab address fields dev notes and tooltips (master...improve-peers-tab-address-fields-extracomments-and-tooltips) https://github.com/bitcoin-core/gui/pull/554
re: rpc bindings in bitcoin core, the sentiment seems to be 'no', that there is a percieved need for something to be 'well-maintained' doesn't mean it needs to end up on the plate of the maintainers of bitcoin core, see also the discussion in #23468 (and that's about Python, not some language)
bitcoin/master 7f2f35f Hennadii Stepanov: build: Fix gcc-cross-x86_64-w64-mingw32-10.3.0 in Guix
bitcoin/master b3617a9 Hennadii Stepanov: build: Point Guix to recent commit on the master branch
bitcoin/master 9761192 fanquake: Merge bitcoin/bitcoin#24348: build: Fix Guix build for Windows (attempt 2)...
laanwj: wrt 23542, potential privacy gain but if many DNS seeds take advantage of it before the seeder and bitcoin core code reading them are updated... be good to have those updated before this release (or the next one)
[bitcoin] vasild opened pull request #24357: refactor: make setsockopt() and SetSocketNoDelay() mockable/testable (master...mockable_SetSocketNoDelay_and_setsockopt) https://github.com/bitcoin/bitcoin/pull/24357
i meannn it's the same discussion every time but clearly bitcoin and cryptocurrency is still experimental on several levels, which makes it useful as a warning/disclaimer, and also not in some other ways, it's really not worth getting into that discussion over a single word in the documentation
I'm not sure if this is the proper place to ask but the bitcoin client qt displays "This is experimental software." when you go to about -> About Bitcoin Core. Is there a goal to consider the software no longer experimental? Like, it won't be experimental when a milestone/feature set is reached.
start bitcoin again, wait for it to sync up, kill it with -9
to reproduce: install bitcoin core, sync it until it's like a week behind, close it orderly
Why doesn't Bitcoin Core sync db after completing ibd?
Can move to #bitcoin-dev if the answer is "complicated" :-)
provoostenator: Probably should be in #bitcoin-dev (and I think only luke-jr can answer it) but BIP 148, 149 weren't given single digits and allocated at similar time. But they were entitled to be SegWit specific rather than general activation mechanism