Skip to content

Commit f3d7d75

Browse files
committed
Release notes: integrate detached release notes
1 parent 97fbe67 commit f3d7d75

File tree

5 files changed

+33
-60
lines changed

5 files changed

+33
-60
lines changed

doc/release-notes-14060.md

Lines changed: 0 additions & 21 deletions
This file was deleted.

doc/release-notes-14477.md

Lines changed: 0 additions & 5 deletions
This file was deleted.

doc/release-notes-14565.md

Lines changed: 0 additions & 5 deletions
This file was deleted.

doc/release-notes-pr13381.md

Lines changed: 0 additions & 29 deletions
This file was deleted.

doc/release-notes.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,13 @@ Configuration option changes
8282
configuration file. Recognized sections are `[test]`, `[main]`, and
8383
`[regtest]`.
8484

85+
- Four new options are available for configuring the maximum number of
86+
messages that ZMQ will queue in memory (the "high water mark") before
87+
dropping additional messages. The default value is 1,000, the same as
88+
was used for previous releases. See the [ZMQ
89+
documentation](https://github.com/bitcoin/bitcoin/blob/master/doc/zmq.md#usage)
90+
for details.
91+
8592
- The `enablebip61` option (introduced in Bitcoin Core 0.17.0) is
8693
used to toggle sending of BIP 61 reject messages. Reject messages have no use
8794
case on the P2P network and are only logged for debugging by most network
@@ -211,6 +218,32 @@ in the Low-level Changes section below.
211218
P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept
212219
an additional `witnessscript` parameter.
213220

221+
- The `importmulti` RPC now returns an additional `warnings` field for
222+
each request with an array of strings explaining when fields are being
223+
ignored or are inconsistent, if there are any.
224+
225+
- The `getaddressinfo` RPC now returns an additional `solvable` boolean
226+
field when Bitcoin Core knows enough about the address's scriptPubKey,
227+
optional redeemScript, and optional witnessScript in order for the
228+
wallet to be able to generate an unsigned input spending funds sent to
229+
that address.
230+
231+
- The `getaddressinfo`, `listunspent`, and `scantxoutset` RPCs now
232+
return an additional `desc` field that contains an output descriptor
233+
containing all key paths and signing information for the address
234+
(except for the private key). The `desc` field is only returned for
235+
`getaddressinfo` and `listunspent` when the address is solvable.
236+
237+
- The `importprivkey` RPC will preserve previously-set labels for
238+
addresses or public keys corresponding to the private key being
239+
imported. For example, if you imported a watch-only address with the
240+
label "cold wallet" in earlier releases of Bitcoin Core, subsequently
241+
importing the private key would default to resetting the address's
242+
label to the default empty-string label (""). In this release, the
243+
previous label of "cold wallet" will be retained. If you optionally
244+
specify any label besides the default when calling `importprivkey`,
245+
the new label will be applied to the address.
246+
214247
- See the [Mining](#mining) section for changes to `getblocktemplate`.
215248

216249
Graphical User Interface (GUI)

0 commit comments

Comments
 (0)