This week in Bitcoin Core
Bitcoin Core contributor kevkevin covers some of the latest updates...
Hello 👋 folks, I’m kevkevin. I’m an open-source developer and reporter for Insider Edition. Last week, I reviewed several pull requests from the Bitcoin Core repo. Here’s what I found notable.
Merged PR’s
Every week, several changes are officially added to Bitcoin Core. This week, 8 changes were merged. Here are some I thought were interesting from this week.
docs: Undeprecate datacarrier and datacarriersize configuration options by bitschmidty
This change was in response to the deprecation marker for the datacarrier and datacarriersize configurations. This was motivated by the fact that while being marked as deprecated, there is no plan to remove these configurations in the near future.
This means that Bitcoin Core will support the configuration to change the data carrier and data carrier size. I wonder how many node runners have moved from Bitcoin Core to Knots, knowing that this option may be removed in the future, and whether this will convince them to switch back?net: improve the interface around FindNode() and avoid a recursive mutex lock by vasild
From what I understand in this PR, there was a chance of a recursive mutex lock in the FindNode() function, which is unsafe. If you are unaware of what a mutex is, it is basically a lock that guards a resource. This way no two threads are accessing it at the same time, causing inconsistencies.
This PR makes it safer to use the FindNode() function without getting caught in a recursive mutex lock and having to restart your BitcoindFuzz: extend CConnman tests by vasild
This change affects the fuzz testing suite by extending the CConnman tests. There were 4 functions that were added to the fuzz tests. You might be wondering why they were not added earlier.
The reason why they were not added earlier is that previously, fuzzing those methods would have resulted in real socket functions being called in the operating system. You can imagine that it is undesirable functionality. But now that #21878 is merged, we can fuzz those previously unfuzzed functions.
Open PR’s
There are always changes being updated and reviewed in real-time. Here are some notable PR’s that are still up and looking for reviews.
Adds a new RPC
sendrawtransactiontopeer, which sends a single tx to a specific peer.
After the transaction is sent to the peer it is forgotten and not stored in the local mempool.This rpc can serve several purposes. For example, it allows you to “spoof” an initial retransmission from a different “trusted” peer, making it appear as if the original participant was never aware of the transaction. It can also be useful in testing and simulation environments.
IRC meeting notes
Every week on Thursday, there is an IRC meeting. Here are some short notes from that meeting.
Cluster Mempool WG Update (sdaftuar, sipa)
sipa: the last week or so i’ve mostly been looking into how good block building post-clustermempool would work with our current code. Improving that wasn’t really the primary goal, but it’s still interesting to know how close we are. Will share diagrams soon, but when replying 2023 mempool/block data, we get some 1/10000 blocks that miss more than 1% of fees, and some 1/3000 blocks that miss more than 0.1% of fees.
glozow: I’ve been building package rbf / package test accept with 28676. Mostly throwaway code but it’s helped with review.
MuSig2 WG Update (achow101)
achow101: #29675 has been getting lots of review that I’ve been working on addressing.
v30.0
achow101: Any new issues found in rc2 testing? The milestone has a couple things in it so we are expecting a rc3. Or any other topics to discuss today?
glozow: I think 30 won’t come out tomorrow
achow101: The tag date has been pushed back to the 10th
sipa: 2025/10/10 is a nice number
For the full log, check the meeting in minutes
Releases
Bitcoin Core v30.0 has been rescheduled to be tagged on Oct 10th, 2025
Thank you for reading. Be sure to tune in again next week for your updates on Bitcoin Core!
 | A guest post by
|