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 28.1 Release: Tor and Key-Safety Maintenance Guide
Bitcoin Core 28.1 guide covering derived onion ports, multi-node compatibility, Tor configuration, extended-key memory clearing, builds and staged rollout.
This guide explains Bitcoin Core 28.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 28.1 corrected an important multi-node networking regression from 28.0 and tightened handling of decoded extended-key secrets. When a custom P2P port is set without an explicit bind, the default onion listener now uses that port plus one instead of fixed mainnet port 8334.
- Why it matters: Bitcoin Core 28.1 is especially relevant to multi-node and Tor operators. A successful upgrade proves the actual listening sockets and hidden-service mapping, while continuing to minimise exposure of all extended-key material.
- 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 a mempool as one node’s waiting room for valid transactions that have not yet entered a block. Different nodes can have different waiting rooms, and the contents can change from one second to the next.
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.
Derived onion port
With a custom port and no explicit onion bind, the listener becomes port plus one. This allows multiple local nodes to avoid the 28.0 collision.
Tor configuration
A manually configured HiddenServicePort may still point at the old localhost target. Compare torrc, Bitcoin configuration and the actual listening socket before accepting traffic.
Explicit compatibility
Operators needing the previous listener can set a bind such as localhost port 8334 with the onion permission. Avoid relying on implicit defaults.
Secret clearing
DecodeExtKey now clears secret data. This is defence in depth, not permission to expose extended private keys to logs, shell history or long-lived processes.
Address manager
Internal address-manager identifiers moved to a 64-bit counter. Monitor normal peer discovery and persistence after restart.
Build fixes
Windows cross-compilation and NetBSD flags received maintenance fixes. Custom builders must rerun toolchain and reproducibility checks.
Upgrade procedure
Record ports and sockets, verify artifacts, stop cleanly, upgrade one node, test clearnet and Tor reachability, inspect logs and retain the prior binary and configuration. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.
Frequently asked questions
What is Bitcoin Core 28.1 Release?
Bitcoin Core 28.1 corrected an important multi-node networking regression from 28.0 and tightened handling of decoded extended-key secrets. When a custom P2P port is set without an explicit bind, the default onion listener now uses that port plus one instead of fixed mainnet port 8334.
Is Bitcoin Core 28.1 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 28.1 Release matter?
Bitcoin Core 28.1 is especially relevant to multi-node and Tor operators. A successful upgrade proves the actual listening sockets and hidden-service mapping, while continuing to minimise exposure of all extended-key material.
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 28.1 is especially relevant to multi-node and Tor operators. A successful upgrade proves the actual listening sockets and hidden-service mapping, while continuing to minimise exposure of all extended-key material.
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.