Sealminer A4 Ultra Hydro
Bitcoin & Bitcoin Cash ASIC Miner
886TH
HASHRATE
9.45W/TH
EFFICIENCY
8373W
POWER
£903.43
EST. MONTHLY
NO PAYBACK
EST. ROI
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.
Bitcoin Core 28.1 release in simple English
Bitcoin Core 28.1 release: A manually configured HiddenServicePort may still point at the old localhost target. Compare torrc, Bitcoin configuration and the actual listening socket before accepting traffic.
Simple example
A node operator is checking Bitcoin Core 28.1 release. This allows multiple local nodes to avoid the 28.0 collision. Monitor normal peer discovery and persistence after restart.
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 the main point of Bitcoin Core 28.1 release?
Bitcoin Core 28.1 release: A manually configured HiddenServicePort may still point at the old localhost target.
For Bitcoin Core 28.1 release, what should a beginner know about derived onion port?
With a custom port and no explicit onion bind, the listener becomes port plus one.
For Bitcoin Core 28.1 release, what should a beginner know about tor configuration?
A manually configured HiddenServicePort may still point at the old localhost target.
For Bitcoin Core 28.1 release, what should a beginner know about explicit compatibility?
Operators needing the previous listener can set a bind such as localhost port 8334 with the onion permission.
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.
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.