Post
Topic
Board Development & Technical Discussion
Re: Full RBF
by
LoyceV
on 06/05/2023, 09:28:08 UTC
Unfortunately this is no good news for solving the lower bits puzzle transactions
Do you mean those puzzles? All the easy ones are long gone, and for the difficult ones it's not so likely different people will find the keys at the same time.

Quote
If ALL unconfirmed transactions in mempool are RBF enabled there will an overbidding fight for lower bit-puzzles even if initial transaction has set "NO RBF".
People will watch the mempool, check for solved puzzle publickey, solve it quickly with pollard kangaroo and create a new transaction with higher fee.
Interesting approach, I hadn't thought of this. How long would it take to solve the puzzle with known pubkey?

Assuming the extreme worst case scenario of a BRC20 spamstorm and the mempool gets clogged for 48 hours, it's not that big of a deal. Just slap a 200 sat/byte fee on the outgoing transaction and it will be confirmed within minutes, literally.  Not a problem since rewards are basically over 1 bitcoin by now, so $300 in fees is quite nothing by comparison. Smiley
With 200 sat/byte, it's only $12 in fees. But if someone manages to raise the fee, Kamoheapohea has a point.

It will be much more interesting what happens to leaked private keys when Full RBF gets implemented:
Things will get quite interesting once full RBF becomes commonplace. Any such transaction stealing coins from a brain wallet or leaked private key could be replaced by another transaction, regardless of whether or not is opted in to RBF or not. We could end up seeing different bots broadcasting more and more replacements, each paying a higher and higher fee, trying to steal the coins for themselves. Since there is no incentive for any one such bot to surrender and let another bot win, then such transactions could just escalate until the entire value (or close to it) is paid in fees.
I was curious about that scenario too. That would mean that (eventually) only miners profit from funds sent to addresses with leaked private keys.

just set it to no RBF
If only you would have read what this topic is about.