Merge bitcoin/bitcoin#31034: [28.x] doc: Sync 28.0 release notes with website

89d34cffed doc: Sync 28.0 release notes with website (Ava Chow)

Pull request description:

  Since there were some changes to the release notes after the tagging, update the in branch release notes to match those that ended up on the website.

ACKs for top commit:
  tdb3:
    ACK 89d34cffed

Tree-SHA512: 1feeafb0f604d36c1817e8bf38cbaef5d41f958dd823c99a19a1a9f7f1f1d38f917872c84b536dd784d7a672904ed2399369693f200a2837cd5707a686d3e634

doc/release-notes.md

@@ -25,9 +25,9 @@ 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.
 
-Running bitcoin core binaries on macOS requires self signing.
+Running Bitcoin Core binaries on macOS requires self signing.
 ```
-cd /path/to/bitcoin-core/bin
+cd /path/to/bitcoin-28.0/bin
 xattr -d com.apple.quarantine bitcoin-cli bitcoin-qt bitcoin-tx bitcoin-util bitcoin-wallet bitcoind test_bitcoin
 codesign -s - bitcoin-cli bitcoin-qt bitcoin-tx bitcoin-util bitcoin-wallet bitcoind test_bitcoin
 ```
@@ -37,7 +37,7 @@ Compatibility
 
 Bitcoin Core is supported and extensively tested on operating systems
 using the Linux Kernel 3.17+, macOS 11.0+, and Windows 7 and newer. Bitcoin
-Core should also work on most other Unix-like systems but is not as
+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.
 
@@ -53,7 +53,7 @@ the section header is also named `[testnet4]`.
 
 While the intention is to phase out support for Testnet3 in an upcoming
 version, support for it is still available via the known options in this
