Author: Anthony Towns 2022-02-01 01:56:37
Published on: 2022-02-01T01:56:37+00:00
In a Bitcoin Dev mailing list, Bastien Teinturier suggested an alternative approach to designing new rules for descendants. He argued that limiting the impact on descendant transactions was only important for DoS protection and not for incentive compatibility. However, another member of the mailing list pointed out that the goal is to discourage people from wasting network bandwidth by publishing transactions that will never get confirmed. The proposal was to have a relay rate limit and prioritize by ancestor fee rate. This way, any low fee rate tx spam will sit as "relayed=false" until they are replaced or the network becomes less busy. The actual mempool accept policy can be "is this tx a higher fee rate than the txs it replaces." Regarding updated RBF rules, a wallet can continue to use old rules for a long time if they want to be safe, even if Bitcoin Core releases a new version with updated rules. However, all that is needed is for there to be *a* path that follows the new relay rules and gets from a node/wallet to perhaps 10% of hashpower. Wallet providers could construct such a path relatively quickly.
Updated on: 2023-05-22T16:59:24.391098+00:00