Merge bitcoin/bitcoin#34266: release note: cpfp carveout removed in 31.0

61726483e1c226c87212d0e12a3dd640fc393791 release note: cpfp carveout removed in 31.0 (Greg Sanders)

Pull request description:

  Seems it was overlooked for release notes, so let's add something

ACKs for top commit:
  l0rinc:
    ACK 61726483e1c226c87212d0e12a3dd640fc393791
  glozow:
    ACK 61726483e1c226c87212d0e12a3dd640fc393791

Tree-SHA512: 6d01a07977f530c1e3cc2a21a0ed27283e76813f1013af824a3690b47d7a2233244ede88c75d5f138c6965f94ebd6f3503741844522be5a0d1fdc188dee24d75
This commit is contained in:
merge-script 2026-01-12 15:11:42 -08:00
commit 5e98a6a470
No known key found for this signature in database
GPG Key ID: BA03F4DBE0C63FB4

View File

@ -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.