Bitcoin Core 32.0 Puts Node Security in Focus

Avatar photo

ByJordan Lee

October 4, 2026

Bitcoin Core’s forthcoming maintenance release addresses node performance and security as the SEC considers new custody rules and Bitcoin ETF flows remain uneven.

Bitcoin’s most concrete infrastructure development this week is a forthcoming Bitcoin Core release focused on node performance and security, not a change to the network’s consensus rules. Version 32.0 is targeted for October 10, after its first release candidate entered testing on September 14.

The update includes faster block validation, revised fee estimation and making PSBT version 2 the default for Partially Signed Bitcoin Transactions. It also fixes two security issues relevant to node and wallet operators. A software release does not alter Bitcoin’s consensus rules or require operators to upgrade, but it gives them changes to review against their own setups.

One fix addresses a wallet-name command-execution flaw that required authenticated wallet creation and a configured `walletnotify` command. Another resolves memory exhaustion in the new web and REST server. CoinDesk reported that, before the fix, 16 unauthenticated REST connections in testing drove memory use from 46 megabytes to about 3 gigabytes in roughly a minute.

These are operational and security improvements, rather than a protocol milestone. That distinction is significant in a decentralized network: improvements to commonly used software can help operators run nodes more safely, but they do not themselves change the rules that nodes use to validate blocks and transactions.

Regulatory developments are proceeding on a separate track. On October 1, the U.S. Securities and Exchange Commission proposed rules for custody of crypto assets by investment advisers and regulated funds. The proposal would permit limited self-custody and allow state-chartered trust companies to serve as custodians. It also updates audit and broker-dealer custody requirements. The comment period will last 60 days after publication in the Federal Register; the proposal is not a final rule.

SEC Chair Paul Atkins said the proposal would provide a clear framework and a compliant pathway for advisers and funds. The agency is using existing authority after the Clarity Act stalled in the Senate in September, CNBC reported. That could let regulators address some custody questions without waiting for comprehensive legislation, but the proposal’s final terms and practical effects remain undecided.

Custody requirements can shape how advisers and funds hold Bitcoin, but they do not change the Bitcoin protocol or guarantee increased institutional demand. The proposed rules govern intermediaries and asset handling, not the network’s engineering. Keeping those layers distinct helps clarify what the SEC action does—and does not—mean for Bitcoin.

ETF flows offer a separate measure of investor activity, though recent figures show volatility. U.S. spot-Bitcoin ETFs reportedly attracted roughly $2.65 billion in September, their second-largest monthly inflow since October 2025. On October 1, they recorded a $102.7 million inflow after a $148.7 million outflow in the previous session. That daily reversal is not enough to establish a lasting trend, and flows do not indicate changes to Bitcoin’s software or security.

Citi-linked commentary also pointed to U.S. Treasury repurchases of longer-dated bonds as a factor easing pressure in longer-maturity Treasury markets. Citigroup raised its 12-month Bitcoin target, citing renewed ETF inflows, stronger crypto activity and supportive macro conditions. It expects about $5 billion in crypto investment-product inflows over the next year, describing allocations by advisers and brokerages as slower but more persistent. These are market assessments, not protocol developments.

Taken together, the week’s developments are unfolding at distinct layers: maintainers are preparing a security-focused software release, the SEC is considering custody standards, and fund flows remain uneven. No major Bitcoin consensus-rule activation was reported. For node operators, the immediate task is to review the Core release notes and test the update before deployment.

Leave a Reply

Your email address will not be published. Required fields are marked *