Bitcoin Core 32 has completed its final testing: RC1 was submitted on 9/14, with the goal of releasing the official version on 10/10. No consensus rules are changed. The focus is mainly on how nodes estimate fees, verify blocks, and how wallets build transactions.
For fee estimation, it will take another look at the transactions currently queued in the mempool; when congestion eases, the quote can move through faster. Block verification defaults to using 8 threads for parallel prefetching, and block syncing (“chasing blocks”) should be a bit faster. Several wallet-related commands have switched by default to PSBTv2—if you’re integrating with hardware wallets or services, pay attention to compatibility.
In addition, a command-execution risk in walletnotify scenarios was fixed, and the memory exhaustion issue in the new Web service has also been blocked before rollout. Friends running nodes can test-drive it first in the test environment.$BTC #BitcoinCore
For fee estimation, it will take another look at the transactions currently queued in the mempool; when congestion eases, the quote can move through faster. Block verification defaults to using 8 threads for parallel prefetching, and block syncing (“chasing blocks”) should be a bit faster. Several wallet-related commands have switched by default to PSBTv2—if you’re integrating with hardware wallets or services, pay attention to compatibility.
In addition, a command-execution risk in walletnotify scenarios was fixed, and the memory exhaustion issue in the new Web service has also been blocked before rollout. Friends running nodes can test-drive it first in the test environment.$BTC #BitcoinCore
