Disabling RBF has no practical effect in minimizing risks in this case.
With RBF enabled:
- You send tx first, hacker can RBF
- Hacker send tx first, you can RBF
It’s purely based on luck on whether your tx or the hackers will be included in the next block. You and the hacker can continue to RBF indefinitely until the tx is confirmed.
Knots with RBF disabled:
- You send tx first, hacker can broadcast a replaceable tx to Core and get your tx replaced
- Hacker send tx first, you can broadcast a RBF to Core and get it replaced.
Core v28+ has full-RBF which means it allows replacement even if the original tx didn’t signal RBF.
Disabling RBF in Knots does absolutely nothing to protect the user or mitigate any risks.
@sardinhaplantao Eu tenho um plugin no TradingView que puxa os Tweets do Augustão Backes. Excelente indicador de topo e fundo, nunca falhou. Tenho pena do rapaz mas pelo menos as análises dele são úteis dessa forma.
@1hmle Both sides. I’ve seen conspiracy theorists saying the Coldcard hack happened at the last BIP-110 activation window just to distract people away from what is happening between Core and Knots. 🤷♂️