aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRussell Yanofsky <russ@yanofsky.org>2017-02-27 11:35:35 -0500
committerRussell Yanofsky <russ@yanofsky.org>2017-02-27 16:12:22 -0500
commit29bae0c6c5a03890e3498f1ee194f5bef5426091 (patch)
tree581788b338d26729a682268a1833af7edc506e33
parentf00429666c60932b233dbee4d3a0618c9c63819f (diff)
downloadbitcoin-29bae0c6c5a03890e3498f1ee194f5bef5426091.tar.xz
Mention bumpfee in 0.14 release notes.
-rw-r--r--doc/release-notes.md8
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 33f5ed1f87..9c7064d0dc 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -168,7 +168,8 @@ Opt into RBF When Sending
A new startup option, `-walletrbf`, has been added to allow users to have all
transactions sent opt into RBF support. The default value for this option is
-currently `false`, so transactions will not opt into RBF by default.
+currently `false`, so transactions will not opt into RBF by default. The new
+`bumpfee` RPC can be used to replace transactions that opt into RBF.
Sensitive Data Is No Longer Stored In Debug Console History
-----------------------------------------------------------
@@ -247,6 +248,11 @@ Low-level RPC changes
optimizations to memory management. See [Pull #8753](https://github.com/bitcoin/bitcoin/pull/8753)
for more information.
+ - A new RPC command `bumpfee` has been added which allows replacing an
+ unconfirmed wallet transaction that signaled RBF (see the `-walletrbf`
+ startup option above) with a new transaction that pays a higher fee, and
+ should be more likely to get confirmed quickly.
+
HTTP REST Changes
-----------------