Return to Answer

Hence a -mempoolfullrbf option was introduced in the Bitcoin Core 24.0 release which would allow full node operators to ignore RBF signaling on transactions and accept replacement transactions into their mempools regardless of whether the original transaction was signaling for RBF or not. In Bitcoin Core 24.0 it is off by default but node operators can turn it on to ignore the RBF signaling of transactions. The proportion of node operators that turn this option on will determine how likely it is for a replacement transaction (for an original transaction that didn't initially signal for RBF) to ultimately reach a miner's mempool via the P2P network. There has also been a derivative of Bitcoin Core (Full-RBF Peering Bitcoin Core v24.0.1) released by Peter Todd which will advertise that you have the option switched on and to connect to other peers that also have the option switched on. If you run this derivative it would increase the likelihood of a RBF transaction reaching a miner's mempool via the P2P network.

Hence a -mempoolfullrbf option was introduced in the Bitcoin Core 24.0.1 release which would allow full node operators to ignore RBF signaling on transactions and accept replacement transactions into their mempools regardless of whether the original transaction was signaling for RBF or not. In Bitcoin Core 24.0.1 it is off by default but node operators can turn it on to ignore the RBF signaling of transactions. The proportion of node operators that turn this option on will determine how likely it is for a replacement transaction (for an original transaction that didn't initially signal for RBF) to ultimately reach a miner's mempool via the P2P network. There has also been a derivative of Bitcoin Core (Full-RBF Peering Bitcoin Core v24.0.1) released by Peter Todd which will advertise that you have the option switched on and to connect to other peers that also have the option switched on. If you run this derivative it would increase the likelihood of a RBF transaction reaching a miner's mempool via the P2P network.

Hence a -mempoolfullrbf option was introduced in the Bitcoin Core 24.0 release which would allow full node operators to ignore RBF signaling on transactions and accept replacement transactions into their mempools regardless of whether the original transaction was signaling for RBF or not. In Bitcoin Core 24.0 it is off by default but node operators can turn it on to ignore the RBF signaling of transactions. The proportion of node operators that turn this option on will determine how likely it is for a replacement transaction (for an original transaction that didn't initially signal for RBF) to ultimately reach a miner's mempool via the P2P network.

Hence a -mempoolfullrbf option was introduced in the Bitcoin Core 24.0 release which would allow full node operators to ignore RBF signaling on transactions and accept replacement transactions into their mempools regardless of whether the original transaction was signaling for RBF or not. In Bitcoin Core 24.0 it is off by default but node operators can turn it on to ignore the RBF signaling of transactions. The proportion of node operators that turn this option on will determine how likely it is for a replacement transaction (for an original transaction that didn't initially signal for RBF) to ultimately reach a miner's mempool via the P2P network. There has also been a derivative of Bitcoin Core (Full-RBF Peering Bitcoin Core v24.0.1) released by Peter Todd which will advertise that you have the option switched on and to connect to other peers that also have the option switched on. If you run this derivative it would increase the likelihood of a RBF transaction reaching a miner's mempool via the P2P network.

Thanks to Orange Surf for providing feedback on the original post.