v30.3-roots.1 · Commit 58: [PATCH 58/68] doc: correct published Roots feature provenance
doc/roots-features.md
Before: doc/roots-features.md · After: doc/roots-features.md
File metadata
index fe8e85a2f8d14d62da417d936e843ed4f264e2a0..466ed224d9d8ed4904bc6de5b6f7a5b7c5d50e9d 100644
Download original patch · Release notes
Diff rows 1–54 of 54. 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
|
@@ -6,7 +6,7 @@ operator and local-policy work whose historical lineage includes Bitcoin Knots
|
|
| 6 |
tree is not a list of shipped features.
|
| 7 |
|
| 8 |
This page is the public inventory for Roots-specific work. The published
|
| 9 |
-
`v29.4-roots.2` release is the historical baseline. This checkout is the
|
| 10 |
unreleased candidate for the intended `v30.3-roots.1` release, ported directly
|
| 11 |
onto Bitcoin Core v30.3; candidate wording is not a release announcement.
|
| 12 |
Ordinary Bitcoin Core v30.3 functionality is documented in the built help and
|
|
@@ -15,8 +15,9 @@ this tree; use `bitcoind -help` as the authority for its exact options.
|
|
| 15 |
|
| 16 |
## Available in this checkout
|
| 17 |
|
| 18 |
-
Unless explicitly marked as `v30.3-roots.1` candidate work, the items in this
|
| 19 |
-
section were available in the published `v29.4-roots.2` baseline.
|
|
|
|
| 20 |
|
| 21 |
### Conservative, configurable local transaction policy
|
| 22 |
|
|
@@ -96,11 +97,11 @@ replacement will be accepted by peers or their local policy. This Roots
|
|
| 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.
|
| 98 |
|
| 99 |
-
### Advanced sweep and coin-control tools (candidate for `v30.3-roots.1`)
|
| 100 |
|
| 101 |
-
The intended `v30.3-roots.1` candidate adds a guarded private-key sweep and
|
| 102 |
-
advanced coin-control views. These tools are not part of the published
|
| 103 |
-
`v29.4-roots.2` release. Their operational contract and limitations are in
|
| 104 |
[`doc/wallet-privacy.md`](/doc/wallet-privacy.md); the built
|
| 105 |
`bitcoin-cli help sweepprivkeys` output is authoritative for the exact RPC
|
| 106 |
schema in a given build.
|
|
@@ -113,7 +114,7 @@ The key-handling path uses transient secure storage and clears temporary dialog
|
|
| 113 |
state; it does not promise erasure of every copy a GUI toolkit or host might
|
| 114 |
retain. Coin control presents wallet-reported selection, reuse, grouping, fee,
|
| 115 |
change, and RBF facts. It provides no privacy score or anonymity guarantee. The
|
| 116 |
-
candidate coverage includes
|
| 117 |
[`wallet_sweepprivkeys.py`](/test/functional/wallet_sweepprivkeys.py),
|
| 118 |
[`wallet_send.py`](/test/functional/wallet_send.py), and
|
| 119 |
[`src/qt/test/wallettests.cpp`](/src/qt/test/wallettests.cpp).
|
|
@@ -182,9 +183,9 @@ from the presence of a local tag alone.
|
|
| 182 |
|
| 183 |
## Planned or under review
|
| 184 |
|
| 185 |
-
The sweep and coin-control tools described above are intended
|
| 186 |
-
`v30.3-roots.1` candidate work, not part of the published baseline. The P2P
|
| 187 |
-
and wallet reviews otherwise retained the published-baseline behavior rather
|
| 188 |
than adding hardening or backup features. Cross-feature coverage and catalog
|
| 189 |
reconciliation are release-readiness work, not operator features. Any later
|
| 190 |
proposal remains under review until it has an accepted implementation and
|
|
|
|
| 6 |
tree is not a list of shipped features.
|
| 7 |
|
| 8 |
This page is the public inventory for Roots-specific work. The published
|
| 9 |
+
`v29.4-roots.4` release is the historical baseline. This checkout is the
|
| 10 |
unreleased candidate for the intended `v30.3-roots.1` release, ported directly
|
| 11 |
onto Bitcoin Core v30.3; candidate wording is not a release announcement.
|
| 12 |
Ordinary Bitcoin Core v30.3 functionality is documented in the built help and
|
|
|
|
| 15 |
|
| 16 |
## Available in this checkout
|
| 17 |
|
| 18 |
+
This section describes the current 30.3 checkout. The selected Roots features,
|
| 19 |
+
including sweep and coin control, were already available on the published
|
| 20 |
+
29.4 line; their implementations and tests are adapted to the Core 30.3 base.
|
| 21 |
|
| 22 |
### Conservative, configurable local transaction policy
|
| 23 |
|
|
|
|
| 97 |
[`src/qt/test/wallettests.cpp`](/src/qt/test/wallettests.cpp), including the
|
| 98 |
explicit overrides and saved-PSBT signaling; it is not broad coin control.
|
| 99 |
|
| 100 |
+
### Advanced sweep and coin-control tools (ported for `v30.3-roots.1`)
|
| 101 |
|
| 102 |
+
The intended `v30.3-roots.1` candidate preserves the guarded private-key sweep
|
| 103 |
+
and advanced coin-control views already available in the published
|
| 104 |
+
`v29.4-roots.4` release. Their operational contract and limitations are in
|
| 105 |
[`doc/wallet-privacy.md`](/doc/wallet-privacy.md); the built
|
| 106 |
`bitcoin-cli help sweepprivkeys` output is authoritative for the exact RPC
|
| 107 |
schema in a given build.
|
|
|
|
| 114 |
state; it does not promise erasure of every copy a GUI toolkit or host might
|
| 115 |
retain. Coin control presents wallet-reported selection, reuse, grouping, fee,
|
| 116 |
change, and RBF facts. It provides no privacy score or anonymity guarantee. The
|
| 117 |
+
retained coverage includes
|
| 118 |
[`wallet_sweepprivkeys.py`](/test/functional/wallet_sweepprivkeys.py),
|
| 119 |
[`wallet_send.py`](/test/functional/wallet_send.py), and
|
| 120 |
[`src/qt/test/wallettests.cpp`](/src/qt/test/wallettests.cpp).
|
|
|
|
| 183 |
|
| 184 |
## Planned or under review
|
| 185 |
|
| 186 |
+
The intended `v30.3-roots.1` candidate remains unreleased, including its
|
| 187 |
+
Core 30.3 adaptations of the existing sweep and coin-control tools. The P2P
|
| 188 |
+
and wallet reviews retained the published-baseline behavior rather
|
| 189 |
than adding hardening or backup features. Cross-feature coverage and catalog
|
| 190 |
reconciliation are release-readiness work, not operator features. Any later
|
| 191 |
proposal remains under review until it has an accepted implementation and
|