New Bitcoin Core Software Update Uses Bech32 Addresses by Default

The Bitcoin Core development team released the latest update on Nov. 24 to Bitcoin's original software client - the nineteenth in the coin's eleven-year history.

Releasing Bitcoin Core 0.19.0 was overseen by lead maintainer Wladimir J. van der Laan and was reportedly developed by over a hundred contributors over a roughly six month period.

The "Bech32" address format is now set for the first time as the default option in the Bitcoin Core wallet Graphical User Interface, having first been introduced in early 2018 with version 0.16.0.

Bech32 also reportedly improves interoperability with SegWit wallets, with transactions now requiring less data to be transmitted over the Bitcoin network - and thus included in the blockchain - thereby reducing costs.

Van Wirdum indicates that the updated software client also now makes it possible for users to start a pruned node immediately from setup, even those with low disk space.

Bloom Filters - a way for light clients, such as those running from mobile phones, to request relevant data from full nodes on the network - have now been deprecated, as they are deemed to be weak on privacy.

Instead of Bloom Filters, 0.19.0.1 is evolving toward supporting a newer solution called "Compact client-side block filtering", which essentially reverses the operation of Bloom Filters by having full nodes create filters for each block and enabling light clients to use these filters to determine whether transactions relevant to them may have happened in a block.

Bitcoin Core 0.19.0 has removed payment protocol from its GUI, noting that it was never widely adopted and that most wallets still use the more basic URI scheme to receive payments.

The minor features outlined include support for the Partially Signed Bitcoin Transactions protocol, which is useful for multi-signature and CoinJoin transactions.

This October, Bitcoin Core developer Greg Maxwell had criticized the "Attractive mystery" that fear of a 51% attack on Bitcoin entails, arguing that any mechanism cooked up to mitigate it always implies centralization and represents a far greater threat to the network's integrity.