aboutsummaryrefslogtreecommitdiff
path: root/doc/release-notes.md
diff options
context:
space:
mode:
authort-bast <bastuc@hotmail.fr>2021-03-10 15:37:18 +0100
committert-bast <bastuc@hotmail.fr>2021-04-30 18:53:47 +0200
commit11d6459b6e101f05f36e13799c400bef82d2fc21 (patch)
treee467b32e008eca8e9978766ab1d783059de3f35f /doc/release-notes.md
parent480bf01c295527bd212964efe4df3bb886db5654 (diff)
downloadbitcoin-11d6459b6e101f05f36e13799c400bef82d2fc21.tar.xz
rpc: include_unsafe option for fundrawtransaction
Allow RPC users to opt-in to unsafe inputs when funding a raw transaction. Applications that need to manage a complex RBF flow (such as lightning nodes using anchor outputs) are very limited if they can only use safe inputs. Fixes #21299
Diffstat (limited to 'doc/release-notes.md')
-rw-r--r--doc/release-notes.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 874b919f08..5c70bc91db 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -152,6 +152,11 @@ Wallet
- The `bumpfee` RPC is not available with wallets that have private keys
disabled. `psbtbumpfee` can be used instead. (#20891)
+- The `fundrawtransaction`, `send` and `walletcreatefundedpsbt` RPCs now support an `include_unsafe` option
+ that when `true` allows using unsafe inputs to fund the transaction.
+ Note that the resulting transaction may become invalid if one of the unsafe inputs disappears.
+ If that happens, the transaction must be funded with different inputs and republished. (#21359)
+
GUI changes
-----------