aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2017-06-15 12:43:36 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2017-06-15 12:44:01 +0200
commitfc61c8322bd7288f7546d18ad04c36c345be13cd (patch)
treefb6f1a7023eeb36d324c156adca8b80cfcf0d050
parent7a643511b474d53f952d3cd403af51aabd104044 (diff)
parent60b967ec41edc93f7f2d7cc115c169348be28b69 (diff)
Merge #10588: doc: Note preexisting bug in display of fee calculation in coin controlv0.14.2
60b967e Note preexisting bug in display of fee calculation in coin control (Alex Morcos) Tree-SHA512: 0179654d313ea10b776781617cea744757344d8b4455153540f116978a72aabdc0a3092388b9cfbe8d0348b699943a9e41082ed964e161e4f3017dcd056e77fc
-rw-r--r--doc/release-notes.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index defec1696d..0ad554b773 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -45,6 +45,15 @@ setting or through the `-upnp` option, as since the last UPnP vulnerability
If you use this option, it is recommended to upgrade to this version as soon as
possible.
+Known Bugs
+==========
+
+Since 0.14.0 the approximate transaction fee shown in Bitcoin-Qt when using coin
+control and smart fee estimation does not reflect any change in target from the
+smart fee slider. It will only present an approximate fee calculated using the
+default target. The fee calculated using the correct target is still applied to
+the transaction and shown in the final send confirmation dialog.
+
0.14.2 Change log
=================