Bitcoin (BTC) node software’s latest version was officially announced on the 27th. This update mainly improves how data is read during transaction propagation and block verification processes. Previously, each peer managed its own output queue; this structure has been removed, and a common queue has been introduced inside the node to minimize memory and CPU overhead.
The new transaction output limit is 14 per second, and the connected peers are designed to apply a speed factor of 2.5 times. It also sets the separate transaction data bandwidth at 12 MB per 10 minutes, allowing higher burst capacity for brief periods. During block linking, by pre‑reading previous transaction output information from the chain state database, multiple workers (typically 8–16) can perform verification concurrently, improving verification speed.
Bitcoin Core stated in this release note that the code tag of the previous version was 32.0 and that no official distribution had been made, but the actually distributed version is 32.1. Network access methods have also changed; in automatically generated Tor hidden services, when a Tor daemon is supported, PoW (Proof of Work) will be applied. The ElGamal (type 0) encryption scheme used for I2P is slated to be removed before or during v34, and the low‑usage CJDNS support is under review.
There was also concern about security; on the 28th a security advisory noted that node memory consumption could become an issue via select() handling in operating systems other than Linux. The advisory classified the severity as “medium” and stated that Linux nodes are not affected. Subsequent automatic LLM analysis identified vulnerabilities in versions 29.5, 30.4, 31.2, and 32.1 that were corrected and distributed. Bitcoin Core’s security policy is to quickly disclose any vulnerabilities found in major releases; this advisory was issued alongside the updated version.
The proposal also includes a cross‑border agreement BIP‑361. It contains a plan to gradually restrict existing ECDSA and Schnorr signatures; it remains in “draft” status. Whether it will be activated or which network it will apply to has not yet been decided, but there is potential for future application. CoinBase ($COIN) in its technical document released on Oct 13 recommended preparing for cross‑border conversion, and forese that the process could take many years. This information points more at software improvement and policy direction than price or investment analysis.