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.3 Release: Relay and Reorganisation Guide
Bitcoin Core 28.3 guide covering lower relay fees, TRUC reorganisation handling, onion whitelist permissions, build fixes and controlled deployment.
This guide explains Bitcoin Core 28.3 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.3 brings selected maintenance and policy fixes to the 28.x branch. Default block, minimum relay and incremental relay fee floors are lower, TRUC policy is handled correctly during reorganisations and inbound onion whitelist permissions are restored.
- Why it matters: Bitcoin Core 28.3 is a maintenance release with visible relay and network effects. Operators should verify effective policy locally, test behaviour across real peers and keep the older branch artefact available until the rollout is proven.
- 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.
- Mempool:
- A node’s changing local collection of valid, unconfirmed transactions.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Fee defaults
The default block minimum is 1 satoshi per kvB, while minimum relay and incremental relay defaults are 100 satoshis per kvB. Express units explicitly and inspect effective configuration after restart.
Wallet boundary
Wallet fee selection and dust policy are separate controls. Do not infer spendability, economical confirmation or dust acceptance solely from the lower node defaults.
Propagation
A transaction accepted locally at a low feerate may not travel across peers running different policy. Measure peer propagation and confirmation outcomes before offering a service guarantee.
Reorganisation handling
TRUC policy checks are not applied while transactions are restored during a reorganisation. Test mempool transitions and downstream alerts with controlled reorg scenarios.
Onion permissions
Inbound onion connections regain configured whitelist permissions. Audit whitelist scope and confirm that permissions are neither missing nor broader than intended.
Maintenance scope
Build, test and documentation fixes improve branch reliability without importing the complete Core 29 or 30 feature set. Maintain an explicit branch-compatibility matrix.
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 28.3 Release?
Bitcoin Core 28.3 brings selected maintenance and policy fixes to the 28.x branch. Default block, minimum relay and incremental relay fee floors are lower, TRUC policy is handled correctly during reorganisations and inbound onion whitelist permissions are restored.
Is Bitcoin Core 28.3 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.3 Release matter?
Bitcoin Core 28.3 is a maintenance release with visible relay and network effects. Operators should verify effective policy locally, test behaviour across real peers and keep the older branch artefact available until the rollout is proven.
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.3 is a maintenance release with visible relay and network effects. Operators should verify effective policy locally, test behaviour across real peers and keep the older branch artefact available until the rollout is proven.
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.