> Bitcoin Core has spent more than a century of CPU time fuzzing individual functions and critical components (though oss-fuzz, Fuzzor, bitcoinfuzz and individual contributors), and decades of CPU time simulating small networks of full nodes under test (Antithesis, Fuzzamoto). I can’t establish causality from this alone, but my strong suspicion is that the sustained testing effort is an important reason these projects have become so robust.
Show more
More progress being made by @remix7531 on the libsecp256k1 Schnorr Signature (BIP 340) formal verification front:
I’ve pushed up a new round of -static-pie Bitcoin Core binaries that I’d like to get more testing of! More details on the mailing list:
Bitcoin Cores 29.x branch continues to receive maintenance. 29.4 has been released
Congrats to @andrew_s_toth for shipping his parallel input fetching work. Pretty clear impact
Big shout out to @n1ckler for a 7+ year stint as secp256k1 maintainer. Lots of valuable improvements made to the library, API, performance and otherwise, during that time. Looking forward to seeing any future Bitcoin research work!
Show more
Thanks to all the work done by @fjahr and pinheadz, libevent is no-longer a dependency of Bitcoin Core,
This means a minimal bitcoind, now only has a single, header only, external dependency; which is Boost MultiIndex. Work is ongoing to replace this too.
Show more
> After Bitcoin Core 0.14.0 and before Bitcoin Core 29.0, validating a specially-crafted block may cause the node to access previously freed memory.
> An attacker capable of mining a block with sufficient proof-of-work could have exploited this to crash victim nodes.
Show more
Cluster Mempool
Embedded ASmap
Private broadcast
A new tx output spender index
Stratum V2 / IPC interface updates
A more usable (experimental) kernel
Plenty of bug fixes and improvements
