Author: Rhavar 2018-01-23 22:19:59
Published on: 2018-01-23T22:19:59+00:00
In a discussion on the bitcoin-dev mailing list, Ryan proposed changing the fee requirement for transactions to support more use cases and make it more incentive compatible. He suggested that the new fee should be at least the minimum between the original fee rate times the replacement transaction size plus the relay fee, or one-third of the original absolute fee. This change would allow for "retroactive transaction merging" and would be resistant to attacks. Another participant in the discussion suggested that fee rates should be required to increase if users wished to replace multiple transactions with a single one, similar to RBF. However, this could introduce DoS vectors and make it easier to push other users' transactions out of the mempool. The original poster had been trying to use bip125 to merge unconfirmed transactions, but found it difficult to track changes and ensure payment safety without introducing complexity.
Updated on: 2023-06-12T23:59:15.895338+00:00