BIP 394 gives the rawtr() descriptor, used in Bitcoin Core since version 24.0, a specification of its own
The descriptor names a Taproot output by its output key alone, and the BIP warns that it cannot prove no script path exists.
The descriptor names a Taproot output by its output key alone, and the BIP warns that it cannot prove no script path exists.
The merged change closes a gap in the reference validator, which only checked the witness UTXO field, and adds a test vector for it.
The 6 November newsletter also reports Antoine Riard's view that BIP54 activation could be discussed in the second half of 2027.
Version 0.2.0 of the Testnet 5 proposal, merged on 4 November, changes one number and names its reference implementation.
Fabian Jahr's proposal combines BIP 458 half-aggregation and BIP 459 full-aggregation; inputs can opt out with a plain BIP 341 signature.
The draft by Tim Ruffing, Jonas Nick and Fabian Jahr specifies a non-interactive way to compress many BIP 340 signatures into one, with a reference implementation and test vectors.
The 30 October releases 0.21.6-beta and 0.20.7-beta mitigate CVE-2026-98432 for Lightning nodes on Linux; the project says only a kernel patch fixes it.
A self-referential channel announcement crashed Core Lightning 25.02 to 26.04 on every restart; separately, a two-round protocol lets FROST and MuSig2 wallets send silent payments without BIP changes.
CVE-2026-117350 let a peer exhaust memory with TCP urgent data on non-Linux systems; all three are the first disclosures under the new fast track for easily discoverable bugs.
The major release adds Tor PoW defences, a global transaction-relay backlog with a new bandwidth cap, and fixes a private-broadcast IP leak; three medium or high severity 30.0 bugs will be disclosed in two weeks.