<bitcoin-git>
[bitcoin] stringintech opened pull request #33877: kernel: Rename in-memory DB option setters and simplify API (master...2025/11/kernel-in-mem-options) https://github.com/bitcoin/bitcoin/pull/33877
<bitcoin-git>
[bitcoin] maflcko reopened pull request #31823: tests: Add witness commitment if we have a witness transaction in `FullBlockTest.update_block()` (master...2025-02-07-featureblockpy-witnesscommitment) https://github.com/bitcoin/bitcoin/pull/31823
<bitcoin-git>
[bitcoin] maflcko closed pull request #31823: tests: Add witness commitment if we have a witness transaction in `FullBlockTest.update_block()` (master...2025-02-07-featureblockpy-witnesscommitment) https://github.com/bitcoin/bitcoin/pull/31823
<bitcoin-git>
[bitcoin] maflcko opened pull request #33869: refactor: Avoid -W*-whitespace in git archive (master...2511-git-archive-ws) https://github.com/bitcoin/bitcoin/pull/33869
<bitcoin-git>
[bitcoin] glozow merged pull request #33003: test: add option to skip large re-org test in feature_block (master...2025-07-test-featureblock-skiplargereorg) https://github.com/bitcoin/bitcoin/pull/33003
<bitcoin-git>
bitcoin/master 8810642 brunoerg: test: add option to skip large re-org test in feature_block
<bitcoin-git>
bitcoin/master e652b69 merge-script: Merge bitcoin/bitcoin#33003: test: add option to skip large re-org test in...
<bitcoin-git>
[bitcoin] frankomosh opened pull request #33858: test: add unit test coverage for the empty leaves path in MerkleComputation (master...merkle-empty-path) https://github.com/bitcoin/bitcoin/pull/33858
2025-11-11
<bitcoin-git>
[bitcoin] hebasto opened pull request #33857: depends, doc: Learn `x86_64-w64-mingw32ucrt` host and document it (master...251111-doc-ucrt) https://github.com/bitcoin/bitcoin/pull/33857
<bitcoin-git>
[bitcoin] yuvicc opened pull request #33856: kernel, validation: Refactor ProcessNewBlock(Headers) to return BlockValidationState (master...2025-11-refractor_bool_to_blockvalidationstate) https://github.com/bitcoin/bitcoin/pull/33856
<corebot>
https://github.com/bitcoin/bitcoin/issues/29415 | Broadcast own transactions only via short-lived Tor or I2P connections by vasild · Pull Request #29415 · bitcoin/bitcoin · GitHub
<corebot>
https://github.com/bitcoin/bitcoin/issues/33565 | net_processing: rename RelayTransaction to better describe what it does by vasild · Pull Request #33565 · bitcoin/bitcoin · GitHub
<corebot>
https://github.com/bitcoin/bitcoin/issues/33565 | net_processing: rename RelayTransaction to better describe what it does by vasild · Pull Request #33565 · bitcoin/bitcoin · GitHub
<bitcoin-git>
[bitcoin] fanquake closed pull request #30059: Add option dbfilesize to control LevelDB target ("max") file size (master...dbfilesize_param) https://github.com/bitcoin/bitcoin/pull/30059
<bitcoin-git>
[bitcoin] fanquake merged pull request #33433: test: rpc_bind: Skip nonloopback test if no such address is found (master...qafix_rpc_bind_nonloopback_unavail) https://github.com/bitcoin/bitcoin/pull/33433
<bitcoin-git>
bitcoin/master 79b4c27 Luke Dashjr: Bugfix: QA: rpc_bind: Skip nonloopback test if no such address is found
<bitcoin-git>
[bitcoin] hebasto opened pull request #33841: cmake: Switch to `minisketch` upstream build system (master...251110-minisketch) https://github.com/bitcoin/bitcoin/pull/33841
<bitcoin-git>
[bitcoin] maflcko opened pull request #33840: test: [refactor] Use reference over ptr to chainman (master...2511-assert-func) https://github.com/bitcoin/bitcoin/pull/33840
<bitcoin-git>
[bitcoin] glozow reopened pull request #33565: net_processing: rename RelayTransaction to better describe what it does (master...rename_RelayTransaction) https://github.com/bitcoin/bitcoin/pull/33565
2025-11-09
<bitcoin-git>
[bitcoin] achow101 closed pull request #33832: refactor: Add missing include in util/result.h (master...refactor/add-missing-include-util-result) https://github.com/bitcoin/bitcoin/pull/33832
<bitcoin-git>
[bitcoin] achow101 closed pull request #33833: script: Remove dead nullptr check in VerifyScript (master...refactor/verifyscript-remove-null-check) https://github.com/bitcoin/bitcoin/pull/33833
<bitcoin-git>
[bitcoin] 777genius opened pull request #33836: refactor: Remove redundant boolean comparisons across codebase (master...refactor/bool-comparisons-cleanup) https://github.com/bitcoin/bitcoin/pull/33836
<bitcoin-git>
[bitcoin] 777genius opened pull request #33835: refactor: Remove redundant ternary operator in wallet HaveChain() (master...refactor/wallet-redundant-ternary) https://github.com/bitcoin/bitcoin/pull/33835
<bitcoin-git>
[bitcoin] 777genius opened pull request #33834: refactor: Remove redundant boolean comparisons in txgraph.cpp (master...refactor/txgraph-bool-comparisons) https://github.com/bitcoin/bitcoin/pull/33834
<bitcoin-git>
[gui] ilkinsufi closed pull request #905: Increase tooltip wrap threshold from 80 to 100 characters (master...qt-increase-tooltip-threshold) https://github.com/bitcoin-core/gui/pull/905
<bitcoin-git>
[bitcoin] 777genius opened pull request #33833: script: Remove dead nullptr check in VerifyScript (master...refactor/verifyscript-remove-null-check) https://github.com/bitcoin/bitcoin/pull/33833
<bitcoin-git>
[bitcoin] 777genius opened pull request #33832: refactor: Add missing include in util/result.h (master...refactor/add-missing-include-util-result) https://github.com/bitcoin/bitcoin/pull/33832
<bitcoin-git>
[bitcoin] maflcko opened pull request #33825: refactor: Add missing include in bitcoinkernel_wrapper.h (master...2511-bld-include) https://github.com/bitcoin/bitcoin/pull/33825
<bitcoin-git>
[bitcoin] maflcko opened pull request #33824: ci: Enable experimental kernel stuff in most CI tasks (master...2511-ci-dev-mode-kernel) https://github.com/bitcoin/bitcoin/pull/33824
<bitcoin-git>
[bitcoin] maflcko opened pull request #33823: ci: Use cmake --preset=dev-mode in test-each-commit task (master...2511-ci-preset-test-each) https://github.com/bitcoin/bitcoin/pull/33823
<bitcoin-git>
[bitcoin] Ataraxia009 opened pull request #33813: Changing the rpcbind argument being ignored to a pop up warning, inst… (master...rpc-bind-warning) https://github.com/bitcoin/bitcoin/pull/33813
<bitcoin-git>
[gui] waketraindev opened pull request #910: Added test coverage for qt gui#901 console history filter (master...2025-11-gui-filtered-qt-tests) https://github.com/bitcoin-core/gui/pull/910
<glozow>
You can just do things! But if you're interested and don't know where to start, maybe a comment in #bitcoin-core-pr-reviews? I'm very happy to help people ramp up / look for things to do
<glozow>
I didn't say I have bitcoin, I have pizzas
<stickies-v>
i thought core devs don't have bitcoin
<glozow>
Perhaps we can use this channel or #bitcoin-core-pr-reviews as a helpdesk for it next week. Please please do join in :)
<abubakarsadiq>
From novo__: Hi I won't be available for the irc meeting. This is the update for SIlent Payments; josibake is off for now, so I and theStack will be taking over the PRs. A new silentpayments secp module PR has been opened by theStack https://github.com/bitcoin-core/secp256k1/pull/1765 (limited to full-node scanning to make it easier to merge). We will update https://github.com/bitcoin/bitcoin/pull/28122
<l0rinc>
and we're writing an article for Bitcoin magazine about our benchmarking and optimization efforts
<TheCharlatan>
yes, purpleKarrot had suggested a naming in his own experimental api. I think it makes sense, but it does break convention with other C APIs under the bitcoin-core umbrella, e.g. minisketch and libsecp256k1.
<TheCharlatan>
This versioning approach seemed a bit confusing to some, and would still practically tie bitcoin core versioning with the kernel library.
<laanwj>
i'd guess that works for languages that have a very active bitcoin community, like rust, yes
<TheCharlatan>
I talked to a few people working on language-specific bitcoin tooling (bitcoinj, rust-bitcoin, btcsuite) and some have voiced support for hosting bindings under their org umbrella. A project even offered nice domain names :P
<laanwj>
would make sense to make a repository for that under bitcoin-core
<TheCharlatan>
I.e. should these live in bitcoin-core/bindings, bitcoin/bindings, or somewhere else.