Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
Bitcoin Core 23.1 Maintenance Release Guide
Bitcoin Core 23.1 guide covering P2P timestamps, createmultisig warnings, descriptor boundary crashes, GUI fixes, upgrade verification and rollback.
This guide explains Bitcoin Core 23.1 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 23.1 is a maintenance release for the 23.x branch. It corrects a focused set of P2P, RPC, descriptor, GUI, build and test issues.
- Why it matters: Core 23.1 addresses real branch-specific defects without changing Bitcoin consensus. Operators should validate the affected RPC, descriptor, networking and GUI paths while preserving a simple return to the prior known-good build.
- 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 transaction as a form passed between several authorised signers. Each person or device checks the same payment details before adding approval. Passing the form around does not make the payment safe unless every signer checks what it contains.
Key terms in plain English
- Bitcoin Core
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC
- A command that software sends to a node to request information or a local action.
- Consensus
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Node
- A computer running Bitcoin software that checks data and communicates with other peers.
Upgrade boundary
Shut down fully before replacing binaries and preserve a configuration and wallet snapshot. Confirm the process reports 23.1 and the intended network and data directory after restart.
P2P correction
Self-advertisements now always set nTime. Monitor peer connections and address-manager behaviour, but do not interpret this fix as a change to consensus or transaction validity.
RPC corrections
createmultisig no longer gives the cited incorrect warning for p2sh-segwit, RPC documentation checking was hardened and HTTP path-handler access received a data-race fix.
Descriptor boundary
deriveaddresses no longer crashes at index 2147483647. That fix does not make arbitrary ranges sensible; enforce derivation limits, validate paths and use a disposable wallet for extremes.
GUI changes
The branch moved to Qt 5.15.3, disallowed encryption of watch-only wallets and prevented certain macOS 13 notification crashes. Headless nodes should still test their own dependencies.
Compatibility
Officially tested platforms included Linux, macOS 10.15 or later and Windows 7 or later. Bespoke Unix-like and older systems need explicit support decisions.
Post-upgrade proof
Compare block height and hash, peer count, wallet inventory, RPC health and application logs. Exercise multisig and descriptor workflows and retain the old executable until the observation window closes. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is Bitcoin Core 23.1 Maintenance Release?
Bitcoin Core 23.1 is a maintenance release for the 23.x branch. It corrects a focused set of P2P, RPC, descriptor, GUI, build and test issues.
Is Bitcoin Core 23.1 Maintenance 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 23.1 Maintenance Release matter?
Core 23.1 addresses real branch-specific defects without changing Bitcoin consensus. Operators should validate the affected RPC, descriptor, networking and GUI paths while preserving a simple return to the prior known-good build.
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
Core 23.1 addresses real branch-specific defects without changing Bitcoin consensus. Operators should validate the affected RPC, descriptor, networking and GUI paths while preserving a simple return to the prior known-good build.
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.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 explained in detail: its seven consensus restrictions, 55% signalling threshold, chain-split risk and August 2026 closure.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.