RBF can be back?

[cryptcoin-junkey]

Let me have a casual discussion here before publishing the issue.

Currently, Monacoin have decided to reject RBF (replace by fee).
The reason is as Litecoin was rejected RBF.

But just AFAIK, there is no application that requires 0-conf on Monacoin (and also Monaparty).
And Monacoin can provide Lightning Network for applications that requires a real-time transfer.

So I suppose we can accept RBF with no pain.
WDYT, @wakiyamap @tcejorpniocanom ?

[wakiyamap]

I think that's a good point, because it makes it easier to manage the electrum-mona and monad sources.

But I don't have a problem with RBF itself,
but I'm wondering if there are people who will start calling it the source of DoubleSpend.

It doesn't seem to me that there's enough merit in the community to get into trouble.
It is not currently necessary, and I don't think it is necessary as long as there are alternatives such as CPFP.

[cryptcoin-junkey]

There have two case that a double spend attack is done, I suppose.

1. 0-conf
2. n-conf with reorg.

Some cases like a Comiket, 0-conf can be used.
But it have a low risk because receivers can be check if the transaction have Opt-in RBF flag.

"n-conf with reorg" is too expensive for casual attackers.
Surely, some bad people may try it and use the source of FUD.
But such people will keep spreading FUD whether double spendable or not. :-)

[cryptcoin-junkey]

After inspects, we know Litecoin doesn't disable RBF in the protocol level but UI layer. Monacoin is same.

I suppose the current approach will misread users.
Users believe RBF is disabled, thieves know they can do 0-conf double-spend attack. Horrible.

In Monacoin-core 0.20, opt-in RBF UI will be back. The default value is disable even if the Bitcoin's default is enable. This is a backward compatibility.
After Monacoin-core 0.21, opt-in RBF is enable as the default.

Monacoin-core won't disable opt-in RBF in the protocol level.

This decision does not constrain the judgment of the wallet developers.
All wallet developers can choose the default value of opt-in RBF by their policy.