Bitcoin Core 32 was released 26 days ago; no fork depends on it
Bitcoin Core 32.0 (21 Oct 2026) speeds up block validation, changes fee estimation and wallet defaults. It changes no consensus rules: there is no Bitcoin fork to prepare for. The BIP-110 soft fork attempt failed to gain miners in 2026.
No soft fork is currently signalling for activation in Bitcoin Core. Source: Bitcoin Core v32.0 (checked 12 Nov 2026).
What do I have to do?
Holders
Nothing to do
No fork. Your coins and addresses are unaffected. Fake "BTC upgrade" or "fork claim" sites are scams.
Exchange users
Nothing to do
Client releases do not pause deposits.
Stakers
Not applicable
Bitcoin is proof-of-work.
Node operators
Update to 32.1 (or 31.2 / 30.4 / 29.5)
Not mandatory, but recommended: 32.0 fixes a walletnotify command-execution bug present since v24 (non-Windows). Point releases for all maintained branches landed on 28 Oct 2026.
Source: Crypto Briefing (32.0 notes) (checked 12 Nov 2026)
Developers
PSBT v2 by default; fee estimates change
Four wallet RPCs now return PSBT version 2 unless you ask for v0; estimatesmartfee now blends mempool data and may return lower fees.
Source: Crypto Briefing (checked 12 Nov 2026)
Client versions for node operators
Latest point release per maintained branch (28 Oct 2026).
| Client | Recommended | Latest stable (live) | |
|---|---|---|---|
| Bitcoin Core Full node | v32.1 | v32.1 28 Oct 2026 | Latest stable includes it |
Versions: Bitcoin Core releases (checked 12 Nov 2026). Latest stable is read from each project's GitHub releases feed. All clients on the Patch Radar
Readiness
Reachable listening nodes only (Bitnodes crawler). Non-listening nodes, the majority, are not counted. No fork depends on this release, so this shows adoption, not a safety threshold.
Exchange pause board
Right now
| Network | Binance | KuCoin | Kraken | Coinbase | Gate | Bitget |
|---|---|---|---|---|---|---|
| BTC Bitcoin | Open | Open | Open | Open | Open | Open |
Last check 4 min ago. Coinbase's status page does not split deposits from withdrawals. "—" means the exchange does not list that network or does not report it.
Exchange notices
Timeline and date slips
- 21 Apr 2026 Bitcoin Core 31.0 (cluster mempool) Bitcoin Core 31.0
- 27 Jul 2026 BIP-110: mandatory signalling; ~0% of hashrate signalled, minority branch stalled KuCoin blog: BIP-110 stalls
- 14 Sep 2026 32.0rc1 tagged GitHub
- 21 Oct 2026 32.0 final GitHub
- 28 Oct 2026 32.1, 31.2, 30.4, 29.5 point releases GitHub
The target moved 1 time
| When | Was | Became | Source |
|---|---|---|---|
| 10 Oct 2026 | Final release targeted 10 Oct | Released 21 Oct | Crypto Briefing |
Also on the Network Desk for Bitcoin
How this works and where the data comes from
Each upgrade page is built from primary sources: client release notes, foundation announcements, governance proposals and Forkcast data for Ethereum. Every curated fact carries its source and the date we checked it. Live data refreshes automatically: exchange flags every 15 minutes, chain heights and governance every 15 minutes, client releases hourly, readiness data every 6 hours.
Countdowns: fixed-time forks use the announced timestamp; Ethereum slots are exact (12 s per slot); height-based forks (Cosmos) are estimated from the average block time of the last 2,000 blocks and will drift. When a target changes we record it as a date slip.
Exchange pauses: we read Binance (deposit/withdraw flags per network), KuCoin (per chain), Kraken (asset funding status) and Coinbase (status page component per network). A pause is any period where deposits or withdrawals are off. Reopen time is measured from the activation time to the first check where both are back on.
Sources: Bitcoin Core releases (checked 12 Nov 2026); Bitnodes (checked 12 Nov 2026)
Information only, not financial advice. Data comes from public sources and can be delayed or wrong; check the primary source before acting.