v29.4-roots.4 · Commit 17: [PATCH 17/37] docs: reconcile Roots feature catalog

doc/roots-features.md

Before: doc/roots-features.md · After: doc/roots-features.md

File metadata

index eec8847fe59202e1e7f234b6e8eb840e74678895..2d620408895a71b7309d7ac2aad5569b3d89db93 100644

Download original patch · Release notes

Diff rows 1–109 of 109. Line numbers refer to the original before/after files.

+ Added− RemovedUnmarked lines are context.

Scroll the code area horizontally to read long lines. Before is on the left; after is on the right. Unified view fits narrow screens more easily.

doc/roots-features.md CHANGED Viewed

@@ -5,12 +5,19 @@ operator and local-policy work whose historical lineage includes Bitcoin Knots
 `29.3.knots20260507`; Knots is not an upstream dependency and its candidate
 tree is not a list of shipped features.
-This page is the public inventory for Roots-specific work. Ordinary Bitcoin Core
-v29.4 functionality is documented in the built help and the manuals in this
-directory. The commands below describe the binary that is built from this tree;
-use `bitcoind -help` as the authority for the exact options in a given build.
-## Available now
 ### Conservative, configurable local transaction policy
@@ -44,7 +51,10 @@ The retained P2P coverage includes
 [`p2p_invalid_messages.py`](/test/functional/p2p_invalid_messages.py).
 This is not a Network Watch or transaction/block activity feed.
-### Focused peer-health monitoring
 The existing Debug window's Peers tab provides a bounded, live view of current
 connections. Its sortable table shows connection age, direction, network,
@@ -55,7 +65,9 @@ connection type, current ping, and synchronization heights.
 This uses the node's existing peer-stat refresh and does not retain history or
 inspect transaction or block content. If optional node-state details cannot be
 read during a refresh, the details pane reports them as unavailable instead of
-showing values from an earlier peer.
 ### Wallet and signing hardening
@@ -71,13 +83,19 @@ Legacy Berkeley DB support is a separate build choice. This catalog makes no
 claim that it has been tested on a particular host library; release-compatible
 legacy testing requires Berkeley DB 4.8.
-### Per-send Replace-By-Fee choice
 The Send Coins dialog provides an explicit Replace-By-Fee (BIP-125) choice for
 each transaction. It starts with the wallet's `-walletrbf` preference, and the
 confirmation shows whether the prepared transaction signals replacement. This
 only signals a transaction's replaceability; it does not promise that a later
-replacement will be accepted by peers or their local policy.
 ### Runtime and operator foundations
@@ -111,11 +129,13 @@ has been tested by the current checkout.
 ### Roots identity and desktop application
-The daemon, command-line tools, and Qt application identify themselves as
-Bitcoin Roots `v29.4-roots.1`. The Qt application includes Roots branding and
-icons. In the receive-request dialog, a QR image can be saved as a PNG. On
-Windows GUI builds where taskbar progress is enabled, synchronization progress
-is reflected in the taskbar. The Qt source and tests are in
 [`src/qt/`](/src/qt/), including QR export coverage in
 [`src/qt/test/apptests.cpp`](/src/qt/test/apptests.cpp).
@@ -142,19 +162,12 @@ in this checkout.
 ## Planned or under review
-The following areas are approved for evaluation in the follow-on operator
-features plan. They are not available merely because they appear in a candidate
-or in this roadmap.
-1. Narrow P2P privacy and resource-use hardening.
-2. Wallet database, flush, and backup reliability improvements.
-3. Cross-feature regression coverage and catalog reconciliation.
-Each item requires its own accepted implementation and tests before it moves to
-the available section. Planned wallet reliability work does not imply a
-guarantee about backup or recovery before the relevant tests exist. The plan
-does not include Tor endpoint sharing, private-key sweeping, or broad or
-privacy-aware coin control.
 ## Consensus and provenance boundary

 `29.3.knots20260507`; Knots is not an upstream dependency and its candidate
 tree is not a list of shipped features.
+This page is the public inventory for Roots-specific work. The published
+`v29.4-roots.1` release is the baseline. This checkout is an unreleased
+post-`v29.4-roots.1` follow-on candidate: its accepted additions are identified
+below and must not be read as claims about that published release. Ordinary
+Bitcoin Core v29.4 functionality is documented in the built help and the
+manuals in this directory. The commands below describe the binary built from
+this tree; use `bitcoind -help` as the authority for the exact options in a
+given build.
+## Available in this checkout
+Unless marked as an unreleased follow-on, the items in this section were
+available in the published `v29.4-roots.1` baseline.
 ### Conservative, configurable local transaction policy
 [`p2p_invalid_messages.py`](/test/functional/p2p_invalid_messages.py).
 This is not a Network Watch or transaction/block activity feed.
+The follow-on review retained these existing bounds and their coverage; it did
+not add a separate P2P hardening feature or alter Bitcoin P2P wire behavior.
+### Focused peer-health monitoring (unreleased follow-on)
 The existing Debug window's Peers tab provides a bounded, live view of current
 connections. Its sortable table shows connection age, direction, network,
 This uses the node's existing peer-stat refresh and does not retain history or
 inspect transaction or block content. If optional node-state details cannot be
 read during a refresh, the details pane reports them as unavailable instead of
+showing values from an earlier peer. This Roots follow-on selection is covered
+by [`src/qt/test/apptests.cpp`](/src/qt/test/apptests.cpp); it adds no new
+network collector or monitoring application.
 ### Wallet and signing hardening
 claim that it has been tested on a particular host library; release-compatible
 legacy testing requires Berkeley DB 4.8.
+The follow-on review retained these existing wallet boundaries and their
+coverage; it did not add a new database, flush, or backup behavior.
+### Per-send Replace-By-Fee choice (unreleased follow-on)
 The Send Coins dialog provides an explicit Replace-By-Fee (BIP-125) choice for
 each transaction. It starts with the wallet's `-walletrbf` preference, and the
 confirmation shows whether the prepared transaction signals replacement. This
 only signals a transaction's replaceability; it does not promise that a later
+replacement will be accepted by peers or their local policy. This Roots
+follow-on selection is covered by
+[`src/qt/test/wallettests.cpp`](/src/qt/test/wallettests.cpp), including the
+explicit overrides and saved-PSBT signaling; it is not broad coin control.
 ### Runtime and operator foundations
 ### Roots identity and desktop application
+The published baseline's daemon, command-line tools, and Qt application identify
+themselves as Bitcoin Roots `v29.4-roots.1`. The follow-on candidate is not a
+published release merely because it retains that build identity. The Qt
+application includes Roots branding and icons. In the receive-request dialog, a
+QR image can be saved as a PNG. On Windows GUI builds where taskbar progress is
+enabled, synchronization progress is reflected in the taskbar. The Qt source
+and tests are in
 [`src/qt/`](/src/qt/), including QR export coverage in
 [`src/qt/test/apptests.cpp`](/src/qt/test/apptests.cpp).
 ## Planned or under review
+No additional operator feature from this follow-on series is available merely
+because it was evaluated. The P2P and wallet reviews retained the existing
+published-baseline behavior rather than adding new hardening or backup features.
+Cross-feature coverage and catalog reconciliation are release-readiness work,
+not operator features. Any later proposal remains under review until it has an
+accepted implementation and tests.
 ## Consensus and provenance boundary