Bitcoin Core’s November 13, 2026, weekly update reported three changes relevant to developers working with node processes, RPC requests and block data:
- On Windows, the
bitcoinwrapper now waits for its child process to finish and forwards its exit status. - Each element in a JSON-RPC batch is now parsed independently, preventing a non-object element from inheriting the preceding request’s
id. CScriptWitnessnow stores the witness stack in serialized form. The update says this reduces memory use when deserializing a valid block in the worst case from 106.8 MiB to 6.0 MiB.
The update also summarized IRC discussions and review work, rather than announcing those items as completed changes. Topics included a kernel-wrapper RFC; a benchmarking-group experiment with reindex-chainstate that connects blocks out of order without a precomputed hints file or reliance on assumevalid; more than 300 surviving mutations found by QA in validation.cpp; 300 review findings for the QML GUI; and a reactivated Erlay working group discussing whether BIP-434 could replace a custom handshake.