Author: Matt Corallo 2017-12-23 16:25:08
Published on: 2017-12-23T16:25:08+00:00
A recent pull request has been submitted that would turn on Replace-by-Fee (RBF) by default. This has triggered some discussion, and to ease the transition for merchants who are reluctant to see their customers use RBF, a no125=1 flag was suggested by Matt Corallo. When this flag is set, wallets should not use RBF, regardless of their default, unless the user explicitly overrides the merchant's preference. Luke Dashjr objects to this suggestion, stating that there is no reason to ever avoid the RBF flag and he is not aware of any evidence that it reduces risk or prevents double spending. Peter Todd seconds this objection, but adds that there are some legitimate reasons why people use non-RBF transactions, such as selling BTC based on an incoming transaction which will need to be converted to fiat. If people want to overpay on fees to do so, there is no reason not to let them, including if the merchant is willing to Child Pays for Parent (CPFP) to do so. Todd anticipates very low usage of the no125=1 flag, but supports including it nonetheless. If things turn out differently with merchants reducing the usability of BTC without taking over the CPFP responsibility, the option could imply receiver-pays-fee, but there is no reason to overcomplicate it yet.
Updated on: 2023-05-20T04:36:27.622836+00:00