Author: Eugene Siegel 2022-08-10 18:03:14
Published on: 2022-08-10T18:03:14+00:00
The conversation is about a function in bitcoind called PaysMoreThanConflicts, which checks that a transaction pays a higher fee rate than the replaced transaction. This function is not a BIP125 rule, so it may have caused confusion. The discussion also covers the ancestor bulking variant of pinning and how it matters in certain cases. If a low feerate ancestor junk puts the transaction at the bottom of the mempool, it would require a higher feerate to replace it through BIP125 rule#3, even if it has a high feerate itself. The new funding output can't have 1 OP_CSV unless the commit tx format changes. If it's not encumbered, an attacker can make a junk tree using the anchor output, and pinning exists. It is replaceable using RBF since you have your own commit tx (with anchor) to broadcast.
Updated on: 2023-06-03T09:40:05.850943+00:00