Bitcoin Core developers released version 0.19.0.1 on November 24, 2019, delivering a broad maintenance and policy update to the software used by many Bitcoin full-node operators. The release did not change Bitcoin’s consensus rules. Its significance was operational: it altered wallet defaults, hardened peer-to-peer connectivity and signaled a migration path away from older payment and light-client mechanisms.
The release represented the public 0.19 series even though the downloadable build carried the extra “.1” suffix. Contemporaneous reporting and Bitcoin Optech’s November 27 account said a late-discovered bug affected the 0.19.0-tagged version, so 0.19.0.1 became the first release build users were encouraged to install. That distinction matters because “0.19.0” describes the major release line, while 0.19.0.1 identifies the actual binaries made available on November 24.
Safer defaults at the network edge
The most consequential node-level change was the addition of two outbound connections dedicated only to block relay. Those links did not process transactions or peer-address messages. The release notes said the design imposed little extra memory or bandwidth cost while making some partitioning attacks harder. This was a resilience measure rather than a protocol fork: each operator could upgrade independently, and nodes running earlier compatible versions could remain on the network.
Bitcoin Core also disabled BIP37 bloom-filter service by default by changing `-peerbloomfilters` to false. Bloom filters had allowed lightweight wallets to ask public full nodes for potentially relevant transactions, but serving those requests exposed full nodes to known denial-of-service vectors and created privacy concerns for light clients. Operators could still re-enable the service globally or for selected peers. The release notes explicitly cautioned wallet developers to consider specific BIP37 servers or another filtering system.
Version 0.19.0.1 added an optional `-blockfilterindex` setting and a `getblockfilter` RPC for BIP158 compact block filters. The index was estimated in the release notes to consume about 4 GiB. However, the software did not yet serve those filters over Bitcoin’s peer-to-peer network, so this was infrastructure for local use and future integration, not a complete replacement light-client service on November 24.
Wallets moved toward native SegWit
The graphical wallet began generating bech32 receiving addresses by default. These “bc1” addresses represented native SegWit outputs and could reduce the data needed when spending compared with SegWit wrapped inside pay-to-script-hash outputs. Users retained a graphical toggle and configuration option for another address type, an important compatibility escape hatch because support for sending to bech32 addresses was not universal in 2019.
The release also disabled BIP70 payment-protocol support in default builds, while permitting developers to compile it back in. Other wallet and application changes included a new `getbalances` RPC, an optional `avoid_reuse` wallet flag, improved Partially Signed Bitcoin Transaction handling and a CPFP “carve-out” in mempool policy designed to help two-party contract protocols preserve a fee-bumping path.
Why the release mattered
Bitcoin Core 0.19.0.1 was consequential less as a headline feature than as coordinated maintenance of shared infrastructure. Defaults determine what ordinary node operators actually provide to the network. On November 24, the project favored block-relay resilience, reduced exposure to bloom-filter abuse, native SegWit address creation and more explicit wallet privacy controls.
The limitations are equally important. Release availability did not measure adoption, and the cited records do not establish how many nodes upgraded on November 24. The changes also did not prove that partition attacks, wallet privacy leaks or compatibility failures had been eliminated. They documented a set of engineering choices made available to operators on that date.
The complete source packet and revision history are retained with the newsroom record.
Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.
This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.