Bitcoin Core’s planned release targets node performance, fee estimation and security, as reported ETF flows weaken after September’s inflows.
Bitcoin’s clearest infrastructure development this week is the planned release of Bitcoin Core 32.0, a node-software update focused on performance, transaction handling and security. CoinDesk reported that the first release candidate was tagged September 14, with the stable release targeted for October 10. That is a target rather than a guarantee; testing could delay the release.
The update adds a second, mempool-based fee estimator and parallel transaction-data fetching. During block processing, the software will use eight threads by default for that work. These changes affect how nodes handle transactions and estimate fees, not the rules that determine whether blocks and transactions are valid across Bitcoin’s network.
That distinction is central to the release. Bitcoin Core is open-source software, and node operators choose whether to upgrade. Version 32.0 does not change consensus rules, Bitcoin’s issuance schedule or the obligations of network participants. Its significance will depend on practical deployment: whether operators and services can upgrade smoothly and benefit from the operational changes.
The release also addresses two security issues. CoinDesk reports that a command-execution flaw has existed since Bitcoin Core 24.0 on non-Windows systems, affecting configurations that use `walletnotify`. Version 32.0 also fixes a memory-exhaustion issue in the new web server. These are software and operational risks, distinct from a change to Bitcoin’s consensus layer.
Wallet and service developers have a compatibility task, too. Four commands that create partially signed Bitcoin transactions will default to PSBT version 2. Applications can still request the older format, but services built around those Core commands should test their integrations before upgrading. The change illustrates how network infrastructure relies on a wider ecosystem of wallets and services, not just the node software itself.
CoinDesk’s October 8 reporting showed a reversal in U.S. spot-Bitcoin ETF flows. September had delivered about $2.65 billion in net inflows, but October’s cumulative flows had reached negative $165.6 million by the time of reporting. Year-to-date net inflows stood at $717 million, while cumulative inflows since January 2024 totaled $57.33 billion.
A much larger single-day withdrawal figure has appeared in coverage attributed to SoSoValue, but the supplied material identifies that figure as unconfirmed. It should not be presented as established fact. The verified monthly totals still show that ETF demand had weakened from September. They measure flows through investment products, not activity on Bitcoin’s peer-to-peer network, and do not establish why investors bought or sold.
CoinDesk also cited volatile Treasury yields, possible escalation of U.S.-Iran tensions and higher oil prices as headwinds. These are macroeconomic and geopolitical conditions, not changes to Bitcoin’s code. They may influence the environment in which fund investors make decisions, but the reporting does not establish a direct cause for the shift in ETF flows.
A related October 9 search result said XRP funds were the only tracked major crypto-asset ETF group showing inflows, while Bitcoin, Ether and Zcash funds recorded outflows. The supplied material includes no verified XRP flow figure or underlying data, limiting what can be concluded from that comparison.
For Bitcoin infrastructure, the week’s substantive development is the approaching Core release: faster transaction-data handling, a second fee-estimation method, security fixes and a wallet-compatibility change, without a consensus-rule shift. ETF and macro reports describe the wider financial backdrop, but they are separate from the engineering work underway in Bitcoin’s software.

