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.
TL;DR
- What it is: Bitcoin Core 30.0 is a major operational release. It ends support for the 27.x series and older, removes Berkeley DB legacy-wallet loading, changes transaction-relay defaults, improves package relay, introduces an experimental IPC Mining Interface and relocates a rebuilt coinstats index.
- Why it matters: 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.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
What this means in simple English
Bitcoin Core is widely used software for running a Bitcoin node. A release can change networking, wallet tools, transaction policy or operator settings without changing every rule of Bitcoin itself.
Beginners can focus on what changed and why it matters. Node operators should also read the official release notes and test their own configuration before upgrading.
Simple example
Think of the proposal as giving each transaction a limited allowance of computer work. Simple operations use a little of that allowance and expensive operations use more. If a script uses the whole allowance, validation stops.
Key terms in plain English
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Support boundary
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.
Wallet migration
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.
Relay policy
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.
Fee defaults
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.
Indexes and observability
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.
Mining and interfaces
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.
Networking and deprecations
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.
How specialists test it
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.
Frequently asked questions
What is Bitcoin Core 30.0 Release?
Bitcoin Core 30.0 is a major operational release. It ends support for the 27.x series and older, removes Berkeley DB legacy-wallet loading, changes transaction-relay defaults, improves package relay, introduces an experimental IPC Mining Interface and relocates a rebuilt coinstats index.
Is Bitcoin Core 30.0 Release active or supported today?
Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Why does Bitcoin Core 30.0 matter?
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.
Do beginners need to use the technical details?
Only if you run a Bitcoin Core node or maintain software that connects to one. Ordinary Bitcoin users can read the summary without changing any software.
Conclusion
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.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
