Consider switching the client to full-RBF

[lontivero]

Bitcoin core is moving to change the way the RBF transactions are treated because the are some hypothetical situations where opt-out transactions can be used to deny propagation of multiparty transactions like our coinjoins.

Currently Wasabi client only allow replacement of transactions which opted-in BIP125 but it would be convenient to review this.

[petertodd]

Also along these lines, it could be good to change the coinjoin transactions to opt-in to RBF via BIP-125. That'll make sure you've got all the necessary infrastructure to deal with double-spends of coinjoin inputs.

[lontivero]

it could be good to change the coinjoin transactions to opt-in to RBF via BIP-125

Sadly it's not so easy to do because clients build the coinjoin transaction by themselves and then everybody should upgrade at the same time. It could be possible to have some kind of activation date after what users have to upgrade but it is not cool.

Anyway, RBF (full or opted-in via 125) is something we need to implement a more effective DoS prevention mechanism.

[lontivero]

First step in this direction: #12301

[MaxHillebrand]

TODO: client local full node use full-RBF

[molnard]

Closed by #12644