Author: Daniel Lipshitz 2022-12-14 08:12:30
Published on: 2022-12-14T08:12:30+00:00
A potential solution to the issue of double spending caused by FullRBF is First-Seen-Safe Replace-By-Fee (FSS-RBF). This is because FSS-RBF only requires an additional input transaction to be included in the second transaction, which would not harm the original output. Merchants could monitor block inclusion for the relevant output and implement some wallet logic to easily resolve any issues. However, it is unclear why the limitation of adding an additional input hinders the added value of FullRBF and how significant that hinderance is. John Carvalho, CEO of Synonym.to, questioned why this solution was not put in place earlier and expressed concerns about the potential for more double spending at unknowing merchants after years of FSS protection. Daniel Lipshitz, from GAP600, responded by acknowledging the suitability of FSS-RBF as a way forward to balance FullRBF while retaining the significant 0-conf use case.
Updated on: 2023-06-16T03:23:38.595766+00:00