v30.3-roots.1 · Commit 17: [PATCH 17/68] docs: reconcile Roots feature catalog
doc/roots-features.md
Before: doc/roots-features.md · After: doc/roots-features.md
File metadata
index d77d0c5e182c77b0dddeef38018fec5f8ddc11d2..edb81e4aa8e389e81c853f20303ab9242727e916 100644
Download original patch · Release notes
Diff rows 1–101 of 101. Line numbers refer to the original before/after files.
+ Added− RemovedUnmarked lines are context.
Scroll the code area horizontally to read long lines. The two line-number columns refer to before and after.
doc/roots-features.md
CHANGED
|
@@ -5,12 +5,18 @@ operator and local-policy work whose historical lineage includes Bitcoin Knots
|
|
|
5
5
|
`29.3.knots20260507`; Knots is not an upstream dependency and its candidate
|
|
6
6
|
tree is not a list of shipped features.
|
|
7
7
|
|
|
8
|
-
This page is the public inventory for Roots-specific work. Ordinary Bitcoin Core
|
|
9
|
-
v30.3 functionality is documented in the built help and the manuals in this
|
|
10
|
-
directory. The commands below describe the binary that is built from this tree;
|
|
11
|
-
use `bitcoind -help` as the authority for the exact options in a given build.
|
|
8
|
+
This page is the public inventory for Roots-specific work. The published
|
|
9
|
+
`v29.4-roots.1` release is the historical baseline. This checkout is an unreleased
|
|
10
|
+
port onto Bitcoin Core v30.3 with follow-on additions identified below; it is
|
|
11
|
+
not a published release. Ordinary Bitcoin Core v30.3 functionality is documented
|
|
12
|
+
in the built help and the manuals in this directory. The commands below describe
|
|
13
|
+
the binary built from this tree; use `bitcoind -help` as the authority for the
|
|
14
|
+
exact options in a given build.
|
|
12
15
|
|
|
13
|
-
## Available now
|
|
16
|
+
## Available in this checkout
|
|
17
|
+
|
|
18
|
+
Unless marked as an unreleased follow-on, the items in this section were
|
|
19
|
+
available in the published `v29.4-roots.1` baseline.
|
|
14
20
|
|
|
15
21
|
### Conservative, configurable local transaction policy
|
|
16
22
|
|
|
@@ -44,7 +50,10 @@ The retained P2P coverage includes
|
|
|
44
50
|
[`p2p_invalid_messages.py`](/test/functional/p2p_invalid_messages.py).
|
|
45
51
|
This is not a Network Watch or transaction/block activity feed.
|
|
46
52
|
|
|
47
|
-
### Focused peer-health monitoring
|
|
53
|
+
The follow-on review retained these existing bounds and their coverage; it did
|
|
54
|
+
not add a separate P2P hardening feature or alter Bitcoin P2P wire behavior.
|
|
55
|
+
|
|
56
|
+
### Focused peer-health monitoring (unreleased follow-on)
|
|
48
57
|
|
|
49
58
|
The existing Debug window's Peers tab provides a bounded, live view of current
|
|
50
59
|
connections. Its sortable table shows connection age, direction, network,
|
|
@@ -55,7 +64,9 @@ connection type, current ping, and synchronization heights.
|
|
|
55
64
|
This uses the node's existing peer-stat refresh and does not retain history or
|
|
56
65
|
inspect transaction or block content. If optional node-state details cannot be
|
|
57
66
|
read during a refresh, the details pane reports them as unavailable instead of
|
|
58
|
-
showing values from an earlier peer.
|
|
67
|
+
showing values from an earlier peer. This Roots follow-on selection is covered
|
|
68
|
+
by [`src/qt/test/apptests.cpp`](/src/qt/test/apptests.cpp); it adds no new
|
|
69
|
+
network collector or monitoring application.
|
|
59
70
|
|
|
60
71
|
### Wallet and signing hardening
|
|
61
72
|
|
|
@@ -71,13 +82,19 @@ Legacy Berkeley DB support is a separate build choice. This catalog makes no
|
|
|
71
82
|
claim that it has been tested on a particular host library; release-compatible
|
|
72
83
|
legacy testing requires Berkeley DB 4.8.
|
|
73
84
|
|
|
74
|
-
### Per-send Replace-By-Fee choice
|
|
85
|
+
The follow-on review retained these existing wallet boundaries and their
|
|
86
|
+
coverage; it did not add a new database, flush, or backup behavior.
|
|
87
|
+
|
|
88
|
+
### Per-send Replace-By-Fee choice (unreleased follow-on)
|
|
75
89
|
|
|
76
90
|
The Send Coins dialog provides an explicit Replace-By-Fee (BIP-125) choice for
|
|
77
91
|
each transaction. It starts with the wallet's `-walletrbf` preference, and the
|
|
78
92
|
confirmation shows whether the prepared transaction signals replacement. This
|
|
79
93
|
only signals a transaction's replaceability; it does not promise that a later
|
|
80
|
-
replacement will be accepted by peers or their local policy.
|
|
94
|
+
replacement will be accepted by peers or their local policy. This Roots
|
|
95
|
+
follow-on selection is covered by
|
|
96
|
+
[`src/qt/test/wallettests.cpp`](/src/qt/test/wallettests.cpp), including the
|
|
97
|
+
explicit overrides and saved-PSBT signaling; it is not broad coin control.
|
|
81
98
|
|
|
82
99
|
### Runtime and operator foundations
|
|
83
100
|
|
|
@@ -112,8 +129,9 @@ has been tested by the current checkout.
|
|
|
112
129
|
### Roots identity and desktop application
|
|
113
130
|
|
|
114
131
|
The daemon, command-line tools, and Qt application identify themselves as
|
|
115
|
-
Bitcoin Roots `v30.3-roots.1`. The Qt application includes Roots branding and
|
|
116
|
-
icons. In the receive-request dialog, a QR image can be saved as a PNG. On
|
|
132
|
+
Bitcoin Roots `v30.3-roots.1`. This checkout is not a published release merely
|
|
133
|
+
because it has that build identity. The Qt application includes Roots branding
|
|
134
|
+
and icons. In the receive-request dialog, a QR image can be saved as a PNG. On
|
|
117
135
|
Windows GUI builds where taskbar progress is enabled, synchronization progress
|
|
118
136
|
is reflected in the taskbar. The Qt source and tests are in
|
|
119
137
|
[`src/qt/`](/src/qt/), including QR export coverage in
|
|
@@ -142,19 +160,12 @@ from the presence of a local tag alone.
|
|
|
142
160
|
|
|
143
161
|
## Planned or under review
|
|
144
162
|
|
|
145
|
-
The following areas are approved for evaluation in the follow-on operator
|
|
146
|
-
features plan. They are not available merely because they appear in a candidate
|
|
147
|
-
or in this roadmap.
|
|
148
|
-
|
|
149
|
-
1. Narrow P2P privacy and resource-use hardening.
|
|
150
|
-
2. Wallet database, flush, and backup reliability improvements.
|
|
151
|
-
3. Cross-feature regression coverage and catalog reconciliation.
|
|
152
|
-
|
|
153
|
-
Each item requires its own accepted implementation and tests before it moves to
|
|
154
|
-
the available section. Planned wallet reliability work does not imply a
|
|
155
|
-
guarantee about backup or recovery before the relevant tests exist. The plan
|
|
156
|
-
does not include Tor endpoint sharing, private-key sweeping, or broad or
|
|
157
|
-
privacy-aware coin control.
|
|
163
|
+
No additional operator feature from this follow-on series is available merely
|
|
164
|
+
because it was evaluated. The P2P and wallet reviews retained the existing
|
|
165
|
+
published-baseline behavior rather than adding new hardening or backup features.
|
|
166
|
+
Cross-feature coverage and catalog reconciliation are release-readiness work,
|
|
167
|
+
not operator features. Any later proposal remains under review until it has an
|
|
168
|
+
accepted implementation and tests.
|
|
158
169
|
|
|
159
170
|
## Consensus and provenance boundary
|
|
160
171
|
|