< September 2026 >
Su Mo Tu We Th Fr Sa 12345678 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30
2026-08-29
<bitcoin-git>
bitcoin/master 05e49b3 Hennadii Stepanov: Merge bitcoin/bitcoin#36107: iwyu: Fix warnings in `src/init` and treat th...
<bitcoin-git>
[bitcoin] hebasto opened pull request #36116: iwyu: Fix warnings in `src/rpc` and treat them as errors (master...260828-iwyu-rpc) https://github.com/bitcoin/bitcoin/pull/36116
<bitcoin-git>
[bitcoin] hebasto merged pull request #36107: iwyu: Fix warnings in `src/init` and treat them as errors (master...260827-iwyu-init) https://github.com/bitcoin/bitcoin/pull/36107
2026-08-27
<winterrdog>
pinheadmz: i had worked on sth similar in my repo before but never committed/pushed it since i found a similar PR open. i’ve committed what i had and pushed it here: https://github.com/winterrdog/bitcoin/pull/2. might be of help, take a look
<corebot`>
https://github.com/bitcoin/bitcoin/issues/35780 | http: linger-close after parse errors so clients can read the reply by b-l-u-e · Pull Request #35780 · bitcoin/bitcoin · GitHub
<corebot`>
https://github.com/bitcoin/bitcoin/issues/35632 | intermittent ci failure: interface_http.py", line 558, in check_whitespace_in_headers // ConnectionAbortedError: [WinError 10053] An established connection was aborted by the software in your host machine · Issue #35632 · bitcoin/bitcoin · GitHub
<willcl-ark>
Moneyball: I'm catching up from "donors have approached me expressing concern that Bitcoin Core devs "aren't paranoid enough about AI cyber threats" and that the Core project isn't sufficiently leveraging AI tools for tasks like assisting issue and PR triage, code review, and test case development."
<johnny9dev>
It does almost feel too early to add anything additional to bitcoin core. On top of it, bitcoin core is likely extremely well understood already by llms so is there any markdown file that can even really add any additional value to this?
<jonatack>
Moneyball: AI has been (over-)used to prompt finished-looking, verbose, often nonsensical, techno-babbly BIP drafts by nyms that (often) open them directly as PRs to the BIPs repo. OTOH, it is being used well by established bitcoin protocol devs to propose useful BIPs.
<dergoegge>
Not to jinx it but, maybe the fact that the bitcoin network is still up and running, is a hint that core is not behind on things?
<johnny9dev>
yes bitcoin's strong engineering fundamentals are paying off
<sedited>
Moneyball, "issues as PRs" has not worked well here so far. Many bots do take things off the issue tracker, but a lot of them produce slop that then needs more triaging and work from more people. Take this PR from today for example, which took away attention from a bunch of us, but didn't do anything to move things forward: https://github.com/bitcoin/bitcoin/pull/36055 . Can obviously say
<eugenesiegel>
andrewtoth: where? in bitcoin core or somewhere else?
<Moneyball>
My high level point is "how does the bitcoin ecosystem know what the Core project is and is not doing with respect to AI in order to reassure folks that the contributors to the project aren't sticking their heads in the sand"
<Murch[m]>
My impression is that many or most of the Bitcoin Core contributors have started incorporating AI tooling into their workflows and given their prior expertise get great use out of it.
<Moneyball>
Several people, including donors have approached me expressing concern that Bitcoin Core devs "aren't paranoid enough about AI cyber threats" and that the Core project isn't sufficiently leveraging AI tools for tasks like assisting issue and PR triage, code review, and test case development.
<stickies-v>
#topic Bitcoin Core and AI usage, perception and reality (Moneyball)
<johnny9dev>
as a reminder, the staging branch is what we hope to merge into bitcoin/bitcoin
<bitcoin-git>
[bitcoin] fanquake merged pull request #35900: iwyu: Fix warnings in `src/interfaces` and treat them as errors (master...260805-iwyu-interfaces) https://github.com/bitcoin/bitcoin/pull/35900
<bitcoin-git>
[bitcoin] purpleKarrot opened pull request #36101: doc: Add an error handling strategy (master...error-handling-strategy) https://github.com/bitcoin/bitcoin/pull/36101
<bitcoin-git>
bitcoin/master 204256c merge-script: Merge bitcoin/bitcoin#35900: iwyu: Fix warnings in `src/interfaces` and tr...
<praxeology>
I'm going to present evidence that fees will not be sufficient to motivate miners to pile enough work to secure transactions. Hence argue for adjusting bitcoin's tail mint limit per block: from its current scedule of halving down to 0; to having a low constant money supply inflation rate function of something between 0.05% per year (2040 inflation rate) to 0.78% per year (current inflation rate).
<praxeology>
Evidence for the proposal I'd like to make kind of requires lots of block fee and price data for me to make a strong case. The raw data is a 409kB libre office ods spreadsheet. 287kB compressed. I could summarize it and link to a website like blockchain.com. I'm not sure if its appropriate to attach an ods document or images to the bitcoin dev mailing list.
<praxeology>
I created a rough draft of a BIP discussing and resolving the current bitcoin mint reward issuee (eventually resulting in poor transaction security). Is there a good place for me to post it for discussion? Anyone interested in looking at it?
<dviola>
I'd probably change freespacechecker.cpp to consider 1 or all paths bitcoin-qt knows about, combine their sizes and estimate
<dviola>
hebasto: hi, I managed to solve that specific problem here: https://github.com/bitcoin-core/gui/pull/948#issuecomment-5337430176 -- but honestly, I think freespacechecker.cpp needs an overhaul, right now when passing -blocksdir via gArgs.IsArgSet, dataDir becomes the blocksdir path and by the look of it, freespacechecker.cpp wasn't designed around that assumption, but it works
<l0rinc>
dergoegge: dergoegge/loupe-bitcoin-core-public#1 is already worked on in https://github.com/bitcoin/bitcoin/pull/35752 (just converted to draft because of review, will push an update soon)
<bitcoin-git>
bitcoin/master 8b5da67 fanquake: common: remove ::runtime_error from RunCommandParseJSON
<bitcoin-git>
bitcoin/master 2232d6a Martin Zumsande: test: move index_reorg_crash to baseindex_tests
<bitcoin-git>
[bitcoin] fanquake merged pull request #35847: test: move more tests to `baseindex_tests` and run them for all indexes (master...202607_baseindex_tests) https://github.com/bitcoin/bitcoin/pull/35847
<bitcoin-git>
bitcoin/master a3597e2 Martin Zumsande: test: move BuildChain helper into test mining util
<bitcoin-git>
[bitcoin] musaHaruna closed pull request #35970: Test persisted health requires mempool restore (master...test-persisted-health-requires-mempool-restore) https://github.com/bitcoin/bitcoin/pull/35970
<bitcoin-git>
[bitcoin] musaHaruna opened pull request #35970: Test persisted health requires mempool restore (master...test-persisted-health-requires-mempool-restore) https://github.com/bitcoin/bitcoin/pull/35970
<fjahr>
2. https://github.com/asmap/kartograf/pull/148 The IRR DBs we were downloading have inconsistent formatting and since we expected them to always end with an empty line, sometimes the very last entry was skipped when that was not the case. This only resulted in in a single additional prefix mapping (if any) in the final file in the recent runs and bitcoin nodes mappings were not affected by it.
<fjahr>
included in IRR DBs, so the real impact is for our purpose appears to be small. On the last 5 historical maps, the impact to the bitcoin network is that 3-4 peers which previously did not have a mapping do have one with the new map. See a more detailed analysis by Joris here: https://gist.github.com/jorisstrakeljahn/30235e943db90f78fecb9e397ffee9c5
<hebasto>
Dropping MSVC support has many benefits, but the drawback is that it reduces the diversity of compilers testing the Bitcoin Core codebase, which was noted by cfields during the last CoreDev.
<hebasto>
On Windows, as on most other systems, there is more than one compiler that can be used to build Bitcoin Core.
<johnny9dev>
When I get closer I think I will create an issue in bitcoin/bitcoin with the plan and include tracking all of the steps we need to complete and look to start the PR for the first chunk.
<bitcoin-git>
[bitcoin] brunoerg opened pull request #35958: net: align v2 message type validation with v1 range (master...2026-08-v2-fix) https://github.com/bitcoin/bitcoin/pull/35958
<bitcoin-git>
[bitcoin] hebasto opened pull request #35957: ci: Define `BOOST_MULTI_INDEX_ENABLE_SAFE_MODE` for debug builds (master...260812-boost-debug) https://github.com/bitcoin/bitcoin/pull/35957
<bitcoin-git>
[bitcoin] HowHsu opened pull request #35956: fuzz: scope fake clocks to target phases (master...fuzz-target-local-clock) https://github.com/bitcoin/bitcoin/pull/35956
<darosior>
_aj_: i don't know if it's worth the hassle of setting up pool payouts for a testnet. One easy way to achieve that would be to run ckpool in solo mode, this way miners subscribe to the pool with a Bitcoin address as their worker name (in clearnet, yolo SV1)
<bitcoin-git>
bitcoin/master a7b0b50 cyb3ralbert: doc: fix dead link in txrequest.h
<bitcoin-git>
[bitcoin] HowHsu closed pull request #34625: cluster_linearize: add tests and benchmarks for chain and tree-shaped clusters (master...linearize-tests) https://github.com/bitcoin/bitcoin/pull/34625
2026-08-10
<bitcoin-git>
[bitcoin] l0rinc opened pull request #35948: init: correct first-run disk space estimates (master...l0rinc/init-first-run-disk-space) https://github.com/bitcoin/bitcoin/pull/35948
<bitcoin-git>
[bitcoin] sedited merged pull request #33186: wallet, test: Ancient Wallet Migration from v0.14.3 (no-HD and Single Chain) (master...test_no_or_base_hd_wallet_migration) https://github.com/bitcoin/bitcoin/pull/33186
<bitcoin-git>
[bitcoin] sedited opened pull request #35946: rpc: Populate some skip type check args for openrpc (master...skip_type_check_openrpc) https://github.com/bitcoin/bitcoin/pull/35946
<bitcoin-git>
[bitcoin] hebasto opened pull request #35945: depends, qt: Add patch for missing header (master...260810-depends-qt-syncqt) https://github.com/bitcoin/bitcoin/pull/35945
<bitcoin-git>
[bitcoin] kwsantiago opened pull request #35938: blockstorage: fail instead of storing a null XOR key over a lost one (master...fix-missing-blocksdir-xorkey) https://github.com/bitcoin/bitcoin/pull/35938