Bitcoin Core 32.1 Fixes Conditional IP Exposure in Private Broadcast

Bitcoin Core announced version 32.1 on Oct. 27, giving full-node operators a fix for an IP-exposure path in its optional private-broadcast feature and changing RPC and peer-connection defaults. Full nodes verify blocks and transactions before relaying them across Bitcoin’s network. Version 32.1 caps the private-broadcast queue at 10,000 transactions and rejects new submissions when it is full. It also limits each transaction to 1,000 send attempts. Bitcoin Core released versions 31.2 and 30.4 for earlier branches. Version 31.2 includes the queue cap and marks private broadcast as experimental. The update changes data returned by several mempool RPC commands. By default, getmempoolinfo no longer returns the deprecated fullrbf field, and specified mempool responses omit bip125-replaceable unless compatibility options are enabled.

BeCrypto News shows a short excerpt and links to the publisher. The full report belongs to TokenPost.