-release.
+release. (#29775)
 
 Windows Data Directory
 ----------------------
@@ -63,7 +63,22 @@ to `C:\Users\Username\AppData\Local\Bitcoin`. Bitcoin Core will check the existe
 of the old directory first and continue to use that directory for backwards
 compatibility if it is present. (#27064)
 
-P2P and network changes
+JSON-RPC 2.0 Support
+--------------------
+
+The JSON-RPC server now recognizes JSON-RPC 2.0 requests and responds with
+strict adherence to the [specification](https://www.jsonrpc.org/specification).
+See [JSON-RPC-interface.md](https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md#json-rpc-11-vs-20) for details. (#27101)
+
+JSON-RPC clients may need to be updated to be compatible with the JSON-RPC server.
+Please open an issue on GitHub if any compatibility issues are found.
+
+libbitcoinconsensus Removal
+---------------------------
+
+The libbitcoin-consensus library was deprecated in 27.0 and is now completely removed. (#29648)
+
+P2P and Network Changes
 -----------------------
 
 - Previously if Bitcoin Core was listening for P2P connections, either using
@@ -83,30 +98,30 @@ P2P and network changes
   binds had failed. (#22729)
 
 - UNIX domain sockets can now be used for proxy connections. Set `-onion` or `-proxy`
-to the local socket path with the prefix `unix:` (e.g. `-onion=unix:/home/me/torsocket`).
+  to the local socket path with the prefix `unix:` (e.g. `-onion=unix:/home/me/torsocket`).
-(#27375)
+  (#27375)
 
-- unix socket paths are now accepted for `-zmqpubrawblock` and `-zmqpubrawtx` with
+- UNIX socket paths are now accepted for `-zmqpubrawblock` and `-zmqpubrawtx` with
-the format `-zmqpubrawtx=unix:/path/to/file`
+  the format `-zmqpubrawtx=unix:/path/to/file` (#27679)
 
-- Additional flags "in" and "out" have been added to `-whitelist` to control whether
+- Additional "in" and "out" flags have been added to `-whitelist` to control whether
-  permissions apply to incoming connections and/or manual (default: incoming only).
+  permissions apply to inbound connections and/or manual ones (default: inbound only). (#27114)
 
-- Transactions that are too low feerate will be opportunistically paired with their child
+- Transactions having a feerate that is too low will be opportunistically paired with
-transactions and submitted as a package, thus enabling the node to download
+  their child transactions and submitted as a package, thus enabling the node to download
-1-parent-1-child packages using the existing transaction relay protocol. Combined with
+  1-parent-1-child packages using the existing transaction relay protocol. Combined with
-other mempool policies, this allows limited "package relay" when a parent transaction
+  other mempool policies, this change allows limited "package relay" when a parent transaction
-is below mempool minimum feerate; TRUC parents are additionally allowed to be below
+  is below the mempool minimum feerate. Topologically Restricted Until Confirmation (TRUC)
-minimum relay feerate (i.e. pay 0 fees). Use the `submitpackage` RPC to submit packages
+  parents are additionally allowed to be below the minimum relay feerate (i.e., pay 0 fees).
-directly to the node. Warning: this p2p feature is limited (unlike the `submitpackage`
+  Use the `submitpackage` RPC to submit packages directly to the node. Warning: this P2P
-interface, a child with multiple unconfirmed parents is not supported) and not yet
+  feature is limited (unlike the `submitpackage` interface, a child with multiple unconfirmed
-reliable under adversarial conditions. (#28970)
+  parents is not supported) and not yet reliable under adversarial conditions. (#28970)
 
 Mempool Policy Changes
 ----------------------
 
 - Transactions with version number set to 3 are now treated as standard on all networks (#29496),
-  subject to Opt-in Topologically Restricted Until Confirmation (TRUC) Transactions policy as
+  subject to opt-in Topologically Restricted Until Confirmation (TRUC) transaction policy as
   described in [BIP 431](https://github.com/bitcoin/bips/blob/master/bip-0431.mediawiki).  The
   policy includes limits on spending unconfirmed outputs (#28948), eviction of a previous descendant
   if a more incentive-compatible one is submitted (#29306), and a maximum transaction size of 10,000vB
@@ -120,71 +135,65 @@ Mempool Policy Changes
   top of an equivalent `sh(OP_TRUE)` output, in addition to the txid stability
   of the spending transaction.
   N.B. propagation of this output spending on the network will be limited
-  until a sufficient number of nodes on the network adopt this upgrade.
+  until a sufficient number of nodes on the network adopt this upgrade. (#30352)
 
 - Limited package RBF is now enabled, where the proposed conflicting package would result in
   a connected component, aka cluster, of size 2 in the mempool. All clusters being conflicted
-  against must be of size 2 or lower.
+  against must be of size 2 or lower. (#28984)
 
-- `mempoolfullrbf=1` is now set by default.
+- The default value of the `-mempoolfullrbf` configuration option has been changed from 0 to 1,
+  i.e. `mempoolfullrbf=1`. (#30493)
 
 Updated RPCs
 ------------
 
-- The JSON-RPC server now recognizes JSON-RPC 2.0 requests and responds with
-strict adherence to the [specification](https://www.jsonrpc.org/specification).
-See [JSON-RPC-interface.md](https://github.com/bitcoin/bitcoin/blob/master/doc/JSON-RPC-interface.md#json-rpc-11-vs-20) for details.
-
 - The `dumptxoutset` RPC now returns the UTXO set dump in a new and
-  improved format. At the same time the `loadtxoutset` RPC now
+  improved format. Correspondingly, the `loadtxoutset` RPC now expects
-  expects this new format in dumps it tries to load. Dumps with the
+  this new format in the dumps it tries to load. Dumps with the old
-  old format are no longer supported and need to be recreated using
+  format are no longer supported and need to be recreated using the
-  the new format in order to be usable.
+  new format to be usable. (#29612)
 
 - AssumeUTXO mainnet parameters have been added for height 840,000.
   This means the `loadtxoutset` RPC can now be used on mainnet with
-  the matching UTXO set from that height.
+  the matching UTXO set from that height. (#28553)
 
 - The `warnings` field in `getblockchaininfo`, `getmininginfo` and
   `getnetworkinfo` now returns all the active node warnings as an array
-  of strings, instead of just a single warning. The current behaviour
+  of strings, instead of a single warning. The current behaviour
-  can temporarily be restored by running bitcoind with configuration
+  can be temporarily restored by running Bitcoin Core with the configuration
-  option `-deprecatedrpc=warnings`.
+  option `-deprecatedrpc=warnings`. (#29845)
-
-- Previously when using the `sendrawtransaction` rpc and specifying outputs
-  that are already in the UXTO set an RPC error code `-27` with RPC error
-  text "Transaction already in block chain" was returned in response.
-  The help text has been updated to "Transaction outputs already in utxo set"
-  to more accurately describe the source of the issue.
 
-- The default mode for the `estimatesmartfee` RPC has been updated from `conservative` to `economical`.
+- Previously when using the `sendrawtransaction` RPC and specifying outputs
-  which is expected to reduce overestimation for many users, particularly if Replace-by-Fee is an option.
+  that are already in the UTXO set, an RPC error code of `-27` with the
-  For users that require high confidence in their fee estimates at the cost of potentially overestimating,
+  message "Transaction already in block chain" was returned in response.
-  the `conservative` mode remains available.
+  The error message has been changed to "Transaction outputs already in utxo set"
+  to more accurately describe the source of the issue. (#30212)
 
-- An item of `unspents`, of `scantxoutset`, has two new fields: `blockhash`
+- The default mode for the `estimatesmartfee` RPC has been updated from `conservative` to `economical`,
-  and `confirmations`. `blockhash` is the hash of the block where the UTXO was
+  which is expected to reduce over-estimation for many users, particularly if Replace-by-Fee is an option.
-  created. `confirmations` is the number of confirmations of the UTXO. (#30515)
+  For users that require high confidence in their fee estimates at the cost of potentially over-estimating,
+  the `conservative` mode remains available. (#30275)
 
-- `maxfeerate` and `maxburnamount` arguments are added to submitpackage.
+- RPC `scantxoutset` now returns 2 new fields in the "unspents" JSON array: `blockhash` and `confirmations`.
+  See the scantxoutset help for details. (#30515)
 
-Changes to wallet related RPCs can be found in the Wallet section below.
+- RPC `submitpackage` now allows 2 new arguments to be passed: `maxfeerate` and `maxburnamount`. See the
+  subtmitpackage help for details. (#28950)
 
-New RPCs
+Changes to wallet-related RPCs can be found in the Wallet section below.
---------
 
 Updated REST APIs
 -----------------
 - Parameter validation for `/rest/getutxos` has been improved by rejecting
-  truncated or overly large txids and malformed outpoint indices by raising an
+  truncated or overly large txids and malformed outpoint indices via raising
-  HTTP_BAD_REQUEST "Parse error". Previously, these malformed requests would be
+  an HTTP_BAD_REQUEST "Parse error". These requests were previously handled
-  silently handled. (#30482, #30444)
+  silently. (#30482, #30444)
 
 Build System
 ------------
 
 - GCC 11.1 or later, or Clang 16.0 or later,
-are now required to compile Bitcoin Core.
+are now required to compile Bitcoin Core. (#29091, #30263)
 
 - The minimum required glibc to run Bitcoin Core is now
 2.31. This means that RHEL 8 and Ubuntu 18.04 (Bionic)
@@ -192,57 +201,49 @@ are no-longer supported. (#29987)
 
 - `--enable-lcov-branch-coverage` has been removed, given
 incompatibilities between lcov version 1 & 2. `LCOV_OPTS`
-should be used to set any options instead.
+should be used to set any options instead. (#30192)
 
-Updated settings
+Updated Settings
 ----------------
 
 - When running with `-alertnotify`, an alert can now be raised multiple
 times instead of just once. Previously, it was only raised when unknown
-new consensus rules were activated, whereas the scope has now been
+new consensus rules were activated. Its scope has now been increased to
-increased to include all kernel warnings. Specifically, alerts will now
+include all kernel warnings. Specifically, alerts will now also be raised
-also be raised when an invalid chain with a large amount of work has
+when an invalid chain with a large amount of work has been detected.
-been detected. Additional warnings may be added in the future.
+Additional warnings may be added in the future. (#30058)
-(#30058)
 
 Changes to GUI or wallet related settings can be found in the GUI or Wallet section below.
 
-New settings
-------------
-
-Tools and Utilities
--------------------
-
 Wallet
 ------
 
-- The wallet now detects when wallet transactions conflict with the mempool. Mempool
+- The wallet now detects when wallet transactions conflict with the mempool. Mempool-conflicting
-conflicting transactions can be seen in the `"mempoolconflicts"` field of
+  transactions can be seen in the `"mempoolconflicts"` field of `gettransaction`. The inputs
-`gettransaction`. The inputs of mempool conflicted transactions can now be respent
+  of mempool-conflicted transactions can now be respent without manually abandoning the
-without manually abandoning the transactions when the parent transaction is dropped
+  transactions when the parent transaction is dropped from the mempool, which can cause wallet
-from the mempool, which can cause wallet balances to appear higher.
+  balances to appear higher. (#27307)
 
 - A new `max_tx_weight` option has been added to the RPCs `fundrawtransaction`, `walletcreatefundedpsbt`, and `send`.
 It specifies the maximum transaction weight. If the limit is exceeded during funding, the transaction will not be built.
-The default value is 4,000,000 WU.
+The default value is 4,000,000 WU. (#29523)
 
-- A new RPC `createwalletdescriptor` is added which allows users to add new automatically
+- A new `createwalletdescriptor` RPC allows users to add new automatically generated
-generated descriptors to their wallet. This can be used to upgrade wallets created prior to
+  descriptors to their wallet. This can be used to upgrade wallets created prior to the
-the introduction of a new standard descriptor, such as taproot.
+  introduction of a new standard descriptor, such as taproot. (#29130)
 
-- A new RPC `gethdkeys` is added which will list all of the BIP 32 HD keys in use by all
+- A new RPC `gethdkeys` lists all of the BIP32 HD keys in use by all of the descriptors in the wallet.
-of the descriptors in the wallet. These keys can be used in conjunction with `createwalletdescriptor`
+  These keys can be used in conjunction with `createwalletdescriptor` to create and add single key
-to create and add single key descriptors to the wallet for a particular key that the wallet
+  descriptors to the wallet for a particular key that the wallet already knows. (#29130)
-already knows.
 
-- The `sendall` RPC can spend unconfirmed change and will include additional fees as necessary
+- The `sendall` RPC can now spend unconfirmed change and will include additional fees as necessary
-for the resulting transaction to bump the unconfirmed transactions' feerates to the specified feerate.
+  for the resulting transaction to bump the unconfirmed transactions' feerates to the specified feerate. (#28979)
 
-- If a `fee_rate` is specified when using the `bumpfee` RPC, the feerate is no longer restricted to
+- In RPC `bumpfee`, if a `fee_rate` is specified, the feerate is no longer restricted
-following the wallet's incremental feerate of 5 sat/vb. The feerate must still be at least the sum
+  to following the wallet's incremental feerate of 5 sat/vb. The feerate must still be
-of the original fee and the mempool's incremental feerate.
+  at least the sum of the original fee and the mempool's incremental feerate. (#27969)
 
-GUI changes
+GUI Changes
 -----------
 
 - The "Migrate Wallet" menu allows users to migrate any legacy wallet in their wallet
@@ -251,25 +252,36 @@ directory, regardless of the wallets loaded. (gui#824)
 - The "Information" window now displays the maximum mempool size along with the
 mempool usage. (gui#825)
 
-Low-level changes
+Low-level Changes
 =================
 
-RPC
----
-
 Tests
 -----
 
-- The BIP94 timewarp attack mitigation is now active on the `regtest` network
+- The BIP94 timewarp attack mitigation is now active on the `regtest` network. (#30681)
 
-- `-testdatadir` is added to `test_bitcoin` to allow specifying the location for unit test data directories.
+- A new `-testdatadir` option has been added to `test_bitcoin` to allow specifying the
+  location of unit test data directories. (#26564)
 
 Blockstorage
 ------------
 
 - Block files are now XOR'd by default with a key stored in the blocksdir.
 Previous releases of Bitcoin Core or previous external software will not be able to read the blocksdir with a non-zero XOR-key.
-Refer to the `-blocksxor` help for more details.
+Refer to the `-blocksxor` help for more details. (#28052)
+
+Chainstate
+----------
+
+- The chainstate database flushes that occur when blocks are pruned will no longer
+empty the database cache. The cache will remain populated longer, which significantly
+reduces the time for initial block download to complete. (#28280)
+
+Dependencies
+------------
+
+- The dependency on Boost.Process has been replaced with cpp-subprocess, which is contained in source.
+Builders will no longer need Boost.Process to build with external signer support. (#28981)
 
 Credits
 =======