Bitcoin Core version 0.14.1 is now available from:
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
To receive security and update notifications, please subscribe to:
Bitcoin Core is extensively tested on multiple operating systems using
the Linux kernel, macOS 10.8+, and Windows Vista and later.
Microsoft ended support for Windows XP on April 8th, 2014,
No attempt is made to prevent installing or running the software on Windows XP, you
can still do so at your own risk but be aware that there are known instabilities and issues.
Please do not report issues about Windows XP to the issue tracker.
Bitcoin Core should also work on most other Unix-like systems but is not
frequently tested on them.
These interface changes break compatibility with 0.14.0, when the named
arguments functionality, introduced in 0.14.0, is used. Client software
using these calls with named arguments needs to be updated.
In previous versions, getblocktemplate required segwit support from downstream
clients/miners once the feature activated on the network. In this version, it
now supports non-segwit clients even after activation, by removing all segwit
transactions from the returned block template. This allows non-segwit miners to
continue functioning correctly even after segwit has activated.
Due to the limitations in previous versions, getblocktemplate also recommended
non-segwit clients to not signal for the segwit version-bit. Since this is no
longer an issue, getblocktemplate now always recommends signalling segwit for
all miners. This is safe because ability to enforce the rule is the only
required criteria for safe activation, not actually producing segwit-enabled
UTXO memory accounting
Memory usage for the UTXO cache is being calculated more accurately, so that
the configured limit (
-dbcache) will be respected when memory usage peaks
during cache flushes. The memory accounting in prior releases is estimated to
only account for half the actual peak utilization.
-dbcache has also been changed in this release to 450MiB. Users
who currently set
-dbcache to a high value (e.g. to keep the UTXO more fully
cached in memory) should consider increasing this setting in order to achieve
the same cache performance as prior releases. Users on low-memory systems
(such as systems with 1GB or less) should consider specifying a lower value for
Additional information relating to running on low-memory systems can be found
0.14.1 Change log
Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.
RPC and other APIs
142fbb2 Rename first named arg of createrawtransaction (MarcoFalke)
f15268d Remove auth cookie on shutdown (practicalswift)
2fea10a Better error handling for submitblock (rawodb, gmaxwell)
d947afc Prioritisetransaction wasn’t always updating ancestor fee (sdaftuar)
3c79602 Rename disconnectnode argument (jnewbery)
Block and transaction handling
0b5e162 Compensate for memory peak at flush time (sipa)
fc3d7db Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
ab864d3 Clean up calculations of pcoinsTip memory usage (morcos)
P2P protocol and network code
ddc2dd1 Ensure an item exists on the rpcconsole stack before adding (achow101)
569596c Don’t require segwit in getblocktemplate for segwit signalling or mining (sdaftuar)
b5c3440 Prevent slowdown in CreateNewBlock on large mempools (sdaftuar)
Tests and QA
4d8e660 Trivial: Fix typo in help getrawtransaction RPC (keystrike)
e4c9a90 util: Work around (virtual) memory exhaustion on 32-bit w/ glibc (laanwj)
ecc5232 bitcoin-tx input verification (awemany, jnewbery)
Thanks to everyone who directly contributed to this release:
- Alex Morcos
- Andrew Chow
- Cory Fields
- Gregory Maxwell
- James Evans
- John Newbery
- Matt Corallo
- Pieter Wuille
- Suhas Daftuar
- Wladimir J. van der Laan
As well as everyone that helped translating on Transifex.