Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£857.24
EST. MONTHLY
206
DAYS
EST. ROI
This guide explains Bitcoin Core 0.16.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 0.16.3 was released on 18 September 2018 with an urgent recommendation for operators running versions 0.14.0 through 0.16.2. Its release notes described a miner-exploitable denial-of-service issue and fixed a crash triggered by duplicate inputs within a transaction.
- Why it matters: Bitcoin Core 0.16.3 was an urgent consensus-security maintenance release. Safe response required rapid authenticated rollout, complete fleet inventory and proof that no vulnerable node or image could silently return.
- 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 0.16.3 release in simple English
Bitcoin Core 0.16.3 release: The consensus change log fixed a crash involving duplicate inputs inside one transaction. The later notice described the inflation impact discovered during review.
Simple example
A node operator is checking Bitcoin Core 0.16.3 release. Drain dependent services, stop each node cleanly and upgrade canaries before the fleet. Confirm 0.16.3 version, peers, tip hash, chainwork, mempool and wallet status before moving to the next host.
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.
- 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.
Affected fleet
Identify every production, standby, mining, wallet and analytics node and its exact binary provenance. Versions 0.14.0 through 0.16.2 were named vulnerable in the release notes. Include forgotten test and failover nodes because they can re-enter service during an incident.
Duplicate-input defect
The consensus change log fixed a crash involving duplicate inputs inside one transaction. The later notice described the inflation impact discovered during review. Do not reproduce a live exploit. Use official fixtures or isolated regtest coverage and treat the issue as both availability and consensus-security critical.
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.
Rolling upgrade
Drain dependent services, stop each node cleanly and upgrade canaries before the fleet. Keep enough independent verified nodes online for chain and payment monitoring. Confirm 0.16.3 version, peers, tip hash, chainwork, mempool and wallet status before moving to the next host.
Related RPC correction
The release also made signrawtransaction variants error when an amount was required but missing. Transaction signers must supply authenticated previous-output amounts and handle new errors explicitly. Retest offline and multisignature workflows rather than bypassing the stricter result.
Incident evidence
Preserve relevant logs, peer and block context and old binary identity without retaining private wallet data. Alert on crashes, unexpected restarts, divergent tips and suspicious invalid transactions. Escalate through the organisation’s security process if compromise or chain divergence is suspected.
Post-upgrade proof
Verify all fleet versions, block processing, reorganisation handling, mining templates, transaction validation and restart. Confirm no vulnerable instance remains in load balancers, snapshots or autoscaling images and document the emergency rollback boundary without returning to a vulnerable binary. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is the main point of Bitcoin Core 0.16.3 release?
Bitcoin Core 0.16.3 release: The consensus change log fixed a crash involving duplicate inputs inside one transaction.
For Bitcoin Core 0.16.3 release, what should a beginner know about affected fleet?
Identify every production, standby, mining, wallet and analytics node and its exact binary provenance.
For Bitcoin Core 0.16.3 release, what should a beginner know about duplicate-input defect?
The consensus change log fixed a crash involving duplicate inputs inside one transaction.
For Bitcoin Core 0.16.3 release, what should a beginner know about rolling upgrade?
Drain dependent services, stop each node cleanly and upgrade canaries before the fleet.
Conclusion
Bitcoin Core 0.16.3 was an urgent consensus-security maintenance release. Safe response required rapid authenticated rollout, complete fleet inventory and proof that no vulnerable node or image could silently return.
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.