100 sats \ 2 replies \ @krawall 5 Aug \ on: full-RBF by default in Bitcoin Core v28 bitcoin
honestly it doesn't really matter.... there were always ways around even your node didn't have it on by default. plus for those people opposing it, that ship had already sailed. you could never trust a transaction in the mempool getting confirmed or not.
Keeping the feature out did not lead to any more security in having transactions guaranteed than otherwise. I have, on occasion, unpublished a transaction (still possible with bitcoin core I guess when you add config settings) and I have on a different occasion double spent because of my initial fee was way too low and no way to raise it.
we were thinking of accepting mempool only transactions if the fee were high enough and the amount was low enough but we never did. with the advent of L2 solutions (mostly lightning) this is even less of an issue now.
honestly it doesn't really matter....
It actually does! Full-RBF prevents certain types of transaction pinning issues. So having more nodes run it is helpful even if ~100% of miners are already doing it.
Also, it'll help improve block propagation time a bit; right now compact blocks reconstruction frequently fails due to missing full-rbf replacements.