v30.3-roots.1 · Commit 40: [PATCH 40/68] docs: clarify opt-in TRUC replacement in node and RPC help
doc/release-notes-25.md
Before: doc/release-notes-25.md · After: doc/release-notes-25.md
File metadata
index a43aaa6aa7d40eef5cf27a2c06dfca6fbaf1784f..1b3fec4096d32082b2e6b14208581fbf5bd4b993 100644
Download original patch · Release notes
Diff rows 1–9 of 9. 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/release-notes-25.md
CHANGED
|
@@ -4,5 +4,9 @@
|
|
|
4
4
|
or `-mempoolfullrbf` select opt-in replacement or disable replacement.
|
|
5
5
|
Previously it always reported `true`.
|
|
6
6
|
|
|
7
|
+
- Opt-in replacement still permits non-signaling TRUC/v3 conflicts, even
|
|
8
|
+
though `fullrbf` is `false`. Disabling replacement rejects both signaling
|
|
9
|
+
and non-signaling input conflicts, including TRUC/v3 transactions.
|
|
10
|
+
|
|
7
11
|
This changes RPC reporting only. Relay policy and Bitcoin Core consensus
|
|
8
12
|
compatibility are unchanged.
|