1Bitcoin Core version *0.14.3* is now available from:
2
3  <https://bitcoin.org/bin/bitcoin-core-0.14.3/>
4
5This is a new minor version release, including various bugfixes and
6performance improvements.
7
8Please report bugs using the issue tracker at github:
9
10  <https://github.com/bitcoin/bitcoin/issues>
11
12To receive security and update notifications, please subscribe to:
13
14  <https://bitcoincore.org/en/list/announcements/join/>
15
16Compatibility
17==============
18
19Bitcoin Core is extensively tested on multiple operating systems using
20the Linux kernel, macOS 10.8+, and Windows Vista and later.
21
22Microsoft ended support for Windows XP on [April 8th, 2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support),
23No attempt is made to prevent installing or running the software on Windows XP, you
24can still do so at your own risk but be aware that there are known instabilities and issues.
25Please do not report issues about Windows XP to the issue tracker.
26
27Bitcoin Core should also work on most other Unix-like systems but is not
28frequently tested on them.
29
30Notable changes
31===============
32
33Denial-of-Service vulnerability CVE-2018-17144
34 -------------------------------
35
36A denial-of-service vulnerability exploitable by miners has been discovered in
37Bitcoin Core versions 0.14.0 up to 0.16.2. It is recommended to upgrade any of
38the vulnerable versions to 0.14.3, 0.15.2 or 0.16.3 as soon as possible.
39
40Known Bugs
41==========
42
43Since 0.14.0 the approximate transaction fee shown in Bitcoin-Qt when using coin
44control and smart fee estimation does not reflect any change in target from the
45smart fee slider. It will only present an approximate fee calculated using the
46default target. The fee calculated using the correct target is still applied to
47the transaction and shown in the final send confirmation dialog.
48
490.14.3 Change log
50=================
51
52Detailed release notes follow. This overview includes changes that affect
53behavior, not code moves, refactors and string updates. For convenience in locating
54the code changes and accompanying discussion, both the pull request and
55git merge commit are mentioned.
56
57### Consensus
58- #14247 `52965fb` Fix crash bug with duplicate inputs within a transaction (TheBlueMatt, sdaftuar)
59
60### RPC and other APIs
61
62- #10445 `87a21d5` Fix: make CCoinsViewDbCursor::Seek work for missing keys (Pieter Wuille, Gregory Maxwell)
63- #9853 Return correct error codes in setban(), fundrawtransaction(), removeprunedfunds(), bumpfee(), blockchain.cpp (John Newbery)
64
65
66### P2P protocol and network code
67
68- #10234 `d289b56` [net] listbanned RPC and QT should show correct banned subnets (John Newbery)
69
70### Build system
71
72
73### Miscellaneous
74
75- #10451 `3612219` contrib/init/bitcoind.openrcconf: Don't disable wallet by default (Luke Dashjr)
76- #10250 `e23cef0` Fix some empty vector references (Pieter Wuille)
77- #10196 `d28d583` PrioritiseTransaction updates the mempool tx counter (Suhas Daftuar)
78- #9497 `e207342` Fix CCheckQueue IsIdle (potential) race condition and remove dangerous constructors. (Jeremy Rubin)
79
80### GUI
81
82- #9481 `7abe7bb` Give fallback fee a reasonable indent (Luke Dashjr)
83- #9481 `3e4d7bf` Qt/Send: Figure a decent warning colour from theme (Luke Dashjr)
84- #9481 `e207342` Show more significant warning if we fall back to the default fee (Jonas Schnelli)
85
86### Wallet
87
88- #10308 `28b8b8b` Securely erase potentially sensitive keys/values (tjps)
89- #10265 `ff13f59` Make sure pindex is non-null before possibly referencing in LogPrintf call. (Karl-Johan Alm)
90
91Credits
92=======
93
94Thanks to everyone who directly contributed to this release:
95
96- Cory Fields
97- CryptAxe
98- fanquake
99- Jeremy Rubin
100- John Newbery
101- Jonas Schnelli
102- Gregory Maxwell
103- Karl-Johan Alm
104- Luke Dashjr
105- MarcoFalke
106- Matt Corallo
107- Mikerah
108- Pieter Wuille
109- practicalswift
110- Suhas Daftuar
111- Thomas Snider
112- Tjps
113- Wladimir J. van der Laan
114
115And to those that reported security issues:
116
117- awemany (for CVE-2018-17144, previously credited as "anonymous reporter")
118
119