Author: Peter Todd 2022-10-31 17:51:10
Published on: 2022-10-31T17:51:10+00:00
The email thread in bitcoin-dev discusses the relay of full-replace-by-fee (full-rbf) transactions by nodes that do not signal it. There are nodes that signal full-rbf and preferentially peer to each other, ensuring good transaction propagation. People can run some nodes with a large number of outgoing peers to make full-rbf work more reliably. A "full-rbf transaction" is nothing special but it replaces a previously broadcast transaction that did not signal replacement. Non-full-rbf nodes will broadcast replacements when they did not receive the first transaction first. Testing full-rbf is problematic as a small percentage of the time, the "replacement" transaction will be the one that gets mined. There is no consensus over the mempool, so adding more configuration options always increases code complexity. However, accommodating both types of transaction policy seems worth it for network participants who rely on both. Since all the machinery to do replacement already exists, adding a full-rbf config flag requires just a single line in the mempool code.
Updated on: 2023-06-16T02:29:36.032945+00:00