release note: cpfp carveout removed in 31.0
What the developer wrote
Authored by Greg Sanders
release note: cpfp carveout removed in 31.0
What changed, and why it matters
This commit only adds a release note documenting that a mempool feature called the 'CPFP Carveout' was removed in Bitcoin Core version 31.0. It does not change any code, fix a bug, or address a security vulnerability. It is purely informational documentation for users and developers.
No security action needed. Review the release note for awareness of the policy change if operating Bitcoin Core nodes or services dependent on CPFP Carveout behavior.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds a paragraph to doc/release-notes-33629.md explaining that the CPFP Carveout policy has been removed from mempool logic. The carveout previously permitted one extra small child transaction to exceed the descendant limit under strict conditions. The release note states that future use-cases should use TRUC transactions and sibling eviction instead. No source code is modified.
Changed components
doc/release-notes-33629.mdInspect captured patch +8 / −0
diff --git a/doc/release-notes-33629.md b/doc/release-notes-33629.md
index 16bdf0fd..46adf220 100644
--- a/doc/release-notes-33629.md
+++ b/doc/release-notes-33629.md
@@ -41,3 +41,11 @@ are noted:
mempool.
- Chunk size and chunk fees are now also included in the output of `getmempoolentry`.
+
+- The "CPFP Carveout" has been removed from the mempool logic. The CPFP carveout
+ allowed one additional child transaction to be added to a package that's already
+ at its descendant limit, but only if that child has exactly one ancestor
+ (the package's root) and is small (no larger than 10kvB). Nothing is allowed to
+ bypass the cluster count limit. It is expected that smart contracting use-cases
+ requiring similar functionality employ TRUC transactions and sibling eviction
+ instead going forward.
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.