doc: Mention private broadcast RPCs in release notes
What changed, and why it matters
This commit is a documentation-only update to the release notes. It simply tells users about two new commands (RPCs) that let them check or stop private transaction broadcasts. No code behavior changed, and there is no security issue in the commit itself.
No security action needed; treat as routine documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds five lines to doc/release-notes-29415.md describing new RPCs getprivatebroadcastinfo and abortprivatebroadcast. It touches no executable code, no interfaces, and no configuration. It is purely a release-note clarification for functionality already implemented elsewhere.
Changed components
doc/release-notes-29415.mdInspect captured patch +5 / −0
diff --git a/doc/release-notes-29415.md b/doc/release-notes-29415.md
index d5040a31..c0e0f3dc 100644
--- a/doc/release-notes-29415.md
+++ b/doc/release-notes-29415.md
@@ -12,3 +12,8 @@ P2P and network changes
2. If the originator sends two otherwise unrelated transactions, they
will not be linkable. This is because a separate connection is used
for broadcasting each transaction. (#29415)
+
+- New RPCs have been added to introspect and control private broadcast:
+ `getprivatebroadcastinfo` reports transactions currently being privately
+ broadcast, and `abortprivatebroadcast` removes matching
+ transactions from the private broadcast queue.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.