Welcome to the next crypto level
← Nexorena

Technologie & IA

Bitcoin ABC disables Bloom filters by default in version 0.34.5

The eCash node software changes the option that lets clients request filtered data from peers. The team suggests that applications relying on this service prepare to migrate or keep a node configured for it.

Nexorena Editorial Team

Bitcoin ABC disables Bloom filters by default in version 0.34.5

A settings change for eCash nodes

Bitcoin ABC released version 0.34.5 on November 20, 2026. The release notes say that the `-peerbloomfilters` option is now off by default. A node using this setting no longer provides NODE_BLOOM service to peers. The project still lets operators enable the option explicitly. The change affects installations that use the default settings and the services they offer to connected applications.

A Bloom filter allows an application to specify the transaction data it is interested in. The peer uses the filter to limit the data it sends. The mechanism can let false matches through, an inherent property of the filter. An application that still relies on this service needs access to a node that offers it. It may lose that access when an operator installs the new release with default settings, even if the node continues to operate on the eCash network.

Chronik as an alternative source of data

The team suggests that peer-to-peer clients depending on NODE_BLOOM consider Chronik or run their own node with the option enabled. Chronik is an indexer built into Bitcoin ABC. Its documentation describes interfaces for blocks, transactions, scripts, addresses, and tokens. It distinguishes between an application connecting to the service and an operator deploying an instance.

Migration means checking which data the client expects and how it receives them. A wallet that queried a peer for filtered information will need to adapt that part of its operation if it switches to Chronik. Keeping a node configured with NODE_BLOOM temporarily allows operators to control access to the service the client depends on during the transition. The release notes give no timetable for removing the option later.

The context of the November upgrade

The release follows the eCash network upgrade on November 15. The team says the first block produced after that upgrade was number 975611. It had asked operators to move to the 0.34 series to stay in sync, in connection with the renewal of replay protection. The notes for version 0.34.5 describe the change to the filter setting offered to peers.

For node operators, the two events have different effects. Moving to the 0.34 series addresses the synchronization requirement announced for November. The default change affects clients that rely on a particular service. Operators who also host a wallet or another client can check for this dependency before deploying the new release.

Article sources

Written with love byOlivia ParkerMeet this editorial pen name ↗

Explorer Nexorena