Skip to content
Bitcoin Roots

v29.4-roots.2 · Commit 16: [PATCH 16/21] feat(qt): add per-send RBF override

doc/roots-features.md

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

File metadata
index dcf8fe19070216a69ec000a4c057693cd0c52d39..eec8847fe59202e1e7f234b6e8eb840e74678895 100644

Download original patch · Release notes

Diff rows 1–23 of 23. 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
@@ -71,6 +71,14 @@ Legacy Berkeley DB support is a separate build choice. This catalog makes no
71
71
  claim that it has been tested on a particular host library; release-compatible
72
72
  legacy testing requires Berkeley DB 4.8.
73
73
 
74
+ ### Per-send Replace-By-Fee choice
75
+
76
+ The Send Coins dialog provides an explicit Replace-By-Fee (BIP-125) choice for
77
+ each transaction. It starts with the wallet's `-walletrbf` preference, and the
78
+ confirmation shows whether the prepared transaction signals replacement. This
79
+ only signals a transaction's replaceability; it does not promise that a later
80
+ replacement will be accepted by peers or their local policy.
81
+
74
82
  ### Runtime and operator foundations
75
83
 
76
84
  The `getmempoolstats` RPC returns the node's collected, non-interpolated
@@ -140,8 +148,7 @@ or in this roadmap.
140
148
 
141
149
  1. Narrow P2P privacy and resource-use hardening.
142
150
  2. Wallet database, flush, and backup reliability improvements.
143
- 3. An optional thin per-send RBF control.
144
- 4. Cross-feature regression coverage and catalog reconciliation.
151
+ 3. Cross-feature regression coverage and catalog reconciliation.
145
152
 
146
153
  Each item requires its own accepted implementation and tests before it moves to
147
154
  the available section. Planned wallet reliability work does not imply a