[bitcoin] practicalswift opened pull request #21795: fuzz: Terminate immediately if a fuzzing input ever causes a DNS lookup (belts and suspenders) (master...fuzz-terminate-on-dns-lookup) https://github.com/bitcoin/bitcoin/pull/21795
there are lots of improvements being worked on by various people, some related to consensus rules, but far more things in p2p improvements (mostly in bitcoin core), generic software improvements in various software, other software stack built on top, ...
Are there any upcoming plans for optimizing Bitcoin? (Other than Taproot, Schnorr)
in any case, this channel is about bitcoin core really
Has Bitcoin Core ever done an intended hard fork?
sipa: <hard fork count>.<soft fork count>.<patch count> could be a numbering system for bitcoin
If Bitcoin were on semver, then 0.x would mean Bitcoin is prone to backwards-incompatible changes
bitcoin itself doesn't have a version number
the next release of Bitcoin Core will be 22.0
meshcollider: if you mind giving a quick look to https://github.com/bitcoin/bitcoin/pull/20867 , fanquake asked you for review some time ago, and many other wallet people ACKed (or previous versions of it without nits-fixing)
it does seem somewhat of a centralization problem. The BIPs repo is a venue for sharing proposed changes to Bitcoin, and one person decides who can update it, and also decides whether or not they should ever be replaced/supplemented?
you asked why bitcoin core doesn't use something other than assert(), I answered why. There is, to my knowledge, nothing in bitcoin core that will abort() in a debug build and not in a release build, which appears to be what you want.
yanmaani: bitcoin core generally has historically treated assert() as "if this isn't true, we probably have buggy hardware, or otherwise may lose funds, continuing is unsafe". so running without assertions is definitely *not* a goal
How come Bitcoin doesn't use a custom assert macro? That way, if NDEBUG is set, assert could be ((void)__VA_ARGS__) instead, allowing for compilation without assertions to be made.
The PR serves as a proof of concept for how this can be implemented in Bitcoin Core, but is currently in a draft because I have been trying to build confidence that this wouldn’t harm other software on the network.