aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@protonmail.com>2020-07-13 18:27:22 +0200
committerWladimir J. van der Laan <laanwj@protonmail.com>2020-07-13 18:33:00 +0200
commit37485baa275147470aa605e30654a8e42b3f9532 (patch)
tree2b9174c079cd3093589a07b2e875a556ac966da1
parentd52bfc49161721fd55b9312549b3da674da387fe (diff)
parentfa740d4cea92727601d5d9b474e07f7a89afc2db (diff)
Merge #19483: doc: Merge release notes
fa740d4cea92727601d5d9b474e07f7a89afc2db doc: move-only release notes (MarcoFalke) faa3d2eee1cc52b76f6eda8271691fdbff1baaa7 doc: Remove release notes of backports (MarcoFalke) Pull request description: ACKs for top commit: laanwj: ACK fa740d4cea92727601d5d9b474e07f7a89afc2db Tree-SHA512: 86e7077f9050c65b0b33829892aafabbb783a603a1a77932893659bc1071fb2d2a0515662e7e9e6fdfffb59f86bfc41ad74ba6e86d618bf71a6616d9f7a18fa2
-rw-r--r--doc/release-notes-11413.md11
-rw-r--r--doc/release-notes-16377.md9
-rw-r--r--doc/release-notes-16528.md0
-rw-r--r--doc/release-notes-18202.md8
-rw-r--r--doc/release-notes-18594.md5
-rw-r--r--doc/release-notes-18918.md0
-rw-r--r--doc/release-notes-19133.md7
-rw-r--r--doc/release-notes-19200.md7
-rw-r--r--doc/release-notes-19219.md23
-rw-r--r--doc/release-notes-19469.md6
-rw-r--r--doc/release-notes.md49
11 files changed, 49 insertions, 76 deletions
diff --git a/doc/release-notes-11413.md b/doc/release-notes-11413.md
deleted file mode 100644
index 32735e37f6..0000000000
--- a/doc/release-notes-11413.md
+++ /dev/null
@@ -1,11 +0,0 @@
-Updated or changed RPC
-----------------------
-
-The `bumpfee`, `fundrawtransaction`, `sendmany`, `sendtoaddress`, and `walletcreatefundedpsbt`
-RPC commands have been updated to include two new fee estimation methods "BTC/kB" and "sat/B".
-The target is the fee expressed explicitly in the given form. Note that use of this feature
-will trigger BIP 125 (replace-by-fee) opt-in.
-
-In addition, the `estimate_mode` parameter is now case insensitive for all of the above RPC commands.
-
-The `bumpfee` command now uses `conf_target` rather than `confTarget` in the options.
diff --git a/doc/release-notes-16377.md b/doc/release-notes-16377.md
deleted file mode 100644
index 3442fa451b..0000000000
--- a/doc/release-notes-16377.md
+++ /dev/null
@@ -1,9 +0,0 @@
-RPC changes
------------
-- The `walletcreatefundedpsbt` RPC call will now fail with
- `Insufficient funds` when inputs are manually selected but are not enough to cover
- the outputs and fee. Additional inputs can automatically be added through the
- new `add_inputs` option.
-
-- The `fundrawtransaction` RPC now supports `add_inputs` option that when `false`
- prevents adding more inputs if necessary and consequently the RPC fails.
diff --git a/doc/release-notes-16528.md b/doc/release-notes-16528.md
deleted file mode 100644
index e69de29bb2..0000000000
--- a/doc/release-notes-16528.md
+++ /dev/null
diff --git a/doc/release-notes-18202.md b/doc/release-notes-18202.md
deleted file mode 100644
index f2bd870ac4..0000000000
--- a/doc/release-notes-18202.md
+++ /dev/null
@@ -1,8 +0,0 @@
-Low-level RPC Changes
----------------------
-
-- To make RPC `sendtoaddress` more consistent with `sendmany` the following error
- `sendtoaddress` codes were changed from `-4` to `-6`:
- - Insufficient funds
- - Fee estimation failed
- - Transaction has too long of a mempool chain
diff --git a/doc/release-notes-18594.md b/doc/release-notes-18594.md
deleted file mode 100644
index 6a2ef0a67c..0000000000
--- a/doc/release-notes-18594.md
+++ /dev/null
@@ -1,5 +0,0 @@
-## CLI
-
-The `bitcoin-cli -getinfo` command now displays the wallet name and balance for
-each of the loaded wallets when more than one is loaded (e.g. in multiwallet
-mode) and a wallet is not specified with `-rpcwallet`. (#18594)
diff --git a/doc/release-notes-18918.md b/doc/release-notes-18918.md
deleted file mode 100644
index e69de29bb2..0000000000
--- a/doc/release-notes-18918.md
+++ /dev/null
diff --git a/doc/release-notes-19133.md b/doc/release-notes-19133.md
deleted file mode 100644
index 5150fbe1c7..0000000000
--- a/doc/release-notes-19133.md
+++ /dev/null
@@ -1,7 +0,0 @@
-## CLI
-
-A new `bitcoin-cli -generate` command, equivalent to RPC `generatenewaddress`
-followed by `generatetoaddress`, can generate blocks for command line testing
-purposes. This is a client-side version of the
-[former](https://github.com/bitcoin/bitcoin/issues/14299) `generate` RPC. See
-the help for details. (#19133)
diff --git a/doc/release-notes-19200.md b/doc/release-notes-19200.md
deleted file mode 100644
index 4670cb2e75..0000000000
--- a/doc/release-notes-19200.md
+++ /dev/null
@@ -1,7 +0,0 @@
-## Wallet
-
-- Backwards compatibility has been dropped for two `getaddressinfo` RPC
- deprecations, as notified in the 0.20 release notes. The deprecated `label`
- field has been removed as well as the deprecated `labels` behavior of
- returning a JSON object containing `name` and `purpose` key-value pairs. Since
- 0.20, the `labels` field returns a JSON array of label names. (#19200)
diff --git a/doc/release-notes-19219.md b/doc/release-notes-19219.md
deleted file mode 100644
index b5ee885ddc..0000000000
--- a/doc/release-notes-19219.md
+++ /dev/null
@@ -1,23 +0,0 @@
-#### Changes regarding misbehaving peers
-
-Peers that misbehave (e.g. send us invalid blocks) are now referred to as
-discouraged nodes in log output, as they're not (and weren't) strictly banned:
-incoming connections are still allowed from them, but they're preferred for
-eviction.
-
-Furthermore, a few additional changes are introduced to how discouraged
-addresses are treated:
-
-- Discouraging an address does not time out automatically after 24 hours
- (or the `-bantime` setting). Depending on traffic from other peers,
- discouragement may time out at an indeterminate time.
-
-- Discouragement is not persisted over restarts.
-
-- There is no method to list discouraged addresses. They are not returned by
- the `listbanned` RPC. That RPC also no longer reports the `ban_reason`
- field, as `"manually added"` is the only remaining option.
-
-- Discouragement cannot be removed with the `setban remove` RPC command.
- If you need to remove a discouragement, you can remove all discouragements by
- stop-starting your node.
diff --git a/doc/release-notes-19469.md b/doc/release-notes-19469.md
deleted file mode 100644
index 974b228cc1..0000000000
--- a/doc/release-notes-19469.md
+++ /dev/null
@@ -1,6 +0,0 @@
-Updated RPCs
-------------
-
-- `getpeerinfo` no longer returns the `banscore` field unless the configuration
- option `-deprecatedrpc=banscore` is used. The `banscore` field will be fully
- removed in the next major release. (#19469)
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 4d2225884e..2966f9083c 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -87,6 +87,28 @@ Updated RPCs
whether initial broadcast of the transaction has been acknowledged by a
peer. `getmempoolancestors` and `getmempooldescendants` are also updated.
+- The `bumpfee`, `fundrawtransaction`, `sendmany`, `sendtoaddress`, and `walletcreatefundedpsbt`
+RPC commands have been updated to include two new fee estimation methods "BTC/kB" and "sat/B".
+The target is the fee expressed explicitly in the given form. Note that use of this feature
+will trigger BIP 125 (replace-by-fee) opt-in. (#11413)
+
+- In addition, the `estimate_mode` parameter is now case insensitive for all of
+ the above RPC commands. (#11413)
+
+- The `bumpfee` command now uses `conf_target` rather than `confTarget` in the
+ options. (#11413)
+
+- `getpeerinfo` no longer returns the `banscore` field unless the configuration
+ option `-deprecatedrpc=banscore` is used. The `banscore` field will be fully
+ removed in the next major release. (#19469)
+
+- The `walletcreatefundedpsbt` RPC call will now fail with
+ `Insufficient funds` when inputs are manually selected but are not enough to cover
+ the outputs and fee. Additional inputs can automatically be added through the
+ new `add_inputs` option. (#16377)
+
+- The `fundrawtransaction` RPC now supports `add_inputs` option that when `false`
+ prevents adding more inputs if necessary and consequently the RPC fails.
Changes to Wallet or GUI related RPCs can be found in the GUI or Wallet section below.
@@ -109,12 +131,30 @@ Updated settings
Changes to Wallet or GUI related settings can be found in the GUI or Wallet section below.
+Tools and Utilities
+-------------------
+
+- A new `bitcoin-cli -generate` command, equivalent to RPC `generatenewaddress`
+ followed by `generatetoaddress`, can generate blocks for command line testing
+ purposes. This is a client-side version of the
+ former `generate` RPC. See the help for details. (#19133)
+
+- The `bitcoin-cli -getinfo` command now displays the wallet name and balance for
+ each of the loaded wallets when more than one is loaded (e.g. in multiwallet
+ mode) and a wallet is not specified with `-rpcwallet`. (#18594)
+
New settings
------------
Wallet
------
+- Backwards compatibility has been dropped for two `getaddressinfo` RPC
+ deprecations, as notified in the 0.20 release notes. The deprecated `label`
+ field has been removed as well as the deprecated `labels` behavior of
+ returning a JSON object containing `name` and `purpose` key-value pairs. Since
+ 0.20, the `labels` field returns a JSON array of label names. (#19200)
+
- To improve wallet privacy, the frequency of wallet rebroadcast attempts is
reduced from approximately once every 15 minutes to once every 12-36 hours.
To maintain a similar level of guarantee for initial broadcast of wallet
@@ -261,6 +301,15 @@ GUI changes
Low-level changes
=================
+RPC
+---
+
+- To make RPC `sendtoaddress` more consistent with `sendmany` the following error
+ `sendtoaddress` codes were changed from `-4` to `-6`:
+ - Insufficient funds
+ - Fee estimation failed
+ - Transaction has too long of a mempool chain
+
Tests
-----