Merge bitcoin/bitcoin#27503: Bump to 25.99 and remove release note fragments

9c24826e7b58722d7b0ddb8f18f985ba6f17b106 doc: Remove 25.0 release note fragments (Andrew Chow)
088a93dce8e0f406e2c09d1df181fb8aa31532a4 build: Bump to 25.99 (Andrew Chow)

Pull request description:

  Pre-25.x branch off version bump and release note fragments removal.

  The 25.0 draft release notes are in the dev wiki: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/25.0-Release-Notes-Draft

ACKs for top commit:
  fanquake:
    ACK 9c24826e7b58722d7b0ddb8f18f985ba6f17b106

Tree-SHA512: f7c7b04aa904e946bc672b5b07082a819b9d76ebccda0838bc27d0e6179cfb88b8f110500d5ea815f711580916bcfa0275774ec50a7298a4c66e645647111125

24 files changed, 1 insertions, 174 deletions

diff --git a/configure.ac b/configure.ac
index 5803876a1b..b5116922f9 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1,5 +1,5 @@
 AC_PREREQ([2.69])
-define(_CLIENT_VERSION_MAJOR, 24)
+define(_CLIENT_VERSION_MAJOR, 25)
 define(_CLIENT_VERSION_MINOR, 99)
 define(_CLIENT_VERSION_BUILD, 0)
 define(_CLIENT_VERSION_RC, 0)
