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.
net: do not apply whitelist permissions to onion inbounds by mzumsande
This change just makes sense. Why? Inbound Tor connections don’t reveal the peer’s network address because that is specifically what Tor was built to do. So it makes no sense to apply whitelist permissions to inbound Tor connections because they are ineffective.
If you want to read more on how Tor works, you can check out this article, as understanding why inbound Tor connections don’t reveal their network address is the main point of this PR.test: Prevent disk space warning during node_init_tests by ryanofsky
mzumsande saw that they were getting a Disk space warning when running the `src/test/node_init_tests.cpp` test. The reason was that it was being run on mainnet instead of regtest.
This PR changes this test from using mainnet to using regtest.coins: warn on oversized
-dbcacheby l0rincFrom what I understand of this PR the user can set their -dbcache size but as most developers know users will do anything and everything but use your project correctly. So obviously users will set a dbcache size that is too large for their system. This can cause issues like OOM errors, heavy swaping, or grinding the system to a halt.
This change detects if the dbcache is too large for the users system and then gives them a warning. So you’re still allowed to do so but atleast there is a warning letting you know of what you’re doing.
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.
Users can encounter cases where script checks are unexpectedly enabled (e.g. after reindex, or when assumevalid/minimumchainwork gates fail). Without an explicit line, they must infer state from the absence of a message, which is error-prone.
The existing “Assuming ancestors of block …” line does not reliably indicate whether script checks are actually enabled, which makes debugging/benchmarking confusing.
IRC meeting notes
Every week on Thursday, there is an IRC meeting. Here are some short notes from that meeting.
Kernel WG Update (TheCharlatan)
TheCharlatan: not much to share this week besides wanting to ask for review on the API PR #30595
Cluster Mempool WG Update (sdaftuar, sipa)
sipa: main PR to review remains sdaftuar's #28676, which has been rebased and is getting reviews addressed. in parallel, i have a few other PRs; i think #33157 is close (28676 is rebased on top of that one, so it's a dependency). we've been talking with glozow and sdaftuar about package RBF, for after cluster mempool
Stratum v2 WG Update (sjors)
Sjors[m]1: Review welcome on #33374. Would be nice to get in v30, but no need to delay the release for it. There's also a bunch of fixes that have been backported, not sure when we want to cut rc2? ryanofsky anything you need? Just a subtree update or more?
Then fanquake asked a question and a small discussion began
MuSig2 WG Update (achow101)
achow101: No major updates. PR to review is #29675 and I've been addressing comments.
v30.0
(there was a decent amount of conversation on this topic, checkout the full meetings in minutes for the full discussion)
For the full log, check the meeting in minutes
Releases
v30.0rc1 is out. If you have the chance, please give it a test.
This is the testing guide.
Thank you for reading. Be sure to tune in again next week for your updates on Bitcoin Core!
 | A guest post by
|