What the developer wrote
Authored by flack
Remove stale rationale paragraph
It belonged to the note removed in #33892
What changed, and why it matters
This commit only removes an outdated explanatory paragraph from a documentation file. No code, logic, or behavior of the Bitcoin Core software is changed. It is purely a cleanup of stale text that referenced a note removed in an earlier pull request.
No security action needed. This is a documentation-only cleanup.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change deletes an 8-line ‘Rationale’ section from doc/policy/packages.md. The deleted paragraph discussed why transactions below the minimum relay feerate should be prevented from entering the mempool, but the note it supported was already removed in PR #33892. The diff contains no functional changes to mempool policy, package validation, or any executable code.
Changed components
doc/policy/packages.mdInspect captured patch +0 / −8
diff --git a/doc/policy/packages.md b/doc/policy/packages.md
index d48afed4..71b1f2e4 100644
--- a/doc/policy/packages.md
+++ b/doc/policy/packages.md
@@ -99,14 +99,6 @@ submitted as a package.
transaction (i.e. in which a replacement transaction with a higher fee cannot be signed) being
rejected from the mempool when transaction volume is high and the mempool minimum feerate rises.
-*Rationale*: Avoid situations in which the mempool contains non-bumped transactions below min relay
-feerate (which we consider to have pay 0 fees and thus receiving free relay). While package
-submission would ensure these transactions are bumped at the time of entry, it is not guaranteed
-that the transaction will always be bumped. For example, a later transaction could replace the
-fee-bumping child without still bumping the parent. These no-longer-bumped transactions should be
-removed during a replacement, but we do not have a DoS-resistant way of removing them or enforcing a
-limit on their quantity. Instead, prevent their entry into the mempool.
-
Implementation Note: Transactions within a package are always validated individually first, and
package validation is used for the transactions that failed. Since package feerate is only
calculated using transactions that are not in the mempool, this implementation detail affects the
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.