Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£857.29
EST. MONTHLY
206
DAYS
EST. ROI
This guide explains Bitcoin Core 0.14.1 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.14.1 was released on 22 April 2017 with bug fixes, performance changes and operationally important compatibility updates. Named RPC arguments changed, getblocktemplate gained safe support for non-SegWit clients after activation, and UTXO cache accounting was corrected so configured memory better reflected peak use.
- Why it matters: Bitcoin Core 0.14.1 was a patch release with material RPC, mining and memory-accounting effects. Safe rollout required schema-level integration tests, measured cache headroom and explicit template-client compatibility.
- Current position: Bitcoin Core 0.14.1 was released on 22 April 2017 with bug fixes, performance changes and operationally important compatibility updates.
Bitcoin Core 0.14.1 in simple English
Bitcoin Core 0.14.1: The release fixed a shutdown hang involving at least eight addnode entries and handled node-identifier wrapping. Operators with static peers needed stop-time and reconnect tests.
Simple example
A node operator is checking Bitcoin Core 0.14.1. Positional callers were unaffected in the same way, but named-argument clients built for 0.14.0 could break.
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.
- Mempool:
- A node’s changing local collection of valid, unconfirmed transactions.
- UTXO:
- An unspent transaction output: a piece of bitcoin that can be used as an input to a later transaction.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Named RPC compatibility
The first createrawtransaction argument was renamed from transactions to inputs, and disconnectnode renamed node to address. Positional callers were unaffected in the same way, but named-argument clients built for 0.14.0 could break. Contract tests must exercise actual JSON names and error responses.
SegWit mining templates
Earlier getblocktemplate behaviour required downstream SegWit support after activation. 0.14.1 could serve non-SegWit clients by excluding witness transactions, allowing them to continue safely while still recommending signalling. Pools needed to distinguish rule enforcement capability from transaction inclusion capability.
UTXO memory accounting
Prior releases were estimated to account for only about half peak cache memory during flushes. Corrected accounting respected dbcache more accurately, while the default increased. A numerically identical setting could therefore yield different cache performance and lower real peak risk.
Low-memory operation
Hosts near one gigabyte needed an explicit lower dbcache and total-process headroom. Mempool, peers, wallets, indexes, page cache and supervisor limits remained outside a simplistic database budget. Test initial sync, flush and shutdown, not just steady-state RSS.
Mining and fee effects
Changes also fixed ancestor-fee updates for prioritisetransaction and submitblock error handling. Template systems should compare package selection, witness exclusion, block weight, fees and rejection output across primary and failover nodes.
Shutdown and networking fixes
The release fixed a shutdown hang involving at least eight addnode entries and handled node-identifier wrapping. Operators with static peers needed stop-time and reconnect tests. A patch upgrade could change lifecycle reliability as materially as RPC results.
Upgrade and rollback
Verify artefacts, stop cleanly, back up wallets and freeze RPC schemas, dbcache and mining-client capabilities. Test both named and positional paths and non-SegWit fallback. Rollback must reconcile wallet and mempool actions performed while integrations saw the new responses.
Frequently asked questions
What is the main point of Bitcoin Core 0.14.1?
Bitcoin Core 0.14.1: The release fixed a shutdown hang involving at least eight addnode entries and handled node-identifier wrapping.
For Bitcoin Core 0.14.1, what should a beginner know about named RPC compatibility?
The first createrawtransaction argument was renamed from transactions to inputs, and disconnectnode renamed node to address.
For Bitcoin Core 0.14.1, what should a beginner know about segwit mining templates?
Earlier getblocktemplate behaviour required downstream SegWit support after activation. 0.14.1 could serve non-SegWit clients by excluding witness transactions, allowing them to continue safely while still recommending signalling.
For Bitcoin Core 0.14.1, what should a beginner know about utxo memory accounting?
Prior releases were estimated to account for only about half peak cache memory during flushes.
Conclusion
Bitcoin Core 0.14.1 was a patch release with material RPC, mining and memory-accounting effects. Safe rollout required schema-level integration tests, measured cache headroom and explicit template-client compatibility.
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.