diff --git a/doc/release-note-26194.md b/doc/release-note-26194.md
deleted file mode 100644
index b72dbf9a23..0000000000
--- a/doc/release-note-26194.md
+++ /dev/null
@@ -1,4 +0,0 @@
-Add `next_index` in `listdescriptors` RPC
------------------
-
-- Added a new `next_index` field in the response in `listdescriptors` to have the same format as `importdescriptors`
diff --git a/doc/release-notes-19762.md b/doc/release-notes-19762.md
deleted file mode 100644
index 4dc45fb2c8..0000000000
--- a/doc/release-notes-19762.md
+++ /dev/null
@@ -1,19 +0,0 @@
-JSON-RPC
----
-
-All JSON-RPC methods accept a new [named
-parameter](JSON-RPC-interface.md#parameter-passing) called `args` that can
-contain positional parameter values. This is a convenience to allow some
-parameter values to be passed by name without having to name every value. The
-python test framework and `bitcoin-cli` tool both take advantage of this, so
-for example:
-
-```sh
-bitcoin-cli -named createwallet wallet_name=mywallet load_on_startup=1
-```
-
-Can now be shortened to:
-
-```sh
-bitcoin-cli -named createwallet mywallet load_on_startup=1
-```
diff --git a/doc/release-notes-22087.md b/doc/release-notes-22087.md
deleted file mode 100644
index 8d7fd242b2..0000000000
--- a/doc/release-notes-22087.md
+++ /dev/null
@@ -1,4 +0,0 @@
-Updated settings
-----------------
-
-- Ports specified in `-port` and `-rpcport` options are now validated at startup. Values that previously worked and were considered valid can now result in errors. (#22087)
diff --git a/doc/release-notes-23395.md b/doc/release-notes-23395.md
deleted file mode 100644
index b9d7d9409c..0000000000
--- a/doc/release-notes-23395.md
+++ /dev/null
@@ -1,8 +0,0 @@
-Notable changes
-===============
-
-New settings
-------------
-
-- The `shutdownnotify` option is used to specify a command to execute synchronously
-before Bitcoin Core has begun its shutdown sequence. (#23395)
diff --git a/doc/release-notes-25375.md b/doc/release-notes-25375.md
deleted file mode 100644
index 504a2644f4..0000000000
--- a/doc/release-notes-25375.md
+++ /dev/null
@@ -1,11 +0,0 @@
-Updated RPCs
---------
-
-The `minconf` option, which allows a user to specify the minimum number
-of confirmations a UTXO being spent has, and the `maxconf` option,
-which allows specifying the maximum number of confirmations, have been
-added to the following RPCs:
-- `fundrawtransaction`
-- `send`
-- `walletcreatefundedpsbt`
-- `sendall`
diff --git a/doc/release-notes-25412.md b/doc/release-notes-25412.md
deleted file mode 100644
index b11fe73d45..0000000000
--- a/doc/release-notes-25412.md
+++ /dev/null
@@ -1,5 +0,0 @@
-New REST endpoint
------------------
-
-- A new `/rest/deploymentinfo` endpoint has been added for fetching various
-  state info regarding deployments of consensus changes. (#25412)
diff --git a/doc/release-notes-25574.md b/doc/release-notes-25574.md
deleted file mode 100644
index 312a99d95b..0000000000
--- a/doc/release-notes-25574.md
+++ /dev/null
@@ -1,13 +0,0 @@
-Updated settings
-----------------
-
-If the `-checkblocks` or `-checklevel` options are explicitly provided by the
-user, but the verification checks cannot be completed due to an insufficient
-dbcache, Bitcoin Core will now return an error at startup. (#25574)
-
-RPC
----
-The `-verifychain` RPC will now return `false` if the checks didn't fail,
-but couldn't be completed at the desired depth and level. This could be due
-to missing data while pruning, due to an insufficient dbcache or due to
-the node being shutdown before the call could finish. (#25574)
diff --git a/doc/release-notes-25730.md b/doc/release-notes-25730.md
deleted file mode 100644
index 33393cf314..0000000000
--- a/doc/release-notes-25730.md
+++ /dev/null
@@ -1,6 +0,0 @@
-RPC Wallet
-----------
-
-- RPC `listunspent` now has a new argument `include_immature_coinbase`
-  to include coinbase UTXOs that don't meet the minimum spendability
-  depth requirement (which before were silently skipped). (#25730)
\ No newline at end of file
diff --git a/doc/release-notes-25934.md b/doc/release-notes-25934.md
deleted file mode 100644
index b4f1ae0d3c..0000000000
--- a/doc/release-notes-25934.md
+++ /dev/null
@@ -1,8 +0,0 @@
-Low-level changes
-=================
-
-RPC
----
-
-- RPC `listsinceblock` now accepts an optional `label` argument
-  to fetch incoming transactions having the specified label. (#25934)
\ No newline at end of file
diff --git a/doc/release-notes-25943.md b/doc/release-notes-25943.md
deleted file mode 100644
index 81b0a48b5d..0000000000
--- a/doc/release-notes-25943.md
+++ /dev/null
@@ -1,4 +0,0 @@
-New RPC Argument
---------
-- `sendrawtransaction` has a new, optional argument, `maxburnamount` with a default value of `0`. Any transaction containing an unspendable output with a value greater than `maxburnamount` will not be submitted. At present, the outputs deemed unspendable are those with scripts that begin with an `OP_RETURN` code (known as 'datacarriers'), scripts that exceed the maximum script size, and scripts that contain invalid opcodes.
-
diff --git a/doc/release-notes-25957.md b/doc/release-notes-25957.md
deleted file mode 100644
index c71afa2c2e..0000000000
--- a/doc/release-notes-25957.md
+++ /dev/null
@@ -1,9 +0,0 @@
-Wallet
-------
-
-- Rescans for descriptor wallets are now significantly faster if compact
-  block filters (BIP158) are available. Since those are not constructed
-  by default, the configuration option "-blockfilterindex=1" has to be
-  provided to take advantage of the optimization. This improves the
-  performance of the RPC calls `rescanblockchain`, `importdescriptors`
-  and `restorewallet`. (#25957)
diff --git a/doc/release-notes-26213.md b/doc/release-notes-26213.md
deleted file mode 100644
index e78d718ca9..0000000000
--- a/doc/release-notes-26213.md
+++ /dev/null
@@ -1,8 +0,0 @@
-Low-level changes
-=================
-
-- Previously `setban`, `addpeeraddress`, `walletcreatefundedpsbt`, methods
-  allowed non-boolean and non-null values to be passed as boolean parameters.
-  Any string, number, array, or object value that was passed would be treated
-  as false. After this change, passing any value except `true`, `false`, or
-  `null` now triggers a JSON value is not of expected type error. (#26213)
diff --git a/doc/release-notes-26265.md b/doc/release-notes-26265.md
deleted file mode 100644
index ca2313d956..0000000000
--- a/doc/release-notes-26265.md
+++ /dev/null
@@ -1,6 +0,0 @@
-P2P and network changes
----------
-
-- Transactions of non-witness size 65 and above are now allowed by mempool
-  and relay policy. This is to better reflect the actual afforded protections
-  against CVE-2017-12842 and open up additional use-cases of smaller transaction sizes. (#26265)
diff --git a/doc/release-notes-26471.md b/doc/release-notes-26471.md
deleted file mode 100644
index 2cb74804ca..0000000000
--- a/doc/release-notes-26471.md
+++ /dev/null
@@ -1,13 +0,0 @@
-Updated settings
-----------------
-
-- Setting `-blocksonly` will now reduce the maximum mempool memory
-  to 5MB (users may still use `-maxmempool` to override). Previously,
-  the default 300MB would be used, leading to unexpected memory usage
-  for users running with `-blocksonly` expecting it to eliminate
-  mempool memory usage.
-
-  As unused mempool memory is shared with dbcache, this also reduces
-  the dbcache size for users running with `-blocksonly`, potentially
-  impacting performance.
-
diff --git a/doc/release-notes-26618.md b/doc/release-notes-26618.md
deleted file mode 100644
index 9d1ef3bd2e..0000000000
--- a/doc/release-notes-26618.md
+++ /dev/null
@@ -1,4 +0,0 @@
-RPC Wallet
-----------
-
-- RPC `unloadwallet` now fails if a rescan is in progress. (#26618)
diff --git a/doc/release-notes-26628.md b/doc/release-notes-26628.md
deleted file mode 100644
index 48a07c1e81..0000000000
--- a/doc/release-notes-26628.md
+++ /dev/null
@@ -1,4 +0,0 @@
-JSON-RPC
----
-
-The JSON-RPC server now rejects requests where a parameter is specified multiple times with the same name, instead of silently overwriting earlier parameter values with later ones. (#26628)
diff --git a/doc/release-notes-26646.md b/doc/release-notes-26646.md
deleted file mode 100644
index 7f94505a01..0000000000
--- a/doc/release-notes-26646.md
+++ /dev/null
@@ -1,8 +0,0 @@
-JSON-RPC
---------
-
-The `testmempoolaccept` RPC now returns 2 additional results within the "fees" result:
-"effective-feerate" is the feerate including fees and sizes of transactions validated together if
-package validation was used, and also includes any modified fees from prioritisetransaction. The
-"effective-includes" result lists the wtxids of transactions whose modified fees and sizes were used
-in the effective-feerate (#26646).
diff --git a/doc/release-notes-26896.md b/doc/release-notes-26896.md
deleted file mode 100644
index ff4ab44e27..0000000000
--- a/doc/release-notes-26896.md
+++ /dev/null
@@ -1,7 +0,0 @@
-Build System
-------------
-
-The --enable-upnp-default and --enable-natpmp-default options
-have been removed. If you want to use port mapping, you can
-configure it using a .conf file, or by passing the relevant
-options at runtime.
\ No newline at end of file
diff --git a/doc/release-notes-26899.md b/doc/release-notes-26899.md
deleted file mode 100644
index ceb9ec2f7a..0000000000
--- a/doc/release-notes-26899.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Updated settings
-----------------
-
-- Setting `-maxconnections=0` will now disable `-dnsseed`
-  and `-listen` (users may still set them to override).
\ No newline at end of file
diff --git a/doc/release-notes-27037.md b/doc/release-notes-27037.md
deleted file mode 100644
index ee30e64010..0000000000
--- a/doc/release-notes-27037.md
+++ /dev/null
@@ -1,5 +0,0 @@
-RPC
----
-
-- `decodescript` may now infer a Miniscript descriptor under P2WSH context if it is not lacking
-  information.
diff --git a/doc/release-notes-27068.md b/doc/release-notes-27068.md
deleted file mode 100644
index 3f5c5dba37..0000000000
--- a/doc/release-notes-27068.md
+++ /dev/null
@@ -1,6 +0,0 @@
-Wallet
-------
-
-- Wallet passphrases may now contain null characters.
-  Prior to this change, only characters up to the first
-  null character were recognized and accepted. (#27068)
\ No newline at end of file
diff --git a/doc/release-notes-27217.md b/doc/release-notes-27217.md
deleted file mode 100644
index ab1452fc94..0000000000
--- a/doc/release-notes-27217.md
+++ /dev/null
@@ -1,6 +0,0 @@
-Wallet
-------
-
-* Address Purposes strings are now restricted to the currently known values of "send", "receive", and "refund".
-  Wallets that have unrecognized purpose strings will have loading warnings, and the `listlabels`
-  RPC will raise an error if an unrecognized purpose is requested.
diff --git a/doc/release-notes-27279.md b/doc/release-notes-27279.md
deleted file mode 100644
index b664aee755..0000000000
--- a/doc/release-notes-27279.md
+++ /dev/null
@@ -1,10 +0,0 @@
-Wallet
-------
-
-- In the createwallet, loadwallet, unloadwallet, and restorewallet RPCs, the
-  "warning" string field is deprecated in favor of a "warnings" field that
-  returns a JSON array of strings to better handle multiple warning messages and
-  for consistency with other wallet RPCs. The "warning" field will be fully
-  removed from these RPCs in v26. It can be temporarily re-enabled during the
-  deprecation period by launching bitcoind with the configuration option
-  `-deprecatedrpc=walletwarningfield`. (#27279)