What the developer wrote
Authored by rkrux
doc: add release notes for PR 34911
What changed, and why it matters
This commit only adds release notes describing a previously merged change. It does not modify any executable code, network behavior, or RPC logic. There is no security issue in this documentation-only commit.
No action required; this is a documentation-only commit. Review PR 34911 separately if assessing the security relevance of the underlying RPC deprecation changes.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit creates doc/release-notes-34911.md, a release-notes file that documents the removal of deprecated fullrbf and bip125-replaceable keys from mempool RPC responses unless explicitly requested via -deprecatedrpc arguments. The actual functional changes were made in PR 34911, not here. This commit is purely documentation.
Changed components
doc/release-notes-34911.mdInspect captured patch +12 / −0
diff --git a/doc/release-notes-34911.md b/doc/release-notes-34911.md
new file mode 100644
index 00000000..43520296
--- /dev/null
+++ b/doc/release-notes-34911.md
@@ -0,0 +1,12 @@
+### Mempool
+
+mempoolfullrbf=1 behaviour has been the default since v28 and the argument has
+been removed since v29 subsequently. The `getmempoolinfo` RPC stops returning the
+deprecated `fullrbf` key in the response unless the user requests it via the
+`-deprecatedrpc=fullrbf` node argument.
+
+Also, the `bip125-replaceable` key is removed from the mempool RPCs
+responses (because it, too, has been deprecated since v29) unless the user
+requests it via `-deprecatedrpc=bip125` node argument. Affected mempool RPCs
+are `getrawmempool`, `getmempoolancestors`, `getmempooldescendants`, and
+`getmempoolentry`.
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.