Cheers for the write-up, I read it end to end, but haven't managed to digest it fully.
As a community, we want to prevent the possibility of double spending the mempool with mempoolfullrbf=1. Does that means wallets should disable the option for opting out of RBF?
The way we prevent wallets from double spending is the adoption of lightning. The mempool simply can't prevent double spending reliably, and trying to do so is harmful for a lot of reasons.
We have to accept that unconfirmed is unconfirmed. Which is exactly what the supermajority of wallets do already.
Enabled it on my umbrel now
Did you find it easy to activate? I don't have an Umbrel so I don't know how easy the UI is.
It is in the Advanced Settings, so anyone can activate it.
deleted by author
deleted by author
Thanks for this detailed explanation.
deleted by author
Excellent essay and compelling argument. I leanred a lot and have a lot to learn
deleted by author
Cheers for the write-up, I read it end to end, but haven't managed to digest it fully.
As a community, we want to prevent the possibility of double spending the mempool with
mempoolfullrbf=1. Does that means wallets should disable the option for opting out of RBF?The way we prevent wallets from double spending is the adoption of lightning. The mempool simply can't prevent double spending reliably, and trying to do so is harmful for a lot of reasons.
We have to accept that unconfirmed is unconfirmed. Which is exactly what the supermajority of wallets do already.
unconfirmed=unconfirmed
Thanks :)
deleted by author
deleted by author
deleted by author
Good read.
deleted by author
deleted by author