Bitcoin Core 30.0 operator guide covering wallet migration, relay policy, lower fee defaults, indexes, IPC mining, networking and safe deployment.
This guide explains Bitcoin Core 30.0 release in plain English. It summarises the important changes, who they affect and what should be checked before an upgrade.
Bitcoin Core 30.0 release: Bitcoin Core 27.x and earlier reached end of support when 30.0 shipped. Inventory every node and document any deliberate older branch before changing production.
A node operator is checking Bitcoin Core 30.0 release. An experimental IPC Mining Interface can be exposed with bitcoin -m node and an ipcbind Unix socket when built with the optional dependency.
Bitcoin Core 27.x and earlier reached end of support when 30.0 shipped. Inventory every node and document any deliberate older branch before changing production.
Berkeley DB legacy wallets can no longer be loaded or created. Use migratewallet with tested backups, verify descriptors and balances, and keep the original wallet files offline until recovery is proven.
The default datacarriersize is effectively uncapped at 100,000 bytes and multiple OP_RETURN outputs may be standard. Standard legacy sigops are capped at 2,500, while improved one-parent-one-child relay accepts broader package topologies.
blockmintxfee is 0.001 sat/vB and default minimum relay and incremental relay fees are 0.1 sat/vB. Wallet and dust settings remain distinct, and acceptance by one node never guarantees network propagation.
coinstatsindex must resynchronise from scratch in a new indexes path, while the old index remains on disk. Logging gains per-location rate limiting, so monitoring must detect suppression as well as errors.
The bitcoin wrapper command is new. An experimental IPC Mining Interface can be exposed with bitcoin -m node and an ipcbind Unix socket when built with the optional dependency; isolate it and treat its interface as experimental.
NAT-PMP is enabled by default, UPnP support is removed and per-network proxy syntax is available. Paytxfee and settxfee are deprecated for removal in 31, so replace dependent automation now.
Node operators test the release on a representative non-production system. They check startup, normal operation, failure handling and restart before changing a live node. Connected wallets, monitoring and mining services should also be checked.
Bitcoin Core 30.0 release: Bitcoin Core 27.x and earlier reached end of support when 30.0 shipped.
Bitcoin Core 27.x and earlier reached end of support when 30.0 shipped.
Berkeley DB legacy wallets can no longer be loaded or created. Use migratewallet with tested backups, verify descriptors and balances, and keep the original wallet files offline until recovery is proven.
The default datacarriersize is effectively uncapped at 100,000 bytes and multiple OP_RETURN outputs may be standard.
Bitcoin Core 30.0 combines wallet, policy, networking and operator-interface changes. A safe migration treats each as a separate testable boundary and does not promote the fleet until the canary has rebuilt, reconciled and served real workloads correctly.
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Bitcoin Core 31.1 guide covering the private-broadcast IP leak fix, proxy reconnections, chainstate compaction, BDB migration and settings-write safety.
Bitcoin Core 30.3 guide covering excessive chainstate I/O, regular compaction, wallet bump and coin-selection fixes, PSBT, MuSig2 and build maintenance.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.