pull down to refresh

RBF and congestion
123 sats \ 4 comments \ @l0k18 14 May 2023 bitcoin
When finally the majority of the nodes support full RBF, chain congestion isn't gonna be as big a problem. Bumping fees using CPFP can only be done by the spender, and RBF depends on the transaction having it enabled.
I got a not tiny spend made on my behalf by a custodian get abandoned and it had no RBF enabled. It will shortly be 6 days in the mempool. There's a chance it might clear this weekend, first time it's within an hour of clearing.
But I could have had it sorted before the fees rose past 100sat/vByte if it had been RBF.
Enable RBF, upgrade your nodes, and wallet devs, make it default, dammit, so people never have to see stuck transactions they could pay to fix not arriving at addresses they control.
And it weakens the potency of any intentional or unintentional effort to DoS the chain.
write
preview
related posts
120 sats \ 2 replies \ @kristapsk 14 May 2023
Bumping fees using CPFP can only be done by the spender
No, CPFP can be done by receiver too, that's the benefit over RBF.
reply
0 sats \ 0 replies \ @l0k18 OP 14 May 2023
oh really
reply
0 sats \ 0 replies \ @033daf6a55 14 May 2023
100%
reply
0 sats \ 0 replies \ @033daf6a55 14 May 2023
this is not an attack... You have the wrong data. If it is expensive for you to pay 100 sats, then you are not ready. why don't you want to count on a transaction of 2000 sats? or 10000 sats? or maybe 25000 sats??? what will they do? if you can't count on it, then you should think about it and understand the reason for such mathematics...
reply