Skip to content

Commit 0f6a526

Browse files
committed
Merge bitcoin/bitcoin#34160: policy: Remove stale rationale paragraph
337b4a2 Remove stale rationale paragraph (flack) Pull request description: It belonged to the note removed in #33892 ACKs for top commit: instagibbs: ACK 337b4a2 Tree-SHA512: 3cb1d3b87aa42ff92130af10ce2c286c0d83cbfdf17096d47b540ffe8e1a9a4727aedb8d477599fbff0002d7e262a6a52549dcccfa38dbe61281c221cf26cae2
2 parents 94ddc2d + 337b4a2 commit 0f6a526

File tree

1 file changed

+0
-8
lines changed

1 file changed

+0
-8
lines changed

doc/policy/packages.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -99,14 +99,6 @@ submitted as a package.
9999
transaction (i.e. in which a replacement transaction with a higher fee cannot be signed) being
100100
rejected from the mempool when transaction volume is high and the mempool minimum feerate rises.
101101

102-
*Rationale*: Avoid situations in which the mempool contains non-bumped transactions below min relay
103-
feerate (which we consider to have pay 0 fees and thus receiving free relay). While package
104-
submission would ensure these transactions are bumped at the time of entry, it is not guaranteed
105-
that the transaction will always be bumped. For example, a later transaction could replace the
106-
fee-bumping child without still bumping the parent. These no-longer-bumped transactions should be
107-
removed during a replacement, but we do not have a DoS-resistant way of removing them or enforcing a
108-
limit on their quantity. Instead, prevent their entry into the mempool.
109-
110102
Implementation Note: Transactions within a package are always validated individually first, and
111103
package validation is used for the transactions that failed. Since package feerate is only
112104
calculated using transactions that are not in the mempool, this implementation detail affects the

0 commit comments

Comments
 (0)