while adding nothing.
Absolute mischaracterization. Literally everyone who uses 0-conf trusts that a double spend transaction won't be broadcasted and mined by a miner. This change shows the merchant that they are no longer "protected" by "default settings".
you're taking away a way to use Bitcoin
Yes, we're taking away a way to use Bitcoin in a way it wasn't meant to be used.
Literally everyone who uses 0-conf trusts that a double spend transaction won't be broadcasted and mined by a miner.
Yes, congratulations, you understood the risk businesses have to account for when enabling superior user experiences with 0-conf. 👏
Yes, we're taking away a way to use Bitcoin in a way it wasn't meant to be used.
The audacity... fucking unbelievable.
reply
Please tell me, what is more important to you:
Superior UX for users of businesses relying on 0-conf since they don't have to wait for their tx to be included in a block
vs.
Superior UX for all users since they can bump their fee to have it included in the next block faster without having to enable or think about it in advance
reply
Wrong.
If you use Blockstream green, you don't have to think about it. If you enable it in wallets where it's supported, you don't have to think about it. If your wallet doesn't support RBF, then change your wallet.
reply
If you use Blockstream green, you don't have to think about it. If you enable it in wallets where it's supported, you don't have to think about it. If your wallet doesn't support RBF, then change your wallet.
Lots of if's for saying that
without having to enable or think about it in advance
is wrong, no?
Basically, your comment reads like this:
No, you are wrong. You don't have to think about it if you don't have to think about it.
reply