doc: consolidate release note fragments

22 files changed, 1 insertions, 266 deletions

diff --git a/doc/release-notes-123.md b/doc/release-notes-123.md
deleted file mode 100644
index fffd211f37..0000000000
--- a/doc/release-notes-123.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Tools and Utilities
----
-
-- A new `bitcoinconsensus_verify_script_with_spent_outputs` function is available in libconsensus which optionally accepts the spent outputs of the transaction being verified.
-- A new `bitcoinconsensus_SCRIPT_FLAGS_VERIFY_TAPROOT` flag is available in libconsensus that will verify scripts with the Taproot spending rules.
\ No newline at end of file
diff --git a/doc/release-notes-24914.md b/doc/release-notes-24914.md
deleted file mode 100644
index 505d356fce..0000000000
--- a/doc/release-notes-24914.md
+++ /dev/null
@@ -1,9 +0,0 @@
-Wallet
-------
-
-- Wallet loading has changed in this release. Wallets with some corrupted records that could be
-  previously loaded (with warnings) may no longer load. For example, wallets with corrupted
-  address book entries may no longer load. If this happens, it is recommended
-  load the wallet in a previous version of Bitcoin Core and import the data into a new wallet.
-  Please also report an issue to help improve the software and make wallet loading more robust
-  in these cases.
diff --git a/doc/release-notes-25158.md b/doc/release-notes-25158.md
deleted file mode 100644
index ce8ab53ddd..0000000000
--- a/doc/release-notes-25158.md
+++ /dev/null
@@ -1,6 +0,0 @@
-RPC Wallet
-----------
-
-- The `gettransaction`, `listtransactions`, `listsinceblock` RPCs now return
-  the `abandoned` field for all transactions. Previously, the "abandoned" field
-  was only returned for sent transactions. (#25158)
\ No newline at end of file
diff --git a/doc/release-notes-26076.md b/doc/release-notes-26076.md
deleted file mode 100644
index f95e4be0e3..0000000000
--- a/doc/release-notes-26076.md
+++ /dev/null
@@ -1,13 +0,0 @@
-RPC
----
-
-- The `listdescriptors`, `decodepsbt` and similar RPC methods now show `h` rather than apostrophe (`'`) to indicate
-  hardened derivation. This does not apply when using the `private` parameter, which
-  matches the marker used when descriptor was generated or imported. Newly created
-  wallets use `h`. This change makes it easier to handle descriptor strings manually.
-  E.g. the `importdescriptors` RPC call is easiest to use `h` as the marker: `'["desc": ".../0h/..."]'`.
-  With this change `listdescriptors` will use `h`, so you can copy-paste the result,
-  without having to add escape characters or switch `'` to 'h' manually.
-  Note that this changes the descriptor checksum.
-  For legacy wallets the `hdkeypath` field in `getaddressinfo` is unchanged,
-  nor is the serialization format of wallet dumps. (#26076)
diff --git a/doc/release-notes-26094.md b/doc/release-notes-26094.md
deleted file mode 100644
index ba73f2707e..0000000000
--- a/doc/release-notes-26094.md
+++ /dev/null
@@ -1,6 +0,0 @@
-- The `getbalances` RPC now returns a `lastprocessedblock` JSON object which contains the wallet's last processed block
-  hash and height at the time the balances were calculated. This result shouldn't be cached because importing new keys could invalidate it.
-- The `gettransaction` RPC now returns a `lastprocessedblock` JSON object which contains the wallet's last processed block
-  hash and height at the time the transaction information was generated.
-- The `getwalletinfo` RPC now returns a `lastprocessedblock` JSON object which contains the wallet's last processed block
-  hash and height at the time the wallet information was generated.
\ No newline at end of file
diff --git a/doc/release-notes-26485.md b/doc/release-notes-26485.md
deleted file mode 100644
index c8df3d22fb..0000000000
--- a/doc/release-notes-26485.md
+++ /dev/null
@@ -1,16 +0,0 @@
-JSON-RPC
----
-
-For RPC methods which accept `options` parameters ((`importmulti`, `listunspent`, `fundrawtransaction`, `bumpfee`, `send`, `sendall`, `walletcreatefundedpsbt`, `simulaterawtransaction`), it is now possible to pass the options as named parameters without the need for a nested object. (#26485)
-
-This means it is possible make calls like:
-
-```sh
-src/bitcoin-cli -named bumpfee txid fee_rate=100
-```
-
-instead of
-
-```sh
-src/bitcoin-cli -named bumpfee txid options='{"fee_rate": 100}'
-```
diff --git a/doc/release-notes-27213.md b/doc/release-notes-27213.md
deleted file mode 100644
index 3b478f11b7..0000000000
--- a/doc/release-notes-27213.md
+++ /dev/null
@@ -1,8 +0,0 @@
-P2P and network changes
-------
-
-- Nodes with multiple reachable networks will actively try to have at least one
-  outbound connection to each network. This improves individual resistance to
-  eclipse attacks and network level resistance to partition attacks. Users no
-  longer need to perform active measures to ensure being connected to multiple
-  enabled networks.
diff --git a/doc/release-notes-27302.md b/doc/release-notes-27302.md
deleted file mode 100644
index e67a6c8b06..0000000000
--- a/doc/release-notes-27302.md
+++ /dev/null
@@ -1,4 +0,0 @@
-Configuration
----
-
-- `bitcoind` and `bitcoin-qt` will now raise an error on startup if a datadir that is being used contains a bitcoin.conf file that will be ignored, which can happen when a datadir= line is used in a bitcoin.conf file. The error message is just a diagnostic intended to prevent accidental misconfiguration, and it can be disabled to restore the previous behavior of using the datadir while ignoring the bitcoin.conf contained in it.
diff --git a/doc/release-notes-27460.md b/doc/release-notes-27460.md
deleted file mode 100644
index d663ec0baf..0000000000
--- a/doc/release-notes-27460.md
+++ /dev/null
@@ -1,7 +0,0 @@
-- A new `importmempool` RPC has been added. It loads a valid `mempool.dat` file and attempts to
-  add its contents to the mempool. This can be useful to import mempool data from another node
-  without having to modify the datadir contents and without having to restart the node. (#27460)
-    - Warning: Importing untrusted files is dangerous, especially if metadata from the file is taken over.
-    - If you want to apply fee deltas, it is recommended to use the `getprioritisedtransactions` and
-      `prioritisetransaction` RPCs instead of the `apply_fee_delta_priority` option to avoid
-      double-prioritising any already-prioritised transactions in the mempool.
diff --git a/doc/release-notes-27501.md b/doc/release-notes-27501.md
deleted file mode 100644
index 386a00fb34..0000000000
--- a/doc/release-notes-27501.md
+++ /dev/null
@@ -1,3 +0,0 @@
-- A new `getprioritisedtransactions` RPC has been added. It returns a map of all fee deltas created by the
-  user with prioritisetransaction, indexed by txid. The map also indicates whether each transaction is
-  present in the mempool.
diff --git a/doc/release-notes-27596.md b/doc/release-notes-27596.md
deleted file mode 100644
index cbaf4b3a9e..0000000000
--- a/doc/release-notes-27596.md
+++ /dev/null
@@ -1,28 +0,0 @@
-Pruning
--------
-
-When using assumeutxo with `-prune`, the prune budget may be exceeded if it is set
-lower than 1100MB (i.e. `MIN_DISK_SPACE_FOR_BLOCK_FILES * 2`). Prune budget is normally
-split evenly across each chainstate, unless the resulting prune budget per chainstate
-is beneath `MIN_DISK_SPACE_FOR_BLOCK_FILES` in which case that value will be used.
-
-RPC
----
-
-`loadtxoutset` has been added, which allows loading a UTXO snapshot of the format
-generated by `dumptxoutset`. Once this snapshot is loaded, its contents will be
-deserialized into a second chainstate data structure, which is then used to sync to
-the network's tip.
-
-Meanwhile, the original chainstate will complete the initial block download process in
-the background, eventually validating up to the block that the snapshot is based upon.
-
-The result is a usable bitcoind instance that is current with the network tip in a
-matter of minutes rather than hours. UTXO snapshot are typically obtained via
-third-party sources (HTTP, torrent, etc.) which is reasonable since their contents
-are always checked by hash.
-
-You can find more information on this process in the `assumeutxo` design
-document (<https://github.com/bitcoin/bitcoin/blob/master/doc/design/assumeutxo.md>).
-
-`getchainstates` has been added to aid in monitoring the assumeutxo sync process.
diff --git a/doc/release-notes-27609.md b/doc/release-notes-27609.md
deleted file mode 100644
index b8cecbd882..0000000000
--- a/doc/release-notes-27609.md
+++ /dev/null
@@ -1,14 +0,0 @@
-- A new RPC, `submitpackage`, has been added. It can be used to submit a list of raw hex
-  transactions to the mempool to be evaluated as a package using consensus and mempool policy rules.
-These policies include package CPFP, allowing a child with high fees to bump a parent below the
-mempool minimum feerate (but not minimum relay feerate).
-
-    - Warning: successful submission does not mean the transactions will propagate throughout the
-      network, as package relay is not supported.
-
-    - Not all features are available. The package is limited to a child with all of its
-      unconfirmed parents, and no parent may spend the output of another parent.  Also, package
-      RBF is not supported. Refer to doc/policy/packages.md for more details on package policies
-      and limitations.
-
-    - This RPC is experimental. Its interface may change.
diff --git a/doc/release-notes-27632.md b/doc/release-notes-27632.md
deleted file mode 100644
index d588247c85..0000000000
--- a/doc/release-notes-27632.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Updated settings
-----------------
-
-- Passing an invalid `-debug`, `-debugexclude`, or `-loglevel` logging configuration
-  option now raises an error, rather than logging an easily missed warning. (#27632)
diff --git a/doc/release-notes-27757.md b/doc/release-notes-27757.md
deleted file mode 100644
index fb6aaa01a5..0000000000
--- a/doc/release-notes-27757.md
+++ /dev/null
@@ -1,8 +0,0 @@
-Wallet
-------
-
-- The `deprecatedrpc=walletwarningfield` configuration option has been removed.
-  The `createwallet`, `loadwallet`, `restorewallet` and `unloadwallet` RPCs no
-  longer return the "warning" string field. The same information is provided
-  through the "warnings" field added in v25.0, which returns a JSON array of
-  strings. The "warning" string field was deprecated also in v25.0. (#27757)
diff --git a/doc/release-notes-28113.md b/doc/release-notes-28113.md
deleted file mode 100644
index c9f418dbbb..0000000000
--- a/doc/release-notes-28113.md
+++ /dev/null
@@ -1,7 +0,0 @@
-RPC Wallet
-----------
-
-- The `signrawtransactionwithkey`, `signrawtransactionwithwallet`,
-  `walletprocesspsbt` and `descriptorprocesspsbt` calls now return the more
-  specific RPC_INVALID_PARAMETER error instead of RPC_MISC_ERROR if their
-  sighashtype argument is malformed.
diff --git a/doc/release-notes-28354.md b/doc/release-notes-28354.md
deleted file mode 100644
index 03d421eb42..0000000000
--- a/doc/release-notes-28354.md
+++ /dev/null
@@ -1,6 +0,0 @@
-Tests
------
-
-- Non-standard transactions are now disabled by default on testnet
-  for relay and mempool acceptance. The previous behaviour can be
-  re-enabled by setting `-acceptnonstdtxn=1`. (#28354)
diff --git a/doc/release-notes-28414.md b/doc/release-notes-28414.md
deleted file mode 100644
index 3f83a73252..0000000000
--- a/doc/release-notes-28414.md
+++ /dev/null
@@ -1,6 +0,0 @@
-RPC Wallet
-----------
-
-- RPC `walletprocesspsbt`, and `descriptorprocesspsbt` return object now includes field `hex` (if the transaction
-is complete) containing the serialized transaction suitable for RPC `sendrawtransaction`.
-
diff --git a/doc/release-notes-28448.md b/doc/release-notes-28448.md
deleted file mode 100644
index d3ef8cf65b..0000000000
--- a/doc/release-notes-28448.md
+++ /dev/null
@@ -1,6 +0,0 @@
-RPC
----
-
-- Setting `-rpcserialversion=0` is deprecated and will be removed in
-  a future release. It can currently still be used by also adding
-  the `-deprecatedrpc=serialversion` option. (#28448)
diff --git a/doc/release-notes-28685.md b/doc/release-notes-28685.md
deleted file mode 100644
index 6f04d8d542..0000000000
--- a/doc/release-notes-28685.md
+++ /dev/null
@@ -1,4 +0,0 @@
-RPC
----
-
-The `hash_serialized_2` value has been removed from `gettxoutsetinfo` since the value it calculated contained a bug and did not take all data into account. It is superseded by `hash_serialized_3` which provides the same functionality but serves the correctly calculated hash.
diff --git a/doc/release-notes-empty-template.md b/doc/release-notes-empty-template.md
deleted file mode 100644
index 887104548b..0000000000
--- a/doc/release-notes-empty-template.md
+++ /dev/null
@@ -1,99 +0,0 @@
-*The release notes draft is a temporary file that can be added to by anyone. See
-[/doc/developer-notes.md#release-notes](/doc/developer-notes.md#release-notes)
-for the process.*
-
-*version* Release Notes Draft
-===============================
-
-Bitcoin Core version *version* is now available from:
-
-  <https://bitcoincore.org/bin/bitcoin-core-*version*/>
-
-This release includes new features, various bug fixes and performance
-improvements, as well as updated translations.
-
-Please report bugs using the issue tracker at GitHub:
-
-  <https://github.com/bitcoin/bitcoin/issues>
-
-To receive security and update notifications, please subscribe to:
-
-  <https://bitcoincore.org/en/list/announcements/join/>
-
-How to Upgrade
-==============
-
-If you are running an older version, shut it down. Wait until it has completely
-shut down (which might take a few minutes in some cases), then run the
-installer (on Windows) or just copy over `/Applications/Bitcoin-Qt` (on macOS)
-or `bitcoind`/`bitcoin-qt` (on Linux).
-
-Upgrading directly from a version of Bitcoin Core that has reached its EOL is
-possible, but it might take some time if the data directory needs to be migrated. Old
-wallet versions of Bitcoin Core are generally supported.
-
-Compatibility
-==============
-
-Bitcoin Core is supported and extensively tested on operating systems
-using the Linux kernel, macOS 11.0+, and Windows 7 and newer.  Bitcoin
-Core should also work on most other Unix-like systems but is not as
-frequently tested on them.  It is not recommended to use Bitcoin Core on
-unsupported systems.
-
-Notable changes
-===============
-
-P2P and network changes
------------------------
-
-Updated RPCs
-------------
-
-
-Changes to wallet related RPCs can be found in the Wallet section below.
-
-New RPCs
---------
-
-Build System
-------------
-
-Updated settings
-----------------
-
-
-Changes to GUI or wallet related settings can be found in the GUI or Wallet section below.
-
-New settings
-------------
-
-Tools and Utilities
--------------------
-
-Wallet
-------
-
-GUI changes
------------
-
-Low-level changes
-=================
-
-RPC
----
-
-Tests
------
-
-*version* change log
-====================
-
-Credits
-=======
-
-Thanks to everyone who directly contributed to this release:
-
-
-As well as to everyone that helped with translations on
-[Transifex](https://www.transifex.com/bitcoin/bitcoin/).
diff --git a/doc/release-notes.md b/doc/release-notes.md
new file mode 100644
index 0000000000..b40e1296d0
--- /dev/null
+++ b/doc/release-notes.md
@@ -0,0 +1 @@
+See https://github.com/bitcoin-core/bitcoin-devwiki/wiki/26.0%E2%80%90Release%E2%80%90Notes%E2%80%90Draft.
\ No newline at end of file
diff --git a/doc/release-notes/release-notes-27511.md b/doc/release-notes/release-notes-27511.md
deleted file mode 100644
index b5c0847e31..0000000000
--- a/doc/release-notes/release-notes-27511.md
+++ /dev/null
@@ -1,6 +0,0 @@
-New RPCs
---------
-
-- A new RPC `getaddrmaninfo` has been added to view the distribution of addresses in the new and tried table of the
-  node's address manager across different networks(ipv4, ipv6, onion, i2p, cjdns). The RPC returns count of addresses
-  in new and tried table as well as their sum for all networks. (#27511)